| Description | I realized after a routinary server reboot, with sogo version 4.1.1.20191204
When I try to start the service with 'systemctl start sogod', the following messages appear in the log:
- sogod.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2019-12-05 09:02:57 CET; 2s ago
Process: 12393 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=exited, status=0/SUCCESS)
Main PID: 12406 (code=exited, status=1/FAILURE)
Dec 05 09:02:57 hermes6 systemd[1]: Starting SOGo is a groupware server...
Dec 05 09:02:57 hermes6 sogod[12406]: 2019-12-05 09:02:57.594 sogod[12406:12406] unable to get status of descriptor 2 - Bad file descriptor
Dec 05 09:02:57 hermes6 systemd[1]: Started SOGo is a groupware server.
Dec 05 09:02:57 hermes6 systemd[1]: sogod.service: main process exited, code=exited, status=1/FAILURE
Dec 05 09:02:57 hermes6 systemd[1]: Unit sogod.service entered failed state.
Dec 05 09:02:57 hermes6 systemd[1]: sogod.service failed. |
|---|
| Additional Information | If I reinstall the package with yum, the following "non fatal" message is shown:
yum reinstall sogo
--> Running transaction check
---> Package sogo.x86_64 0:4.1.1.20191204-1.el7.centos will be reinstalled
--> Finished Dependency Resolution
Running transaction
Installing : sogo-4.1.1.20191204-1.el7.centos.x86_64 1/1
warning: %post(sogo-4.1.1.20191204-1.el7.centos.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package sogo-4.1.1.20191204-1.el7.centos.x86_64
Verifying : sogo-4.1.1.20191204-1.el7.centos.x86_64 |
|---|
