Thanks for the good luck. I need it, but did not find it.
It's getting very technical now. I'm not sure if I can still follow
everything because I'm tired. I've been working on this for two days
now. If I understand the idea correctly and the systemd service is
causing the problem, then the problem should be gone if I use a
start/stop script in /etc/init.d. I just did that and it didn't change
anything.
Sigh, unfortunately.
Op 4-2-2026 om 18:56 schreef Wietse Venema:
Ruud Baart via Postfix-users:
Thanks for all the help but I can't find the problem.
I rebooted the server with a forced fsck+repair. Nothing special.?I
reviewed de output from mount: nothing special with read-only. Logfiles:
nothing strange, dmesg: nothing strange. Server is running normal and
serving websites and mail.
Pff....
I may have a few leads. Read and shiver.
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
2BAF05F444D 2700 Mon Feb 2 18:26:18 address@concealed
(temporary failure. Command output: /usr/local/sympa/bin/queue: while
opening queue file 'T.listserver.prompt.nl.1770053178.1208809':
Read-only file system)
address@concealed
Source code in sympa/src/libexec/queue.c:
fd = open(qfile, O_CREAT | O_WRONLY, 0600);
if (fd == -1) {
char *buffer =
(char *) malloc(strlen(argv[0]) + strlen(queuedir) + 80);
sprintf(buffer, "%s: while opening queue file '%s'", argv[0],
qfile);
perror(buffer);
exit(EX_TEMPFAIL);
}
This seems to confirm that Sympa isn't lying. The kernel is really
failing an open() call with a 'read-only file system' error.
HOWEVER some postings on the web suggest that opening a file can
fail with this specufic error when a process runs under systemd and
a systemd.service uses DynamicUser=yes.
Examples of deterministic and non-deterministic error behavior:
https://unix.stackexchange.com/questions/658077/what-could-cause-erofs-error-for-an-openat-call-of-a-symlinked-path-but-only-so
Background:
https://unix.stackexchange.com/questions/635027/systemd-dynamicuser-vs-user
I'm not saying that DynamicUser is the problem; it could be some
other systemd feature that is causing this. Or some other policy
setting that was changed from one OS distribution to the next one.
Good luck.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
