Mailman fails to start: No such file or directory: '/var/lock/mailman/master-qrunner.hostname'

Created:

2017-01-26 08:29:47 UTC

Modified:

2017-08-08 15:32:45 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Mailman fails to start: No such file or directory: '/var/lock/mailman/master-qrunner.hostname'

Applicable to:

  • Plesk Onyx for Linux

Symptoms

mailman service is failed to start:

# systemctl status mailman
● mailman.service - GNU Mailing List Manager
Loaded: loaded (/usr/lib/systemd/system/mailman.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-01-26 02:49:29 GMT; 1min 3s ago
Process: 488 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start (code=exited, status=1/FAILURE)
Process: 476 ExecStartPre=/bin/chmod 660 /var/log/mailman/error (code=exited, status=0/SUCCESS)
Process: 465 ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error (code=exited, status=0/SUCCESS
Process: 449 ExecStartPre=/bin/touch /var/log/mailman/error (code=exited, status=0/SUCCESS)
Process: 413 ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited, status=0/SUCCESS)
Process: 337 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg (code=exited, status=0/SUCCESS)

plesk mailmanctl[488]: IOError: [Errno 2] No such file or directory: '/var/lock/mailman/master-qrunner.plesk.323.1'
OR 
plesk mailmanctl[14938]: IOError: [Errno 13] Permission denied: '/var/lock/mailman/master-qrunner.plesk.*

Cause

The /var/lock/mailman/ directory is missing or was created with the incorrect permissions on boot.

Resolution

  1. Create the /var/lock/mailman/ directory (if it does not exist) and set the correct permissions and ownership:

    # mkdir /var/lock/mailman/
    # chmod 775 /var/lock/mailman/
    # chown root:mailman /var/lock/mailman/
  2. Verify that /var/run/mailman has correct permissions as below:

    # ls -ald /var/run/mailman
    drwxrwxr-x 2 root mailman 60 Jan 26 04:38 /var/run/mailman

If after system reboot the issue persists, check the validity of a mailman package using # rpm -V mailman ( debsums mailman command could be used on Debian and Ubuntu). Check the output meaning (use https://linux.die.net/man/8/rpm (Verify Options) for reference) and fix the reported issues. For example:

# rpm -V mailman

......G..    /usr/lib/mailman
.M....G..  /usr/lib/mailman/Mailman/mm_cfg.py
......G..    /usr/lib/mailman/Mailman/mm_cfg.pyc
......G..    /usr/lib/mailman/cgi-bin
......G..    /usr/lib/mailman/cron
......G..    /usr/lib/mailman/pythonlib

The output means that group permissions for the files has been modified. To fix the issue it is required to set correct permissions:

# chown -R root:mailman /usr/lib/mailman/pythonlib

# chown -R root:mailman /usr/lib/mailman/cgi-bin
# chown -R root:mailman /usr/lib/mailman/cron
# chown root:mailman /usr/lib/mailman
# chmod g+s /usr/lib/mailman/cgi-bin/*

Have more questions? Submit a request
Please sign in to leave a comment.