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 co
t/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 r
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
hn ; 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
(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 c
ay, 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: [
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'
> >
> > Se
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
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 dea
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!
10 matches
Mail list logo
