[tech] Sogo behaving badly (on Mussel)

[David Adam]

SoGo is doing a great job of a) filling the disk with logs and b) mapping 
all the memory on the system.

I'm not too familiar with the internals of the OOM killer but for whatever 
reason it wasn't triggering. This made it hard to be certain what was 
going on because I got lots of:

root at mussel ~# df -h
Could not create child process - exiting
fork: Cannot allocate memory
mussel:~# service sogo stop
-bash: fork: Cannot allocate memory
mussel:~# cat /proc/meminfo
-bash: fork: Cannot allocate memory
mussel:~# cd /proc
mussel:/proc# ls
-bash: fork: Cannot allocate memory

When I saw this happen the other day I managed to get top running which 
showed Sogo using most of the memory.

The logs are full of:
sogod[25376] Problem posting notification: <NSException: 0xa8e004b0> 
NAME:NSMallocException REASON:Default zone has run out of memory 
INFO:(null)

I killed process 25376 and everything came back properly. Then I ran 
`logrotate -f /etc/logrotate.d/sogo` to compress the 2.0GB log file and 
now we have some free space.

The remaining sogo process was still trying to eat a fair bit of RAM:
23244 sogo      20   0  980m 929m  720 S     0 23.0   1:54.53 sogod                                                   

I've left sogo stopped for now. Perhaps someone who actually uses it could 
try rolling back to the last version, or put it under ulimit or something?

[DAA]
zanchey@