Nothing other than what I have already sent. sogo logs seem normal otherwise, it is very possible that the lack of memory caused this "safety belt" and was caused by something else.
I only ask this question because this has never happened before and started right after I upgraded to the nightly and I thought both may be connected, plus I was running "top" yesterday I saw sogod on the top of the memory usage list but I did not think much of it and did not notice the actual usage, just remember it was on top when I sorted by memory usage. I will keep monitoring the system and will let you know. Thanks for your time, Anton. On 21 September 2010 13:34, Ludovic Marcotte <[email protected]> wrote: > On 21/09/10 3:13 AM, Anton Popov wrote: > >> Hi all, >> >> I upgraded to latest nightly yesterday afternoon and in the middle of the >> night my server ran out of memory (4G ram, 4G swap) and I only have sogo >> running on that server. >> I am not sure sogo caused it, the only thing in the sogo log is: >> > [snip] > > Could sogo cause this or I have some other issue? >> >> Any evidences from the sogo.log files? > > Regards, > > -- > Ludovic Marcotte > [email protected] :: +1.514.755.3630 :: www.inverse.ca > Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence ( > www.packetfence.org) > > -- > [email protected] > https://inverse.ca/sogo/lists > -- [email protected] https://inverse.ca/sogo/lists
