View Issue Details

IDProjectCategoryView StatusLast Update
0004900SOGoPackaging (RedHat)public2019-12-05 11:25
Reporterourra Assigned Tofrancis  
Status closedResolutionno change required 
Platform[Server] LinuxOSRHEL/CentOSOS Version7
Product Version4.1.1 
Summary0004900: Service won't start and throws error: "unable to get status of descriptor 2 - Bad file descriptor"

I realized after a routinary server reboot, with sogo version
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/ -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.

Steps To Reproduce

Execute 'systemctl restart sogod'

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: will be reinstalled
--> Finished Dependency Resolution

Running transaction
Installing : sogo- 1/1
warning: %post(sogo- scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package sogo-
Verifying : sogo-

TagsNo tags attached.




2019-12-05 08:38

reporter   ~0013952

I've upgraded with Yum to version and the problem remains, I'm unable to start sogo.



2019-12-05 11:04

reporter   ~0013953

Finally I solved the issue.

The problem was that the log permissions were incorrect (0444)!.

To fix it, I simply executed:

chmod 644 /var/log/sogo/sogo.log

...and now the service starts OK.

Issue History

Date Modified Username Field Change
2019-12-05 08:07 ourra New Issue
2019-12-05 08:38 ourra Note Added: 0013952
2019-12-05 11:04 ourra Note Added: 0013953
2019-12-05 11:25 francis Status new => closed
2019-12-05 11:25 francis Assigned To => francis
2019-12-05 11:25 francis Resolution open => no change required