![](https://secure.gravatar.com/avatar/b273ab068bc220d17a3e4c710c401c4b.jpg?s=120&d=mm&r=g)
(Please reply to the list, not the individual)
On 7/2/2024 4:14 PM, John wrote:
Yes, I did run check_perms - it showed no problems.
As Mark suggested, is the file system mounted read-only? 'mount' will show that, and fstab could make that the default.
What happens when you manually try to create a file in /usr/local/mailman/qfiles/in/?
Is 'selinux' turned on? that can cause all kinds of permission errors.
How was mailman started and by which user? Are the mailman user/group correct?
Otherwise, without a lot more info about your installation and whay you've checked we're just making wild guesses.
z!
![](https://secure.gravatar.com/avatar/fd77a9387963da792ed91b5ab48b24ea.jpg?s=120&d=mm&r=g)
Thanks again for getting back to us.
mount says:
/dev/sda1 on / type ext4 (rw,relatime)
this being where mailman lives. The file system definitely seems to be read-write.
I can successfully create a file /usr/local/mailman/qfiles/in/ , even if I log in as a non-root user.
Turning off SELINUX was pretty much the first thing we did when we got the server. I just checked - it's still off:
SELINUX=disabled
Mailman was started as a service:
[Unit] Description=GNU Mailing List Manager After=syslog.target network.target
[Service] ExecStartPre=/usr/local/mailman/bin/mailman-update-cfg ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/local/mailman/cron/crontab.in /etc/cron.d/mailman ExecStartPre=/bin/touch /var/log/mailman/error ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error ExecStartPre=/bin/chmod 660 /var/log/mailman/error ExecStart=/usr/local/mailman/bin/mailmanctl -s start ExecReload=/usr/local/mailman/bin/mailmanctl restart ExecStop=/usr/local/mailman/bin/mailman-update-cfg ExecStop=/usr/local/mailman/bin/mailmanctl stop ExecStop=/bin/sh -c 'echo -e "# DO NOT EDIT THIS FILE!\n#\n# Contents of this file managed by /etc/init.d/mailman\n# Master copy is /usr/local/mailman/cron/crontab.in" > /etc/cron.d/mailman' Type=forking
[Install] WantedBy=multi-user.target
I've also tried running it manually, like this:
/usr/lib/mailman/bin/mailmanctl start
with the same results. I'm logged in as root at the time.
All the files in the mailman directory are owned root:mailman .
I sincerely appreciate your help - even the wild guesses. If there's anything else I can tell you, please let me know.
::Jack
From: Carl Zwanzig <cpz@tuunq.com> Sent: 03 July 2024 03:58 To: John <j_p_waterhouse@hotmail.com>; mailman-users@python.org <mailman-users@python.org> Subject: Re: [Mailman-Users] Re: Read-only file system
(Please reply to the list, not the individual)
On 7/2/2024 4:14 PM, John wrote:
Yes, I did run check_perms - it showed no problems.
As Mark suggested, is the file system mounted read-only? 'mount' will show that, and fstab could make that the default.
What happens when you manually try to create a file in /usr/local/mailman/qfiles/in/?
Is 'selinux' turned on? that can cause all kinds of permission errors.
How was mailman started and by which user? Are the mailman user/group correct?
Otherwise, without a lot more info about your installation and whay you've checked we're just making wild guesses.
z!
![](https://secure.gravatar.com/avatar/fd77a9387963da792ed91b5ab48b24ea.jpg?s=120&d=mm&r=g)
Thanks again for getting back to us.
mount says:
/dev/sda1 on / type ext4 (rw,relatime)
this being where mailman lives. The file system definitely seems to be read-write.
I can successfully create a file /usr/local/mailman/qfiles/in/ , even if I log in as a non-root user.
Turning off SELINUX was pretty much the first thing we did when we got the server. I just checked - it's still off:
SELINUX=disabled
Mailman was started as a service:
[Unit] Description=GNU Mailing List Manager After=syslog.target network.target
[Service] ExecStartPre=/usr/local/mailman/bin/mailman-update-cfg ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/local/mailman/cron/crontab.in /etc/cron.d/mailman ExecStartPre=/bin/touch /var/log/mailman/error ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error ExecStartPre=/bin/chmod 660 /var/log/mailman/error ExecStart=/usr/local/mailman/bin/mailmanctl -s start ExecReload=/usr/local/mailman/bin/mailmanctl restart ExecStop=/usr/local/mailman/bin/mailman-update-cfg ExecStop=/usr/local/mailman/bin/mailmanctl stop ExecStop=/bin/sh -c 'echo -e "# DO NOT EDIT THIS FILE!\n#\n# Contents of this file managed by /etc/init.d/mailman\n# Master copy is /usr/local/mailman/cron/crontab.in" > /etc/cron.d/mailman' Type=forking
[Install] WantedBy=multi-user.target
I've also tried running it manually, like this:
/usr/lib/mailman/bin/mailmanctl start
with the same results. I'm logged in as root at the time.
All the files in the mailman directory are owned root:mailman .
I sincerely appreciate your help - even the wild guesses. If there's anything else I can tell you, please let me know.
::Jack
From: Carl Zwanzig <cpz@tuunq.com> Sent: 03 July 2024 03:58 To: John <j_p_waterhouse@hotmail.com>; mailman-users@python.org <mailman-users@python.org> Subject: Re: [Mailman-Users] Re: Read-only file system
(Please reply to the list, not the individual)
On 7/2/2024 4:14 PM, John wrote:
Yes, I did run check_perms - it showed no problems.
As Mark suggested, is the file system mounted read-only? 'mount' will show that, and fstab could make that the default.
What happens when you manually try to create a file in /usr/local/mailman/qfiles/in/?
Is 'selinux' turned on? that can cause all kinds of permission errors.
How was mailman started and by which user? Are the mailman user/group correct?
Otherwise, without a lot more info about your installation and whay you've checked we're just making wild guesses.
z!
participants (2)
-
Carl Zwanzig
-
John