1 (edited by r.vanderkooi 2021-12-14 02:15:29)

Topic: SOGO Doens't start after update

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2
- Deployed with iRedMail Easy or the downloadable installer? self installed
- Linux/BSD distribution name and version: Centos 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): Mysql
- 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.
====

Helo,

After a update this morning of my centos server with yum update sogo doens't work.

can anybody help me?

sogod.service - SOGo is a groupware server
   Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled; vendor preset: disabled)
   Active: failed (Result: core-dump) since Mon 2021-12-13 18:56:29 CET; 18s ago
  Process: 8218 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=dumped, signal=SEGV)


Dec 13 18:56:28  systemd[1]: Starting SOGo is a groupware server...
Dec 13 18:56:29  systemd-coredump[8220]: Process 8218 (sogod) of user 980 dumped core.
Dec 13 18:56:29  systemd[1]: sogod.service: Control process exited, code=dumped status=11
Dec 13 18:56:29  systemd[1]: sogod.service: Failed with result 'core-dump'.
Dec 13 18:56:29  systemd[1]: Failed to start SOGo is a groupware server.


My /var/log/sogo/sogo.log is empty.

/usr/run/sogo/sogo.pid doens't exist.
i have try: touch /var/run/sogo/sogo.pid ; chown sogo /var/run/sogo/sogo.pid
But after restarting sogod removed the file sogo.pid

----

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

2 (edited by Cthulhu 2021-12-14 02:57:55)

Re: SOGO Doens't start after update

the pid file is only a numerical value which contins the process id and it gets deleted/recreated each time sogo starts or trys to start.

check syslog or deamon.log for more information if sogo.log is empty


(code=dumped, signal=SEGV)
a segmentation violation can have many reasons, not possible to give you a working solution right now, but it might be related to SELinux maybe

3

Re: SOGO Doens't start after update

This stay in messages log? what can i try?


Dec 13 21:47:52 mail systemd[1]: Starting SOGo is a groupware server...
Dec 13 21:47:53 mail kernel: sogod[30346]: segfault at 7fffb6ae4f08 ip 00007f872b036edd sp 00007fffb6ae4f08 error 6 in libgnustep-base.so.1.24.9[7f872ac96000+4e8000]
Dec 13 21:47:53 mail kernel: Code: 08 48 8d 05 05 eb 45 00 5b 5d c3 66 90 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 4c 8d 9c 24 00 c0 ff ff 48 81 ec 00 10 00 00 <48> 83 0c 24 00 4c 39 dc 75 ef 48 81 ec a8 00 00 00 48 89 74 24 18
Dec 13 21:47:53 mail systemd[1]: Started Process Core Dump (PID 30347/UID 0).
Dec 13 21:47:53 mail systemd-coredump[30348]: Resource limits disable core dumping for process 30346 (sogod).
Dec 13 21:47:53 mail systemd-coredump[30348]: Process 30346 (sogod) of user 980 dumped core.
Dec 13 21:47:53 mail systemd[1]: sogod.service: Control process exited, code=dumped status=11
Dec 13 21:47:53 mail systemd[1]: sogod.service: Failed with result 'core-dump'.
Dec 13 21:47:53 mail systemd[1]: Failed to start SOGo is a groupware server.
Dec 13 21:47:53 mail systemd[1]: systemd-coredump@223-30347-0.service: Succeeded.

4

Re: SOGO Doens't start after update

Does it work now with the latest SOGo nightly build?