[tech] Sogo behaving badly (on Mussel)

[Matt Johnston]

I think I've got sogo working again.

The cause of the logs/memory seems to be using ABI
incompatible libraries for SSL LDAP. It was calling accept()
on a /dev/urandom file descriptor! James found it earlier
http://www.sogo.nu/bugs/view.php?id=3211
Possibly Debian don't link to OpenSSL because of license
conflicts with GNUStep or something.

Removing the encryption lines from the config fixes it:
mussel:/home/other/calendar/GNUstep/Defaults# diff gnustepdefaultsbackup-matt .GNUstepDefaults
57,58d56
<       <key>encryption</key>
<       <string>SSL</string>
66c64
<       <string>636</string>
---
>       <string>389</string>


In the process I upgraded to the current nightly sogo deb -
no idea if it improves anything, I've now commented out both
lines in apt sources.list anyway.

I also found I had to remove my entry in the postgresql
table, otherwise I just got a page that said
        object not found: Matt => Calendar
Fixed with
        delete from sogo_user_profile where c_uid = 'matt';
and my calendar/address book seem intact.

Can someone try if their login works? We might need to
empty the sogo_user_profile table.

Matt


On Mon, Jul 27, 2015 at 09:00:19AM +0800, David Adam wrote:
> 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@
> _______________________________________________
> List Archives: http://lists.ucc.gu.uwa.edu.au/pipermail/tech
> 
> Unsubscribe here: http://lists.ucc.gu.uwa.edu.au/mailman/options/tech/matt%40ucc.gu.uwa.edu.au