>> Calling [libxmlSAXLocator -lineNumber] with incorrect signature. Method >> has i16@0:8, selector has q16@0:8 >> >> Calling [NGDOMElement -setLine:] with incorrect signature. Method has >> v24@0:8q16, selector has v20@0:8i16 >> >> Calling [GSMutableArray -length] with incorrect signature. Method has >> I16@0:8, selector has Q16@0:8 > > those should also not really matter. Is there more warnings/errors you get > in sogo logs?
Apparently I missed the following: Jun 02 11:49:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 1 minutes Jun 02 11:50:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 2 minutes Jun 02 11:51:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 3 minutes Jun 02 11:52:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 4 minutes Jun 02 11:53:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 5 minutes Jun 02 11:54:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 6 minutes Jun 02 11:55:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 7 minutes Jun 02 11:56:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 8 minutes Jun 02 11:57:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> pid 22089 has been hanging in the same request for 9 minutes Jun 02 11:58:26 sogod [20383]: [WARN] <0x0x13192b522490[WOWatchDogChild]> safety belt -- sending KILL signal to pid 22089 After some "head scratching" I found that my IMAP server was the problem, not SOGo. After fixing the IMAP server everything works as expected. Sorry for the noise... Kind regards, Martijn Rijkeboer
