Hello
Am 04.07.2017 um 14:56 schrieb Jonathan Dumaresq (jdumar...@cimeq.qc.ca): > Hi all, > > I have upgraded our sogo to version 3.2.9 this morning and I started > receiving this king of email > > Cron <sogo@sogo> /usr/sbin/sogo-tool expire-sessions 30; > /usr/sbin/sogo-ealarms-notify > > with this content > > <0x0x1248680[SOGoProductLoader]> SOGo products loaded from > '/usr/lib/GNUstep/SOGo': > <0x0x1248680[SOGoProductLoader]> MailerUI.SOGo, AdministrationUI.SOGo, > PreferencesUI.SOGo, MainUI.SOGo, Mailer.SOGo, Appointments.SOGo, > ContactsUI.SOGo, MailPartViewers.SOGo, Contacts.SOGo, CommonUI.SOGo, > SchedulerUI.SOGo, ActiveSync.SOGo > See bug https://sogo.nu/bugs/view.php?id=4170 > In my log file I got this also > > Jul 04 08:53:28 sogod [1651]: [WARN] <0x0x559c8cfd4630[WOWatchDogChild]> > pid 1707 has been hanging in the same request for 3 minutes > Jul 04 08:53:28 sogod [1707]: > <0x0x559c8d417360[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while > detecting changes in Ping... > > The PID 1707 if looking like this > > 1707 /usr/sbin/sogod -WOworkersCount 10 > > After upgrading SOGO, I have restarted my server to be sure everything > is restarted. > You use ActiveSync. Therefore your ActiveSync clients keep an open connection to your SOGo server while pinging for changes. That also blocks one worker for each connection. Those messages are normal behaviour in this scenario. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature