On 10/20/26 20:29, Marcin Cieslak wrote:
Some detailed logs from cyrus?
Initially nothing.
Then I put:
rc_debug="YES"
rc_startmsgs="YES"
in /etc/rc.conf and now I see:
root[59608]: /etc/rc: DEBUG: Sourcing /usr/local/etc/rc.conf.d/cyrus_imapd
root[59649]: /etc/rc: DEBUG: checkyesno: cyrus_imapd_enable is set to YES.
root[59663]: /etc/rc: DEBUG: checkyesno: cyrus_imapd_svcj is set to NO.
root[59679]: /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES.
root[59707]: /etc/rc: DEBUG: checkyesno: cyrus_imapd_svcj is set to NO.
root[59771]: /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon
/usr/local/cyrus/libexec/master -d -p /var/run/cyrus-master.pid
master[59790]: couldn't dup fd 0: Bad file descriptor
master[59790]: exiting
root[59843]: /etc/rc: WARNING: failed to start cyrus_imapd
This is hard to debug, since it doesn't happen if I start it manually
and I have no idea how to attach gdb/truss/whatever to a process that is
spawn from boot (although a jail's boot, that can be started with
"ezjail-admin start mail").
If anyone has any suggestion with this goal...
Maybe it tries to access some of the other services and they are not
ready yet?
It shouldn't depend on any other service, AFAICT.
In any case, from the logs, I see it starts after all the others.
Does delaying the start of the imapd servie work as a workaround?
Altough I usually prefer fixes, insted of workarounds, this might be a
good suggestion.
How do I do this?
Overall, I don't know where to go for support next, as I'm not sure if
this a Cyrus bug, a port bug or FreeBSD.
(The fact that it works on 14.4, but not on 15.1 doesn't necessarily
answer the question).
bye & Thanks
av.
