Am 29.05.2024 um 21:52 schrieb Paul Leiber:
Hi list members,
I am running SOGo nightly on a debian bullseye basis which is up to date
with patches. I am on SOGo version 5.10.0 (the most recent nightly).
I am currently trying to figure out some issues (not able to log into
the web interface, calendar not working). I might get back to this list
once I am out of ideas what to do. But now to the issue at hand:
For finding the cause of the above behavior, I am often changing
configuration, which requires me to restart SOGo. However, when
restarting SOGo with "systemctl restart sogo", sogo is not functional
anymore and the following log entries come up:
May 29 21:41:02 sogod [2058]: [WARN] <0x0x557824d99d10[WOWatchDog]>
listening socket: attempt 1 failed
May 29 21:41:03 sogod [2058]: [WARN] <0x0x557824d99d10[WOWatchDog]>
listening socket: attempt 2 failed
May 29 21:41:04 sogod [2058]: [WARN] <0x0x557824d99d10[WOWatchDog]>
listening socket: attempt 3 failed
May 29 21:41:05 sogod [2058]: [WARN] <0x0x557824d99d10[WOWatchDog]>
listening socket: attempt 4 failed
May 29 21:41:06 sogod [2058]: [WARN] <0x0x557824d99d10[WOWatchDog]>
listening socket: attempt 5 failed
May 29 21:41:07 sogod [2058]: [ERROR] <0x0x557824d99d10[WOWatchDog]>
unable to listen on specified port, check that no other process is
already using it
A reboot leads to a functional sogo system (besides the issues mentioned
above), but takes quite some time. In the past, I didn't observe this
behavior.
FYI: With the current nightly, restarting sogo with systemd is working
again.
Best regards,
Paul
