1

Topic: sogod: unable to get status of descriptor 2 - Bad file descriptor

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):

running: 1.3.2 MARIADB edition

- Deployed with iRedMail Easy or the downloadable installer?

Easy

- Linux/BSD distribution name and version:

Ubuntu 18.04
- 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.
====

There was a thread on this earlier, but no answer. /var/log/sogo/sogo.log is empty. the last entries in /var/log/sogo/sogo.log.1 show some watchdog errors (processes hanging). This was working yesterday and today isn't.

I did a package upgrade on sogo AFTER it stopped working... didn't resolve it.

/var/run/sogo is writeable by sogo and does create PID files.

Sogo runs, throws its error to syslog (nothing to the console) and exits cleanly according to systemctl.

I'm 100% sure this is something simple relating to either a memory exhaustion or disk space exhaustion issue. Just started exceeding the capacity of this VM, but haven't migrated to something bitter yet.  Didn't know where in the source to look for what file is trying to be opened and is failing.

everytime sogod runs, we get a log entry like this:

sogod: 2022-01-20 13:46:35.937 sogod[696641:696641] unable to get status of descriptor 2 - Bad file descriptor

just starting using sogo with EAS a few weeks ago.

Thanks so much for any suggestions!!

----

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

2

Re: sogod: unable to get status of descriptor 2 - Bad file descriptor

this happens if you cant access/write to the logfile

create /var/log/sogo/sogo.log as empty file and give it 666 and restart the whole server

3

Re: sogod: unable to get status of descriptor 2 - Bad file descriptor

Wow. you're 100% right.

I mistakenly saw the ownership as syslog:sogo and thought that was fine.  Changing ownership to sogo:sogo and 666 seems fine all around.

thanks so much!