Hi Bero On Feb 9, 2011, at 10:27 AM, Bernhard Rosenkraenzer wrote:
> ever since I updated our server from sogo 1.3.4 to 1.3.5a, we've had problems > with sogod occasionally getting stuck eating up 100% CPU time. > Restarting sogod always fixed it. > > This has appeared in sogo.log just before I had to restart it for the last > time: > > 2011-02-09 16:24:37.698 sogod[10952] WARNING(-[NSNull(misc) length]): called > NSNull -length (returns 0) !!! Those are warnings only. Can you provide use a stacktrace? Use gdb to attach to the stcuk process : gdb -p <PID> ... (gdb) bt Thanks, Francis -- [email protected] :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
