Am 19.01.2016 um 12:47 schrieb Alejandro Vargas: > I am trying SoGo in an already running Centos 7 with postfix+dovecot+sieve. > I added the inverse repo and installed the sogo 2.3.5 with activesync > > sogo-2.3.5-1.el7.centos.x86_64 > sogo-tool-2.3.5-1.el7.centos.x86_64 > sogo-ealarms-notify-2.3.5-1.el7.centos.x86_64 > sogo-activesync-2.3.5-1.el7.centos.x86_64 > > My first problem is that SoGo eats all the available memory even without > clients connected. If I leave the server unused for a few days, I see > the following error in the console: > > Out of memory: Kill process 2870 (sogod) score 537 or sacrifice child > Killed process 2870 (sogod) total-vm:2536588kB, anon-rss:1268056kB, > file-rss:8kB > sogod[2866]: segfault at 7ffc03310004 ip 00007f1e70c0059c sp > 00007ffc0330c238 error 4 in libc-2.17.so[7f1e70abe000+1b6000] > > If I restarts sogo, it works again for one or two days and then aborts > with the same error. > > > This is the complete log: > < cut >
Your messages log is useless, it only states, that you ran out of RAM. I had that on a big machine, because multiple people tried to attach some iso images (~4 GiB) to their emails! Or exporting huge email folders. On a test machine I got that, because my ActiveSync settings where wrong. You should give us at least a hint on your machine and configuration. How many workers do you have? How many users are using it, how many ActiveSync users/devices? Hom much RAM do you have? What is your sogo configuration? Do you have OGo* files in /tmp? Show us your relevant sogo.log messages. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
