[Mailman-Users] IOError: [Errno 13] Permission denied on config.pck in Fedora 30

Robert Kudyba rkudyba at fordham.edu
Wed Jul 24 15:14:38 EDT 2019

>>> Did you see my reply about the file system needing to be mounted suid?
>> Yes I did an responded in line with the permissions of the sub-directories and files:
>> ls -l  /usr/lib/mailman/cgi-bin/
>> total 264
>> -rwxr-sr-x 1 mailman mailman 23048 Feb 12 06:54 admin
> ...
> I'm not talking about the SETGID bit on the file mode. I'm talking about
> the `mount` command that mounts the file system that contains
> /usr/lib/mailman. look in /etc/fstab. The options field should not have
> 'nosuid’.

/dev/mapper/fedora_newdsm-root /                       xfs     defaults        0 0
UUID=d526e70e-89b1-4029-bfb1-db2e50d622fe /boot                   ext4    defaults        1 2
/dev/mapper/fedora_newdsm-home /home                   xfs     defaults        0 0
/dev/mapper/fedora_newdsm-var /var                    xfs     defaults        0 0
/dev/mapper/fedora_newdsm-swap swap                    swap    defaults        0 0

This did work a few weeks ago not sure when it started perhaps when dnf updated June 30.

And now qrunner is failing to start:
Jul 24 14:36:50 2019 (14350) Qrunner RetryRunner reached maximum restart limit of 10, not restarting.
Jul 24 14:36:50 2019 (14350) Master qrunner detected subprocess exit
(pid: 14438, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting]
Jul 24 14:36:50 2019 (14350) Qrunner IncomingRunner reached maximum restart limit of 10, not restarting.

systemctl start mailman
[root at dsm ~]# systemctl status mailman
● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Wed 2019-07-24 15:12:09 EDT; 7s ago
  Process: 20102 ExecStartPre=	 (code=exited, status=0/SUCCESS)
  Process: 20103 ExecStartPre=/usr/bin/install -m644 -o mailman -g mailman /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited, status=0/SUCCESS)
  Process: 20104 ExecStartPre=/bin/touch /var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 20105 ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 20106 ExecStartPre=/bin/chmod 666 /var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 20107 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start (code=exited, status=0/SUCCESS)
  Process: 20201 ExecStop=/usr/lib/mailman/bin/mailman-update-cfg (code=exited, status=0/SUCCESS)
  Process: 20202 ExecStop=/usr/lib/mailman/bin/mailmanctl stop (code=exited, status=0/SUCCESS)
  Process: 20203 ExecStop=/bin/sh -c echo -e "# DO NOT EDIT THIS FILE!
# Contents of this file managed by /etc/init.d/mailman
# Master copy is /usr/lib/mailman/cron/crontab.in" > /etc/cron.d/mailman (code=exited, status=0/SUCCESS)
 Main PID: 20112 (code=exited, status=0/SUCCESS)

Jul 24 15:12:08 ourdomain systemd[1]: Starting GNU Mailing List Manager...
Jul 24 15:12:08 ourdomain mailmanctl[20107]: Starting Mailman's master qrunner.
Jul 24 15:12:08 ourdomain systemd[1]: Started GNU Mailing List Manager.
Jul 24 15:12:09 ourdomain mailmanctl[20202]: No child with pid: 20112
Jul 24 15:12:09 ourdomain mailmanctl[20202]: [Errno 3] No such process
Jul 24 15:12:09 ourdomain mailmanctl[20202]: Stale pid file removed.
Jul 24 15:12:09 ourdomain mailmanctl[20202]: Shutting down Mailman's master qrunner
Jul 24 15:12:09 ourdomain systemd[1]: mailman.service: Succeeded.

Also you mentioned you didn’t know what this file was:
cat /usr/lib/mailman/bin/mailman-update-cfg

# This script is needed, when SELinux is enabled:
# mailman_mail_t context cannot write to the directory
# /usr/lib/mailman/Mailman so when you change mm_cfg.py, 
# mailman cannot create the .pyc
# This script is called in the init script, which is run in unconfined_t
# so the .pyc is created and the AVC denial is avoided. (bz#481446)

import py_compile


More information about the Mailman-Users mailing list