We're attempting to install mailman on our new server. It's been running
happily on our old one for years.
This server is running Oracle 9 RHEL Linux. It uses postfix for its MTA. We
built mailman 2. 1.39 from source, with the options ./configure
--with-cgi-gid=apache –with-mail-gid=nobody .
If
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!
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/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
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
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 20
