• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue mailman configure process never end

Bourgois_Christophe

Basic Pleskian
Since a few weeks, an automated update didn't work, and I find that mailman configure was locking apt-get.
So I killed apt-get and tried to manually update again, at the begining using
Code:
# apt-get --reinstall install  mailman
and finally using
Code:
# /usr/local/psa/admin/bin/autoinstaller --select-release-current --install-component mailman
But in both case, I get this message and the process never end :
Code:
The following packages will be upgraded:
  mailman
Preconfiguring packages ...
Looking for enabled languages (this may take some time) ... done.
 
Hi Bourgois_Christophe,

did you consider to stop mailman before running the upgrade - process, to solve your issue? ( => "/etc/init.d/mailman stop" )

It would help as well ( for investigations and depending answers from people willing to help you ), to inform us about:
  1. Your complete Plesk version ( incl. MU )
  2. Your operating system
  3. Your current mailman - version
  4. ( possible ) Depending log - entries, which may appear at "/var/log/mailman/*"
  5. If you configured your log - system to log "mail.debug", you could as well have a look at the configured log - file, if there are any issues during the upgrade - process
 
Yes unfortunately, it is the same stopping mailman service.
To reply to your answer :

1 - Plesk version 12.5.30 Mise à jour n° 44, dernière mise à jour à 20 Aoû 2016 06:32 (date of the first problem with mailman update)
2 - OS ‪Debian 7.0‬
3 - Package: mailman Version: 1:2.1.15-1+deb7u1
4 - logs
Code:
Sep 16 08:37:29 2016 mailmanctl(13334): PID unreadable in: /var/run/mailman/mailman.pid
Sep 16 08:37:29 2016 mailmanctl(13334): [Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
Sep 16 08:37:29 2016 mailmanctl(13334): Is qrunner even running?
Sep 16 08:37:35 2016 mailmanctl(13365): PID unreadable in: /var/run/mailman/mailman.pid
Sep 16 08:37:35 2016 mailmanctl(13365): [Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
Sep 16 08:37:35 2016 mailmanctl(13365): Is qrunner even running?
Sep 16 08:39:09 2016 mailmanctl(15612): PID unreadable in: /var/run/mailman/mailman.pid
Sep 16 08:39:09 2016 mailmanctl(15612): [Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
Sep 16 08:39:09 2016 mailmanctl(15612): Is qrunner even running?
 
Hi Bourgois_Christophe,

did you consider to check the permissions of the folder "/var/run/mailman" and the corresponding files inside that folder after you started mailman with the command "service mailman start" ?
Did you create "newlist mailman" after your initial mailman - installation?
Did you check, if your entries at "/etc/aliases" are existent?
Which mail - server do you use on your server?
 
Back
Top