1 Topic by Todd1561

  • Todd1561
  • Member
  • Offline
  • Registered: 2023-01-07
  • Posts: 16

Topic: Sogo daemon dying

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.2 PGSQL edition
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: Debian 11
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

About 3-4 times since I set up iRedMail a few weeks ago I've had the SoGo service just die.  If I manually restart it all is well again.  Nothing out of the ordinary is happening that causes the issue as far as I'm aware.  I'm running on a VM allocated 8 cores and 4GB RAM.  Very low user count, just 3 EAS devices accessing 2 email accounts.  This is always what I see in the SoGo logs after the service fails.  Any idea what might be causing this?

Jan 06 13:39:21 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:21 sogod [1062]: <0x0x562d1abeff10[WOWatchDogChild]> child 2249302 exited
Jan 06 13:39:21 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:21 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:21 sogod [1062]: <0x0x562d1abf1100[WOWatchDogChild]> child 1188 exited
Jan 06 13:39:21 sogod [1062]: <0x0x562d1ac9b760[WOWatchDogChild]> child 1191 exited
Jan 06 13:39:21 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:21 sogod [1062]: <0x0x562d1abf0440[WOWatchDogChild]> child 1184 exited
Jan 06 13:39:21 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:22 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:22 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:23 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:23 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:24 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:24 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:24 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1aca02b0[WOWatchDogChild]> child 1192 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1abf0bb0[WOWatchDogChild]> child 1180 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1abf0600[WOWatchDogChild]> child 1183 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1abf08e0[WOWatchDogChild]> child 1181 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> Terminating with SIGINT or SIGTERM
Jan 06 13:39:25 sogod [1062]: <0x0x562d1abe53c0[WOWatchDogChild]> child 1186 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ad1a4c0[WOWatchDogChild]> child 1189 exited
Jan 06 13:39:25 sogod [1062]: <0x0x562d1ab22ac0[WOWatchDog]> all children exited. We now terminate.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,787

Re: Sogo daemon dying

Memory is more important, please try to give it 8 GB memory.

ClamAV + SpamAssassin are memory hungry, also SOGo with ActiveSync clients (30-50MB for each ActiveSync connection years ago, it may be improved nowadays but i'm not sure).

3 Reply by Todd1561

  • Todd1561
  • Member
  • Offline
  • Registered: 2023-01-07
  • Posts: 16

Re: Sogo daemon dying

You may be right about this being a RAM issue. ClamAV was a memory hog to the point where it collapsed the server so I had to disable that from the beginning. I am a little memory strapped on the hypervisor so I can’t allocate much more to it. I’ve bumped it to 5gb for now. I’ll see if that helps. Thanks.