[Mailman-Users] Re: Read-only File System
Hi Jack I'm glad you managed to find a workaround. Another thing to check is that your MTA (exim4, postfix etc) has access to the queue folder if it is running under systemd and then calling the mailman wrapper. If so, you may need to run 'systemctl edit ' and create or modify the override configuration [Service] definition to include something like: # MTA needs to write the mailman2 queue ProtectSystem=read-only ReadWritePaths=/path/to/mailman2/qfiles Good luck. Ken -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Read-only File System
I didn't... but I tried it now, as I kept the original qfiles directory under another name. It said: --e--- qfiles.dist/commands qfiles.dist/commands: --e--- qfiles.dist/shunt qfiles.dist/shunt: --e--- qfiles.dist/in qfiles.dist/in: --e--- qfiles.dist/bounces qfiles.dist/bounces: --e--- qfiles.dist/virgin qfiles.dist/virgin: --e--- qfiles.dist/archive qfiles.dist/archive: --e--- qfiles.dist/retry qfiles.dist/retry: --e--- qfiles.dist/out qfiles.dist/out: --e--- qfiles.dist/news ::Jack From: Dmitri Maziuk Sent: 05 July 2024 16:53 To: mailman-users@python.org Subject: [Mailman-Users] Re: Read-only File System On 7/5/24 08:53, John wrote: ... > Mailman proved to have no problem writing to the relocated qfiles directory, > and everything magically started working. Did you try lsattr on the original files/dir? Just curious, Dima -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: j_p_waterho...@hotmail.com -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Read-only File System
On 7/5/24 08:53, John wrote: ... Mailman proved to have no problem writing to the relocated qfiles directory, and everything magically started working. Did you try lsattr on the original files/dir? Just curious, Dima -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Read-only file system
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 Sent: 03 July 2024 03:58 To: John ; 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! -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[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! -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Re: Read-only file system
Yes a disk "failure" is possible, I recently had a Samsung 980 pro nvme drive runout of spare blocks (due to bad firmware), this made the file system readonly. Run smartctl on the disk(s) to check. regards Steven From: Robert Heller Sent: Tuesday, 2 July 2024 8:21 am To: Mark Sapiro Cc: mailman-users@python.org Subject: [Mailman-Users] Re: Read-only file system At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro wrote: > > On 6/30/24 17:27, John wrote: > > > line 136, in enqueue fp =en(tmpfile, 'w') IOError: [Errno 30] > > Read-only file system: > > '/usr/local/mailman/qfiles/in/1719765141.057583+cb104828efdd0023821ead337d3d60f72e949690.pck.tmp' > > > > Setting /usr/local/mailman/qfiles/in/ to have write permissions for all > > didnâEUR(tm)t fix the problem. > > > It is not clear what directory is the mount pount for this, but it is > mounted read-only. No one, not even root, can write to it. Look at > /etc/fstab If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes). > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.python.org%2Fmailman3%2Flists%2Fmailman-users.python.org%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167833322%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ogMZWlOauOoLoMVcfdjkAbd31MmOW8fV7k9YFLZny74%3D&reserved=0<https://mail.python.org/mailman3/lists/mailman-users.python.org/> > Mailman FAQ: > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.list.org%2Fx%2FAgA3&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167844037%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=8tpu08ng90WCrxVLekk7ArywQyn9tOqPOzv3W4KJCUE%3D&reserved=0<http://wiki.list.org/x/AgA3> > Security Policy: > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.list.org%2Fx%2FQIA9&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167851045%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qyqhZvR8GPPZtF34Pw1svprYSYAFq6ZfKmRZGm3MyLs%3D&reserved=0<http://wiki.list.org/x/QIA9> > Searchable Archives: > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mail-archive.com%2Fmailman-users%40python.org%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167855494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=gu7twmNSX68pqL7lzO8%2FOAJDZ1OAPNhCwEbmEnrZU7Y%3D&reserved=0<https://www.mail-archive.com/mailman-users@python.org/> > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.python.org%2Farchives%2Flist%2Fmailman-users%40python.org%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167859589%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Xp9r6kY0SNCCPXOJ%2BWcSyOd%2FNxBXiNIt1ZxF8udHHIk%3D&reserved=0<https://mail.python.org/archives/list/mailman-users@python.org/> > Member address: hel...@deepsoft.com > > -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software-- Custom Software Services https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deepsoft.com%2F&data=05%7C02%7Csteven.jones%40vuw.ac.nz%7C854ca3d22ee94fee6d9808dc9a0cd701%7Ccfe63e236951427e8683bb84dcf1d20c%7C0%7C0%7C638554627167864182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qm4l7rMm9RxwLTB%2FT%2FtTqj7Iswnbn4nIiPsm5pqRCnY%3D&reserved=0<http://www.deepsoft.com/> -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-u
[Mailman-Users] Re: Read-only file system
At Mon, 1 Jul 2024 12:45:11 -0700 Mark Sapiro wrote: > > On 6/30/24 17:27, John wrote: > > > line 136, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 30] > > Read-only file system: > > '/usr/local/mailman/qfiles/in/1719765141.057583+cb104828efdd0023821ead337d3d60f72e949690.pck.tmp' > > > > Setting /usr/local/mailman/qfiles/in/ to have write permissions for all > > didnâÂÂt fix the problem. > > > It is not clear what directory is the mount pount for this, but it is > mounted read-only. No one, not even root, can write to it. Look at > /etc/fstab If there was some sort of error, the file system would automatically be re-mounted read-only. Something like a power glitch, etc. can do this. Also a failing disk (sudden bad sector reads or writes). > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > Member address: hel...@deepsoft.com > > -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Re: Read-only file system
On 6/30/24 17:27, John wrote: line 136, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 30] Read-only file system: '/usr/local/mailman/qfiles/in/1719765141.057583+cb104828efdd0023821ead337d3d60f72e949690.pck.tmp' Setting /usr/local/mailman/qfiles/in/ to have write permissions for all didn’t fix the problem. It is not clear what directory is the mount pount for this, but it is mounted read-only. No one, not even root, can write to it. Look at /etc/fstab -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Read-only file system
On 6/30/24 19:27, John wrote: Does anyone have any experience with this issue, and a suggestion as to how to resolve it? We’ve tried everything we can think of, and madness is setting in. What are you running on? "Read-only filesystem" with shell looking like everything's fine happens on dead drives and (more often) messed-up VM storage volumes. "Read-only" bit doesn't eve show up in `mount` when that happens, as I recall. Dima -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Read-only file system
On 6/30/2024 5:27 PM, John wrote: Setting /usr/local/mailman/qfiles/in/ to have write permissions for all didn’t fix the problem. Have you run bin/check_perms? If not, that will flag all the permission problems; adding -f will fix them. Later, z! -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
