On the iredmail forum, someone got me this advice: This happens when sogo can't write its logfile. I mistakenly thought syslog controlled this, but sogo does itself, so he suggested setting permissions to 666 for /var/log/sogo/sogo.log and rebooting... or just restarting sogo would likely work. that seems to have squared me. totally my fault I'm sure. thanks so much, leaving this here for others!
On Mon, Jan 24, 2022 at 5:50 PM FF <fusionf...@gmail.com> wrote: > Hi, thanks for your quick response! > > ls -al sogo* > total 52 > drwxr-x--- 2 root sogo 4096 Jan 20 13:46 . > drwxr-xr-x 113 root root 12288 Jan 21 06:04 .. > -r-------- 1 sogo sogo 65 Dec 29 2020 sieve.cred > -rw-r----- 1 root sogo 15838 Dec 29 2020 sogo.conf > -rw-r----- 1 root root 5133 Dec 29 2020 sogo.conf.2020.12.29.20.44.07 > -rw-r----- 1 root sogo 5132 Jan 20 01:35 sogo.conf.dpkg-dist > > looked like it could be a problem, so I changed ownership to sogo. > > Still getting this: > > sogod: 2022-01-24 17:44:20.960 sogod[2105681:2105681] unable to get > status of descriptor 2 - Bad file descriptor > > When upgrading sogo, I also upgraded sope: > > apt list --installed |grep -i "sogo\|sope" > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > libsope-appserver4.9/unknown,now 4.9.r1664.20220119 amd64 > [installed,automatic] > libsope-core4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-gdl1-4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-ldap4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-mime4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-xml4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > sogo-activesync/now 5.5.0.20220120-1 amd64 [installed,upgradable to: > 5.5.0.20220121-1] > sogo/now 5.5.0.20220120-1 amd64 [installed,upgradable to: 5.5.0.20220121-1] > sope4.9-gdl1-mysql/unknown,now 4.9.r1664.20220119 amd64 [installed] > sope4.9-libxmlsaxdriver/unknown,now 4.9.r1664.20220119 amd64 > [installed,automatic] > > I went ahead and ran this command again: > > apt-get install --only-upgrade 'sogo*' '*sope*' > > and now I'm here: > > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > libsope-appserver4.9/unknown,now 4.9.r1664.20220119 amd64 > [installed,automatic] > libsope-core4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-gdl1-4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-ldap4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-mime4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > libsope-xml4.9/unknown,now 4.9.r1664.20220119 amd64 [installed,automatic] > sogo-activesync/unknown,now 5.5.0.20220124-1 amd64 [installed] > sogo/unknown,now 5.5.0.20220124-1 amd64 [installed] > sope4.9-gdl1-mysql/unknown,now 4.9.r1664.20220119 amd64 [installed] > sope4.9-libxmlsaxdriver/unknown,now 4.9.r1664.20220119 amd64 > [installed,automatic] > > Still no joy, but thanks so much for your assistance so far! > > > On Fri, Jan 21, 2022 at 5:31 AM Christian Mack <users@sogo.nu> wrote: > >> Hello >> >> Did the permissions on /etc/sogo change? >> Do you have another service using the SOGo port 20000 ? >> What do you get when stopping sogo service? >> >> To which version did you upgrade? >> Did you also upgrade sope? >> >> >> Kind regards, >> Christian Mack >> >> Those ActiveSync messages are harmless just for info. >> >> Am 20.01.22 um 20:34 schrieb FF (fusionf...@gmail.com): >> > I've verified that /var/run/sogo/sogo.pid is writable by user sogo. >> > I've verified /var/log/sogo/sogo.log is permissioned for syslog. >> > >> > I get no entries in sogo.log and systemctl says sogod starts and exits >> > clearly. >> > >> > Don't know what file its looking for so I can't figure out how to fix >> it. >> > I've tried upgrading the package which worked, but didn't fix the >> > underlying issue. It must be super easy and obvious, but i don't know >> what >> > to look at. >> > >> > It was working until about 24 hours ago and no system level changes were >> > made since then. the last entries in the log were watchdog errors about >> > processes: >> > >> > Jan 18 03:04:51 sogod [1884]: [WARN] <0x0x557d83e4c8b0[WOWatchDogChild]> >> > pid 2326435 has been hanging in the same request for 2 minutes >> > Jan 18 03:04:53 sogod [2326435]: >> > <0x0x557d8445ba70[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while >> > detecting changes for user dee...@fifty50official.com in Ping... >> > Jan 18 03:05:23 sogod [2326435]: >> > <0x0x557d8445ba70[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while >> > detecting changes for user dee...@fifty50official.com in Ping... >> > Jan 18 03:05:51 sogod [1884]: [WARN] <0x0x557d83e4c8b0[WOWatchDogChild]> >> > pid 2326435 has been hanging iroot@truncheon:/var/log/sogo >> > >> > which I don't think are particularly serious, but I don't know. >> > >> > Thanks in advance! >> > >> >> >> -- >> Christian Mack >> Universität Konstanz >> Kommunikations-, Informations-, Medienzentrum (KIM) >> Abteilung IT-Dienste Forschung und Lehre >> 78457 Konstanz >> +49 7531 88-4416 >> >> > > -- > FF > -- FF -- users@sogo.nu https://inverse.ca/sogo/lists
