0005553: MS Outlook 2016 with active Sync stops synchronizing and shows status disconnected - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0005553	SOGo Connector	with SOGo	public	2022-07-08 10:28	2023-08-02 08:25

Reporter	Colmar0	Assigned To	sebastien
Priority	normal	Severity	minor	Reproducibility	sometimes
Status	closed	Resolution	duplicate

Summary	0005553: MS Outlook 2016 with active Sync stops synchronizing and shows status disconnected
Description	Client: Windows 10 Sogo Server: Debian GNU/Linux 11 (bullseye) Sogo version: 5.7.0 Dovecot server: Debian GNU/Linux 10 (buster) MS Outlook version: 2016 with 32-Bit Outlook ost-file size: 1,83GByte MS Outlook with active sync stops synchronization when approximately 90% emails are down loaded and then stops the synchronization and MS Outlook show the error message "disconnected". Reset the the sogo cache with "sogo-tool manage-eas listdevices <user>" does not work anymore. Problem exist also in other previous version of Sogo. Problem seems to stop in the version 5.6.0. In all Sogo versions before the problem could be solved mostly by recreating the complete active sync account in Outlook. Problem seems to appear sporadically on different Windows clients with MS Outlook 2016 and active sync. MS Outlook PST-repair tool "C:\Program Files (x86)\Microsoft Office\Office16\SCANPST.EXE" does not solve the problem. Only the new creation of the whole Outlook account solve the problem. Sogo server syslog show following error message: Jul 6 13:01:56 sogo1 kernel: [540939.953826] sogod[121988]: segfault at 10 ip 00007f2575076713 sp 00007fff724f3190 error 4 in Mailer[7f257504a000+36000] Jul 6 13:01:56 sogo1 kernel: [540939.953836] Code: 8b 45 90 48 05 88 00 00 00 48 89 45 b8 c6 45 8f 00 c6 45 8e 01 80 7d 8f 00 0f 84 86 00 00 00 48 8b 45 b8 48 8b 00 48 83 c0 10 <8b It's unclear where is coming this error message and if this error message is related with the problem or not.
Tags	active sync

Colmar0 2022-10-07 07:09 reporter ~0016267	The "/var/log/sogo/sogo.log" shows following error message: Oct 06 10:01:55 sogod [300679]: <0x0x558b7bc4d3b0[SOGoActiveSyncDispatcher]> Cache cleanup needed for device 93E59085674644A1B75134B006E68485 - user: unsername syncKey: 3177-7914 cache: 3197-7914 After reseting the ActiveSync Cache with "sogo-tool manage-eas resetdevice unsername 93E59085674644A1B75134B006E68485" Outlook 2016 recreate all emails and show new emails, but stops synchronizing after a very short time. sogo.conf (4,172 bytes) { SOGoEASDebugEnabled = NO; MySQL4DebugEnabled = NO; OCSFolderManagerSQLDebugEnabled = NO; GCSFolderManagerSQLDebugEnabled = NO; GCSFolderStoreDebugEnabled = NO; WOListenQueueSize = 60; WOWorkersCount = 100; WOWatchDogRequestTimeout = 59; SOGoMaximumSyncWindowSize = 60; SOGoMaximumSyncResponseSize = 5172; SxVMemLimit = 512; MySQL4Encoding = "utf8mb4"; OCSEMailAlarmsFolderURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_alarms_folder"; OCSFolderInfoURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_folder_info"; OCSCacheFolderURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_cache_folder"; OCSStoreURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_store"; OCSAclURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_acl"; OCSSessionsFolderURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_sessions_folder"; SOGoMaximumPingInterval = 1140; SOGoMaximumSyncInterval = 1140; SOGoInternalSyncInterval = 120; SOGoCacheCleanupInterval = 900; SOGoFailedLoginBlockInterval = 120; SOGoACLsSendEMailNotifications = NO; SOGoAppointmentSendEMailNotifications = YES; SOGoDraftsFolderName = Drafts; SOGoEnableEMailAlarms = YES; SOGoEnablePublicAccess = YES; SOGoFirstDayOfWeek = 1; SOGoFoldersSendEMailNotifications = NO; SOGoForwardEnabled = YES; SOGoIMAPAclConformsToIMAPExt = YES; SOGoIMAPServer = "imaps://mail.domain.de:993"; SOGoLanguage = German; SOGoMailAuxiliaryUserAccountsEnabled = "="; SOGoMailDomain = "domain.de"; SOGoMailShowSubscribedFoldersOnly = YES; SOGoMailingMechanism = smtp; SOGoMemcachedHost = "sogo1.subdomain.domain.de"; SOGoPageTitle = "Rechenzentrum"; SOGoProfileURL = "mysql://sogo:Bla@mysql1-int.subdomain.domain.de:3306/sogo/sogo_user_profile"; SOGoSMTPServer = "smtp.domain.de"; SOGoSentFolderName = Sent; SOGoSieveScriptsEnabled = YES; SOGoSieveServer = "sieve://localhost:4190"; SOGoSieveFolderEncoding = "UTF-8"; SOGoTimeZone = "Europe/Berlin"; SOGoTrashFolderName = Trash; SOGoHideSystemEMail = YES; SOGoSuperUsernames = ("asmobil"); SOGoCalendarDefaultRoles = ("PublicDAndTViewer", "ConfidentialDAndTViewer"); SOGoFirstWeekOfYear = "First4DayWeek"; SOGoUserSources = ( { CNFieldName = cn; IDFieldName = uid; MailFieldNames = ( mail, mailLocalAddress ); SearchFieldNames = ( sn, cn ); UIDFieldName = uid; baseDN = "ou=people,dc=domain.de,dc=de"; scope = "SUB"; MultipleBookingsFieldName = "Multiplebookings"; bindAsCurrentUser = YES; canAuthenticate = YES; displayName = "Adressen Rechnzentrum"; encryption = SSL; hostname = "ldaps://ldap.domain.de:636"; id = public; isAddressBook = NO; passwordPolicy = NO; type = ldap; }, { CNFieldName = cn; IDFieldName = uid; MailFieldNames = ( mail, ); SearchFieldNames = ( sn, cn ); UIDFieldName = uid; baseDN = "ou=people,dc=domain.de,dc=de"; scope = "SUB"; MultipleBookingsFieldName = "Multiplebookings"; bindAsCurrentUser = YES; canAuthenticate = NO; displayName = "Adressen Rechnzentrum"; encryption = SSL; hostname = "ldaps://ldap.domain.de:636"; id = public_addr; isAddressBook = YES; passwordPolicy = NO; type = ldap; }, { CNFieldName = cn; IDFieldName = cn; SearchFieldNames = ( cn ); UIDFieldName = cn; baseDN = "ou=group,dc=domain.de,dc=de"; bindDN = "uid=sogo,ou=ldap-user,ou=rz,dc=domain.de,dc=de"; bindPassword = "bla"; canAuthenticate = YES; bindAsCurrentUser = YES; displayName = "Gruppen Rechnzentrum"; encryption = SSL; hostname = "ldaps://ldap.domain.de:636"; id = Rechnzentrum_groups; isAddressBook = YES; passwordPolicy = NO; type = ldap; } ); SOGoVacationEnabled = YES; } sogo.conf (4,172 bytes)

Colmar0 2022-10-07 07:15 reporter ~0016268	We need a fast solution!

Colmar0 2022-12-01 06:28 reporter ~0016447	Still no response.

sebastien 2022-12-01 07:44 administrator ~0016448	You need to provide a backtrace according to https://www.sogo.nu/support/faq/how-do-i-debug-sogo.html otherwise this is not debuggable Sebastien

Colmar0 2022-12-01 10:12 reporter ~0016449	The problem is that this error only occurs with isolated users. An installation in the production environment is not so easily not possible. Using a single test machine may not even make the problem reproducible. Isn't there some other compromise for debugging? Would it be possible that there are table locks in the database, because e.g. certain "database commits" are executed too late, not at all or with a delay? The combination of Sogo server, Dovecot server and database server is implemented on three physically (virtual machines) separated servers. If there are latencies in the network transfer between these servers, could an incorrectly set database commit, for example, perhaps also lead to such an error? Has the Sogo application been designed or optimized and tested for the separation between Sogo, the email server (Dovecot) and the database server on different physically installed servers, located on different networks? Same text in German: Die Problematik ist, daß dieser Fehler nur bei vereinzelten Benutzern auftritt. Eine Installation in der Produktivumgebung ist nicht so ohne weiteres nicht möglich. Der Einsatz einer einzelnen Test Maschine wird das Problem unter Umständen gar nicht reproduzierbar machen. Gibt es nicht irgendeinen andern Kompromiß für die Fehlersuche? Wäre es möglich, daß es hier zu Table-Locks in der Datenbank kommt, da z.B. bestimmte „Datenbank-Commitments“ zu spät, gar nicht oder verzögert ausgeführt werden? Die Kombination Sogo-Server, Dovecot-Server und Datenbank-Server ist bei uns über drei physikalisch (Virtuelle Maschinen) getrennten Server umgesetzt. Kommt es zu Latenzzeiten in der Netzwerkübertragung zwischen diesen Servern, könnte z.B. ein falsch gesetztes Datenbank-Commitment z.B. vielleicht auch zu einem solchen Fehler führen? Ist denn die Sogo-Anwendung überhaupt für die Auftrennung zwischen Sogo, E-Mail-Server (Dovecot) und Datenbank-Server auf verschiedene physikalisch installierten Servern, in verschiedenen Netzen befindenden Servern ausgelegt worden bzw. ist es optimiert und getestet worden für ein solches Szenario?

sebastien 2022-12-01 10:48 administrator ~0016450 Last edited: 2022-12-01 10:48	Of course SOGo is designed to work with separated components (ie on several servers). This is mostly the case. Does this occurred often ? If it is always the same user, maybe you can provide another sogo instance with the same configuration (database, user source, smtp, dovecot) but with only 1 process (WOWorkersCount = 1), start in debugging mode and give the new url only to this sogo user.

Colmar0 2022-12-01 12:31 reporter ~0016451	We will try to run this test and provide the results. But to elaborate on my question, how robust is the above constellation when there are unexpected delays of the three mentioned servers regarding the execution time of their tasks or when there are unscheduled short-time faulty network dropouts or latencies? Same text in German: Wir werden versuchen, diesen Test durch zu führen und die Ergebnisse zu liefern. Aber um meine Frage noch zu vertiefen, wie Robust ist die oben genannte Konstellation, wenn es zu unerwarteten Verzögerungen der drei genannten Server bezüglich der Ausführungszeit ihrer Aufgaben kommt oder wenn es zu unplanmäßigen kurzeitigen fehlerhaften Netzwerk Aussetzern oder Latenzen kommt?

sebastien 2022-12-01 13:21 administrator ~0016452	As far as I know, db and imap request are synchronous. Your database (postegresql or mariadb) is transactionnal and no concurrency access can occured. Why do you think the issue can be related to connection / timeout ? Do you monitor server resources ?

Colmar0 2022-12-02 06:01 reporter ~0016453	We monitor the Sogo, Dovecot and database servers via Zabbix. There are no particular anomalies to be found there in this regard. Same text in German: Wir überwachen die Sogo-, Dovecot- und Datenbank-Server über Zabbix. Dort sind keinerlei besondere Auffälligkeiten diesbezüglich zu finden.

Colmar0 2022-12-12 11:13 reporter ~0016481	Now we have created a server clone for further error analysis, with different hostname u. IP address. Currently I have the problem that when installing the debugging components via "apt-get install libgnustep-base-dbg sogo-dbg sope4.9-dbg gdb" the "libgnustep-base-dbg" installation package is not found. We are using the following Debian version on this server: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Which installation package must be used for this? Same text in German: Jetzt haben wir für die weitere Fehleranalyse eine Server-Klone erstellt, mit anderem Hostnamen u. IP-Adresse. Momentan habe ich das Problem, daß bei der Installation der Debugging Komponenten über „apt-get install libgnustep-base-dbg sogo-dbg sope4.9-dbg gdb“ das „libgnustep-base-dbg“ Installationspaket nicht gefunden wird. Wir verwenden auf diesem Server folgende Debian Version: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Welches Installationspaket muß hierfür verwendet werden?

Colmar0 2022-12-13 14:59 reporter ~0016496	The solution described here: https://bugs.sogo.nu/view.php?id=5405 , unfortunately also does not work for all three mentioned debugging packages with Debian 11. The following error message always appears after running "sudo apt update" with: apt-get install libgnustep-base-dbgsym sogo-dbg sope4.9-dbg gdb Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libgnustep-base-dbgsym Same text in German: Die Lösung die hier beschrieben wurde: https://bugs.sogo.nu/view.php?id=5405 , funktioniert leider auch nicht für alle drei genannten Debugging Pakete mit Debian 11. Es erscheint immer die folgende Fehlermeldung nach der Ausführung von „sudo apt update“ mit: apt-get install libgnustep-base-dbgsym sogo-dbg sope4.9-dbg gdb Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libgnustep-base-dbgsym

Colmar0 2022-12-14 06:57 reporter ~0016499	The installation of the "libgnustep-base" package has now worked with Debian 11 via "apt-get install libgnustep-base-dbg sogo-dbg sope4.9-dbg gdb". This should be added to "https://bugs.sogo.nu/view.php?id=5405". The installed package looks like this apt list libgnustep-base-dbg Listing... Done libgnustep-base1.27-dbgsym/stable-debug,now 1.27.0-3 amd64 [installed] I will find out the further debugging results with it. Same text in German: Die Installation des "libgnustep-base" Pakets hat jetzt mit Debian 11 über "apt-get install libgnustep-base-dbg sogo-dbg sope4.9-dbg gdb" funktioniert. Das sollte ggf. in "https://bugs.sogo.nu/view.php?id=5405" ergänzt werden. Das installierte Paket sieht dann so aus: apt list libgnustep-base-dbg Listing... Done libgnustep-base1.27-dbgsym/stable-debug,now 1.27.0-3 amd64 [installed] Die weiteren Debugging Ergebnisse damit werde ich noch ermitteln.

Colmar0 2023-01-12 11:07 reporter ~0016541	Here are the debugging results: Same text in German: Hier sind die Debugging Ergebnisse: Breakpoint 1, -[NSException raise] (self=0x55555617c370, _cmd=0x7ffff770fa40 <_OBJC_SELECTOR_TABLE+512>) at NSException.m:1574 1574 in NSException.m (gdb) Continuing. Jan 12 08:59:48 sogod [2843]: <0x0x5555555c6080[LDAPSource]> <NSException: 0x55555617c370> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{"error_code" = 49; login = "cn=bidmon,ou=group,dc=MyDomain,dc=de"; } Jan 12 08:59:49 sogod [2843]: <0x0x5555566a6440[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:00:00 sogod [2843]: <0x0x5555565f3da0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:00:38 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 5534103/4997 49.621 - - 56M - 13 Jan 12 09:01:06 sogod [2843]: <0x0x55555699b1a0[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:01:17 sogod [2843]: <0x0x5555564eb320[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:01:46 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 4890153/4998 44.796 - - 54M - 13 Jan 12 09:02:14 sogod [2843]: <0x0x5555567937b0[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:02:23 sogod [2843]: <0x0x555556775e00[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:05:17 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 21975001/4998 183.007 - - -9892K - 12 Jan 12 09:06:27 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 49/37 0.221 - - 0 - 12 Jan 12 09:06:27 sogod [2843]: <0x0x555557374740[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:06:29 sogod [2843]: <0x0x555556870270[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:07:49 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 16334614/4998 81.903 - - 89M - 12 Jan 12 09:09:36 sogod [2843]: <0x0x55555669fe40[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:09:38 sogod [2843]: <0x0x555556775e00[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:10:02 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 9761350/4998 30.124 - - 122M - 12 Jan 12 09:11:17 sogod [2843]: <0x0x55555674b9d0[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 12 09:11:20 sogod [2843]: <0x0x5555564d2c70[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Jan 12 09:15:41 sogod [2843]: 141.82.149.242 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 28449515/4998 264.812 - - 112M - 12 Breakpoint 1, -[NSException raise] (self=0x5555567f0490, _cmd=0x7ffff770fa40 <_OBJC_SELECTOR_TABLE+512>) at NSException.m:1574 1574 in NSException.m (gdb) bt #0 -[NSException raise] (self=0x5555567f0490, _cmd=0x7ffff770fa40 <_OBJC_SELECTOR_TABLE+512>) at NSException.m:1574 0000001 0x00007ffff76f83d3 in -[NGLdapConnection bindWithMethod:binddn:credentials:] (self=0x555557457670, _cmd=0x7ffff7fa3060 <_OBJC_SELECTOR_TABLE+736>, _method=0x7ffff7fa1200 <_OBJC_INSTANCE_56.85>, _login=0x5555561260c0, _cred=0x55555627f590) at NGLdapConnection.m:305 0000002 0x00007ffff7f15fb8 in -[LDAPSource checkLogin:password:perr:expire:grace:] (self=0x5555555c6080, _cmd=0x7ffff7f9df80 <_OBJC_SELECTOR_TABLE+768>, _login=0x5555560f84b0, _pwd=0x55555627f590, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at LDAPSource.m:630 0000003 0x00007ffff7f0e29d in -[SOGoUserManager _sourceCheckLogin:andPassword:domain:perr:expire:grace:] (self=0x555555e03ac0, _cmd=0x7ffff7f9e0b0 <_OBJC_SELECTOR_TABLE+1072>, login=0x5555560f84b0, password=0x55555627f590, domain=0x7fffffffbf50, perr=0x7fffffffbf4c, expire=0x7fffffffbf48, grace=0x7fffffffbf44) at SOGoUserManager.m:522 0000004 0x00007ffff7f0ec61 in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:useCache:] (self=0x555555e03ac0, _cmd=0x7ffff7f9dfa0 <_OBJC_SELECTOR_TABLE+800>, _login=0x5555560f84b0, _pwd=0x55555627f590, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44, useCache=1 '\001') at SOGoUserManager.m:687 0000005 0x00007ffff7f0e4cb in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:] (self=0x555555e03ac0, _cmd=0x7ffff7fb74d0 <_OBJC_SELECTOR_TABLE+48>, _login=0x5555560f84b0, _pwd=0x55555627f590, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at SOGoUserManager.m:564 0000006 0x00007ffff7f36884 in -[SOGoDAVAuthenticator checkLogin:password:] (self=0x555555de47b0, _cmd=0x7ffff7b93f10 <_OBJC_SELECTOR_TABLE+496>, _login=0x5555560f84b0, _pwd=0x55555627f590) at SOGoDAVAuthenticator.m:69 0000007 0x00007ffff7a4fe86 in -[SoHTTPAuthenticator preprocessCredentialsInContext:] (self=0x555555de47b0, _cmd=0x7ffff7b97f60 <_OBJC_SELECTOR_TABLE+1408>, _ctx=0x555556ca6bb0) at SoHTTPAuthenticator.m:272 0000008 0x00007ffff7a5665f in -[SoObjectRequestHandler handleRequest:inContext:session:application:] (self=0x555555a8dd40, _cmd=0x7ffff7b18c30 <_OBJC_SELECTOR_TABLE+848>, _rq=0x5555563170d0, _ctx=0x555556ca6bb0, _sn=0x0, app=0x555555984130) at SoObjectRequestHandler.m:537 0000009 0x00007ffff79e0c7a in -[WORequestHandler handleRequest:] (self=0x555555a8dd40, _cmd=0x7ffff7ae11b0 <_OBJC_SELECTOR_TABLE+1616>, _request=0x5555563170d0) at WORequestHandler.m:240 0000010 0x00007ffff79a3661 in -[WOCoreApplication dispatchRequest:usingHandler:] (self=0x555555984130, _cmd=0x7ffff7ae1200 <_OBJC_SELECTOR_TABLE+1696>, _request=0x5555563170d0, handler=0x555555a8dd40) at WOCoreApplication.m:712 0000011 0x00007ffff79a3969 in -[WOCoreApplication dispatchRequest:] (self=0x555555984130, _cmd=0x5555555665c0 <_OBJC_SELECTOR_TABLE+1664>, _request=0x5555563170d0) at WOCoreApplication.m:752 0000012 0x000055555555d45b in -[SOGo dispatchRequest:] (self=0x555555984130, _cmd=0x7ffff7b7f180 <_OBJC_SELECTOR_TABLE+1760>, _request=0x5555563170d0) at SOGo.m:584 0000013 0x00007ffff7a45622 in -[WOHttpTransaction _run] (self=0x555556311bb0, _cmd=0x7ffff7b7f1b0 <_OBJC_SELECTOR_TABLE+1808>) at WOHttpTransaction.m:566 0000014 0x00007ffff7a45982 in -[WOHttpTransaction run] (self=0x555556311bb0, _cmd=0x7ffff7b7ceb0 <_OBJC_SELECTOR_TABLE+1168>) at WOHttpTransaction.m:619 0000015 0x00007ffff7a418a9 in -[WOHttpAdaptor runConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf50 <_OBJC_SELECTOR_TABLE+1328>, _socket=0x555556581b80) at WOHttpAdaptor.m:373 0000016 0x00007ffff7a41ab5 in -[WOHttpAdaptor _handleAcceptedConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf60 <_OBJC_SELECTOR_TABLE+1344>, _connection=0x555556581b80) at WOHttpAdaptor.m:407 0000017 0x00007ffff7a41ead in -[WOHttpAdaptor _handleConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7d000 <_OBJC_SELECTOR_TABLE+1504>, connection=0x555556581b80) at WOHttpAdaptor.m:466 0000018 0x00007ffff7a422fe in -[WOHttpAdaptor acceptConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7ce70 <_OBJC_SELECTOR_TABLE+1104>, _notification=0x555556670510) at WOHttpAdaptor.m:527 0000019 0x00007ffff70e9604 in -[NSNotificationCenter _postAndRelease:] (self=0x555555738430, _cmd=<optimized out>, notification=0x555556670510) at NSNotificationCenter.m:1198 0000020 0x00007ffff75fd8e4 in -[NSObject(FileObjectWatcher) receivedEvent:type:extra:forMode:] (self=0x555555bf1e40, _cmd=0x7ffff74bc550 <_OBJC_SELECTOR_TABLE+304>, _fdData=0x5, _type=ET_RDESC, _extra=0x5, _mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>) at NSRunLoop+FileObjects.m:58 0000021 0x00007ffff721198b in -[GSRunLoopCtxt pollUntil:within:] (self=<optimized out>, _cmd=0x7ffff7437ee0 <_OBJC_SELECTOR_TABLE+1184>, milliseconds=<optimized out>, contexts=0x555555ac40f0) at GSRunLoopCtxt.m:600 0000022 0x00007ffff713afde in -[NSRunLoop acceptInputForMode:beforeDate:] (self=0x5555559e9a20, _cmd=0x7ffff7437f10 <_OBJC_SELECTOR_TABLE+1232>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, limit_date=0x5555565ad4f0) at NSRunLoop.m:1238 0000023 0x00007ffff713ad74 in -[NSRunLoop runMode:beforeDate:] (self=0x5555559e9a20, _cmd=<optimized out>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, date=0x5555565ad4f0) at NSRunLoop.m:1318 0000024 0x00007ffff79a2ec8 in -[WOCoreApplication run] (self=0x555555984130, _cmd=0x555555566320 <_OBJC_SELECTOR_TABLE+992>) at WOCoreApplication.m:584 0000025 0x000055555555c664 in -[SOGo run] (self=0x555555984130, _cmd=0x7ffff7b03eb0 <_OBJC_SELECTOR_TABLE+208>) at SOGo.m:337 0000026 0x00007ffff79cbf95 in WOApplicationMain (_appClassName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOApplicationMain.m:42 0000027 0x00007ffff79ebe04 in WOWatchDogApplicationMain (appName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOWatchDogApplicationMain.m:1049 0000028 0x000055555555b2fe in main (argc=13, argv=0x7fffffffec48, env=0x7fffffffecb8) at sogod.m:51 After entering "bt", the process does not continue and following message appears: In German: Nach dem Eingeben von "bt" mit anschließendem Drücken der Eingabetaste erscheint folgende Meldung: (gdb) bt #0 0x00007ffff6c89fb3 in __libc_write (fd=8, buf=0x555557218be3, nbytes=29) at ../sysdeps/unix/sysv/linux/write.c:26 0000001 0x00007ffff6217158 in ?? () from /lib/x86_64-linux-gnu/liblber-2.4.so.2 0000002 0x00007ffff5f7b69b in ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 0000003 0x00007ffff5f7c547 in ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 0000004 0x00007ffff5f726db in ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 0000005 0x00007ffff5f75ab0 in gnutls_record_send2 () from /lib/x86_64-linux-gnu/libgnutls.so.30 0000006 0x00007ffff6259b92 in ?? () from /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 0000007 0x00007ffff6217158 in ?? () from /lib/x86_64-linux-gnu/liblber-2.4.so.2 0000008 0x00007ffff62183a1 in ber_int_sb_write () from /lib/x86_64-linux-gnu/liblber-2.4.so.2 0000009 0x00007ffff6214b13 in ber_flush2 () from /lib/x86_64-linux-gnu/liblber-2.4.so.2 0000010 0x00007ffff623c465 in ldap_send_unbind () from /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 0000011 0x00007ffff6244f18 in ldap_free_connection () from /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 0000012 0x00007ffff623bf9f in ldap_ld_free () from /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 0000013 0x00007ffff76f7d5d in -[NGLdapConnection dealloc] (self=0x555557457670, _cmd=0x7ffff74144f0 <_OBJC_SELECTOR_TABLE+48>) at NGLdapConnection.m:156 0000014 0x00007ffff7f1607a in -[LDAPSource checkLogin:password:perr:expire:grace:] (self=0x5555555c6080, _cmd=0x7ffff7f9df80 <_OBJC_SELECTOR_TABLE+768>, _login=0x5555560f84b0, _pwd=0x55555627f590, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at LDAPSource.m:652 0000015 0x00007ffff7f0e29d in -[SOGoUserManager _sourceCheckLogin:andPassword:domain:perr:expire:grace:] (self=0x555555e03ac0, _cmd=0x7ffff7f9e0b0 <_OBJC_SELECTOR_TABLE+1072>, login=0x5555560f84b0, password=0x55555627f590, domain=0x7fffffffbf50, perr=0x7fffffffbf4c, expire=0x7fffffffbf48, grace=0x7fffffffbf44) at SOGoUserManager.m:522 0000016 0x00007ffff7f0ec61 in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:useCache:] (self=0x555555e03ac0, _cmd=0x7ffff7f9dfa0 <_OBJC_SELECTOR_TABLE+800>, _login=0x5555560f84b0, _pwd=0x55555627f590, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44, useCache=1 '\001') at SOGoUserManager.m:687 0000017 0x00007ffff7f0e4cb in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:] (self=0x555555e03ac0, _cmd=0x7ffff7fb74d0 <_OBJC_SELECTOR_TABLE+48>, _login=0x5555560f84b0, _pwd=0x55555627f590, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at SOGoUserManager.m:564 0000018 0x00007ffff7f36884 in -[SOGoDAVAuthenticator checkLogin:password:] (self=0x555555de47b0, _cmd=0x7ffff7b93f10 <_OBJC_SELECTOR_TABLE+496>, _login=0x5555560f84b0, _pwd=0x55555627f590) at SOGoDAVAuthenticator.m:69 0000019 0x00007ffff7a4fe86 in -[SoHTTPAuthenticator preprocessCredentialsInContext:] (self=0x555555de47b0, _cmd=0x7ffff7b97f60 <_OBJC_SELECTOR_TABLE+1408>, _ctx=0x555556ca6bb0) at SoHTTPAuthenticator.m:272 0000020 0x00007ffff7a5665f in -[SoObjectRequestHandler handleRequest:inContext:session:application:] (self=0x555555a8dd40, _cmd=0x7ffff7b18c30 <_OBJC_SELECTOR_TABLE+848>, _rq=0x5555563170d0, _ctx=0x555556ca6bb0, _sn=0x0, app=0x555555984130) at SoObjectRequestHandler.m:537 0000021 0x00007ffff79e0c7a in -[WORequestHandler handleRequest:] (self=0x555555a8dd40, _cmd=0x7ffff7ae11b0 <_OBJC_SELECTOR_TABLE+1616>, _request=0x5555563170d0) at WORequestHandler.m:240 0000022 0x00007ffff79a3661 in -[WOCoreApplication dispatchRequest:usingHandler:] (self=0x555555984130, _cmd=0x7ffff7ae1200 <_OBJC_SELECTOR_TABLE+1696>, _request=0x5555563170d0, handler=0x555555a8dd40) at WOCoreApplication.m:712 0000023 0x00007ffff79a3969 in -[WOCoreApplication dispatchRequest:] (self=0x555555984130, _cmd=0x5555555665c0 <_OBJC_SELECTOR_TABLE+1664>, _request=0x5555563170d0) at WOCoreApplication.m:752 0000024 0x000055555555d45b in -[SOGo dispatchRequest:] (self=0x555555984130, _cmd=0x7ffff7b7f180 <_OBJC_SELECTOR_TABLE+1760>, _request=0x5555563170d0) at SOGo.m:584 0000025 0x00007ffff7a45622 in -[WOHttpTransaction _run] (self=0x555556311bb0, _cmd=0x7ffff7b7f1b0 <_OBJC_SELECTOR_TABLE+1808>) at WOHttpTransaction.m:566 0000026 0x00007ffff7a45982 in -[WOHttpTransaction run] (self=0x555556311bb0, _cmd=0x7ffff7b7ceb0 <_OBJC_SELECTOR_TABLE+1168>) at WOHttpTransaction.m:619 0000027 0x00007ffff7a418a9 in -[WOHttpAdaptor runConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf50 <_OBJC_SELECTOR_TABLE+1328>, _socket=0x555556581b80) at WOHttpAdaptor.m:373 0000028 0x00007ffff7a41ab5 in -[WOHttpAdaptor _handleAcceptedConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf60 <_OBJC_SELECTOR_TABLE+1344>, _connection=0x555556581b80) at WOHttpAdaptor.m:407 0000029 0x00007ffff7a41ead in -[WOHttpAdaptor _handleConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7d000 <_OBJC_SELECTOR_TABLE+1504>, connection=0x555556581b80) at WOHttpAdaptor.m:466 0000030 0x00007ffff7a422fe in -[WOHttpAdaptor acceptConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7ce70 <_OBJC_SELECTOR_TABLE+1104>, _notification=0x555556670510) at WOHttpAdaptor.m:527 0000031 0x00007ffff70e9604 in -[NSNotificationCenter _postAndRelease:] (self=0x555555738430, _cmd=<optimized out>, notification=0x555556670510) at NSNotificationCenter.m:1198 0000032 0x00007ffff75fd8e4 in -[NSObject(FileObjectWatcher) receivedEvent:type:extra:forMode:] (self=0x555555bf1e40, _cmd=0x7ffff74bc550 <_OBJC_SELECTOR_TABLE+304>, _fdData=0x5, _type=ET_RDESC, _extra=0x5, _mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>) at NSRunLoop+FileObjects.m:58 --Type <RET> for more, q to quit, c to continue without paging--c 0000033 0x00007ffff721198b in -[GSRunLoopCtxt pollUntil:within:] (self=<optimized out>, _cmd=0x7ffff7437ee0 <_OBJC_SELECTOR_TABLE+1184>, milliseconds=<optimized out>, contexts=0x555555ac40f0) at GSRunLoopCtxt.m:600 0000034 0x00007ffff713afde in -[NSRunLoop acceptInputForMode:beforeDate:] (self=0x5555559e9a20, _cmd=0x7ffff7437f10 <_OBJC_SELECTOR_TABLE+1232>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, limit_date=0x5555565ad4f0) at NSRunLoop.m:1238 0000035 0x00007ffff713ad74 in -[NSRunLoop runMode:beforeDate:] (self=0x5555559e9a20, _cmd=<optimized out>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, date=0x5555565ad4f0) at NSRunLoop.m:1318 0000036 0x00007ffff79a2ec8 in -[WOCoreApplication run] (self=0x555555984130, _cmd=0x555555566320 <_OBJC_SELECTOR_TABLE+992>) at WOCoreApplication.m:584 0000037 0x000055555555c664 in -[SOGo run] (self=0x555555984130, _cmd=0x7ffff7b03eb0 <_OBJC_SELECTOR_TABLE+208>) at SOGo.m:337 0000038 0x00007ffff79cbf95 in WOApplicationMain (_appClassName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOApplicationMain.m:42 0000039 0x00007ffff79ebe04 in WOWatchDogApplicationMain (appName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOWatchDogApplicationMain.m:1049 0000040 0x000055555555b2fe in main (argc=13, argv=0x7fffffffec48, env=0x7fffffffecb8) at sogod.m:51 The synchronization stops after reaching the breakpoint with the error message "NSException". The error message "NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{"error_code" = 49; login = "cn=bidmon,ou=group,dc=MyDomain,dc=en"" appears probably because the specified user "bidmon" does not exist in the LDAP group "cn=bidmon,ou=group,dc=MyDomain,dc=en", which was defined in "baseDN = "ou=group,dc=domain.de,dc=en"" but instead was defined in "baseDN = "ou=people,dc=domain.de,dc=en"". In the latter "baseDN" also the specified user "bidmon" exists many users also only in the "baseDN = "ou=people,dc=domain.de,dc=de" to find. Same text in German: Die Synchronisation stoppt nach dem Erreichen des Breakpoints mit der Fehlermeldung "NSException". Die Fehlermeldung "NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{"error_code" = 49; login = "cn=bidmon,ou=group,dc=MyDomain,dc=de"" erscheint wohl, weil der angegebenen Benutzer "bidmon" nicht in der LDAP-Gruppe "cn=bidmon,ou=group,dc=MyDomain,dc=de" existiert, die in "baseDN = "ou=group,dc=domain.de,dc=de"" definiert wurde, aber dafür in "baseDN = "ou=people,dc=domain.de,dc=de"". In der letztgenannten "baseDN" existiert auch der angegebene Benutzer "bidmon" vielen Benutzern auch nur in der "baseDN = "ou=people,dc=domain.de,dc=de"" zu finden sind.

Colmar0 2023-01-12 11:12 reporter ~0016542	However, for the most ActiveSync users works this binding for LDAP for the LDAP user search. Same text in German: Aber für die meisten ActiveSync funktioniert diese Bindungs Angabe für die LDAP-Benutzersuche.

Colmar0 2023-01-13 11:54 reporter ~0016546	Addendum: After the error occurred, the process could not be continued via "(gdb) c" and is terminated. Outlook indicated that it was not connected and the synchronization stopped. Today, the next day, the ActiveSync synchronization continues again, but with different process IDs. It usually continues until the Outlook .ost file has reached nearly its full size (about 2GByte). Then at some point the synchronization stops completely and Outlook remains in the status "Disconnected". The only way to restart the synchronization is to delete the entire Outlook e-mail account (profile) with the associated .ost file and reinstalling it. The same game then continues again. At the moment there are several processes running for Sogo & I don't know how to "hook" into the last process point with (gdb). Same text in German: Nachtrag: Nachdem der Fehler aufgetreten ist, konnte der Prozeß nicht mehr fortgesetzt werden über „(gdb) c“ und ist abgebrochen. Outlook zeige an, daß es nicht verbunden sei und die Synchronisation stoppte. Heute am nächsten Tag, läuft die ActiveSync Synchronisation zwar wieder weiter, aber mit anderen Prozeß-IDs. Die geht meist so lange weiter, bis die Outlook .ost Datei annähernd seine volle Größe (ca. 2GByte) erreicht hat. Dann kommt irgendwann der Punkt, daß die Synchronisation vollständig aufhört und Outlook im Status „Disconnected“ verbleibt. Das Ganze läßt sich dann nur noch dadurch in Gang setzen, in dem man das gesamte Outlook E-Mail Konto löscht mit zugehöriger .ost Datei und neu installiert. Das gleiche Spiel läuft dann erneut so weiter. Momentan laufen mehrere Prozesse für Sogo u. ich weiß nicht, wie ich mich in den letzten Prozeßpunkt „einhängen“ kann mit (gdb). Actual Sogo Processes /aktuelle Sogo Prozesse: sogo@sogo-debug:~$ ps auxw USER PID %CPU %MEM VSZ RSS TTY sogo 757 0.0 0.1 96368 26792 ? sogo 759 0.0 0.1 98680 28028 ? sogo 760 0.0 0.1 98680 28020 ? sogo 761 0.0 0.1 98680 28140 ? sogo 762 0.0 0.1 98680 28180 ? sogo 763 0.0 0.1 98680 28180 ? sogo 764 0.0 0.1 98680 28180 ? sogo 765 0.0 0.1 98680 28180 ? sogo 766 0.0 0.1 98680 28180 ? sogo 767 0.0 0.1 98680 28180 ? sogo 768 0.0 0.1 98680 28180 ? sogo 769 0.0 0.1 98680 28180 ? sogo 770 0.0 0.1 98680 28180 ? sogo 771 0.0 0.1 98680 28180 ? sogo 772 0.0 0.1 98680 28180 ? sogo 773 0.0 0.1 98680 28180 ? sogo 774 0.0 0.1 98680 28180 ? sogo 775 0.0 0.1 98680 28180 ? sogo 776 0.0 0.1 98680 28180 ? sogo 777 0.0 0.1 98680 28180 ? sogo 778 0.0 0.1 98680 28180 ? sogo 779 0.0 0.1 98680 28180 ? sogo 780 0.0 0.1 98680 28180 ? sogo 781 0.0 0.1 98680 28184 ? sogo 782 0.0 0.1 98680 28188 ? sogo 783 0.0 0.1 98680 28188 ? sogo 784 0.0 0.1 98680 28188 ? sogo 785 0.0 0.1 98680 28188 ? sogo 786 0.0 0.1 98680 28188 ? sogo 787 0.0 0.1 98680 28184 ? sogo 788 0.0 0.1 98680 28188 ? sogo 789 0.0 0.1 98680 28188 ? sogo 790 0.0 0.1 98680 28188 ? sogo 791 0.0 0.1 98680 28188 ? sogo 794 0.0 0.1 98680 28188 ? sogo 796 0.0 0.1 98680 28188 ? sogo 797 0.0 0.1 98680 28188 ? sogo 798 0.0 0.1 98680 28188 ? sogo 799 0.0 0.1 98680 28188 ? sogo 800 0.0 0.1 98680 28156 ? sogo 801 0.0 0.1 98680 28192 ? sogo 802 0.0 0.1 98680 28188 ? sogo 803 0.0 0.1 98680 28188 ? sogo 804 0.0 0.1 98680 28188 ? sogo 805 0.0 0.1 98680 28188 ? sogo 806 0.0 0.1 98680 28188 ? sogo 807 0.0 0.1 98680 28188 ? sogo 808 0.0 0.1 98680 28188 ? sogo 809 0.0 0.1 98680 28188 ? sogo 810 0.0 0.1 98680 28188 ? sogo 811 0.0 0.1 98680 28188 ? sogo 812 0.0 0.1 98680 28188 ? sogo 813 0.0 0.1 98680 28180 ? sogo 814 0.0 0.1 98680 28188 ? sogo 815 0.0 0.1 98680 28188 ? sogo 816 0.0 0.1 98680 28188 ? sogo 817 0.0 0.1 98680 28188 ? sogo 818 0.0 0.1 98680 28188 ? sogo 819 0.0 0.1 98680 28188 ? sogo 820 0.0 0.1 98680 28188 ? sogo 821 0.0 0.1 98680 28188 ? sogo 822 0.0 0.1 98680 28188 ? sogo 823 0.0 0.1 98680 28188 ? sogo 824 0.0 0.1 98680 28188 ? sogo 825 0.0 0.1 98680 28188 ? sogo 826 0.0 0.1 98680 28188 ? sogo 827 0.0 0.1 98680 27896 ? sogo 828 0.0 0.1 98680 27964 ? sogo 829 0.0 0.1 98680 28188 ? sogo 830 0.0 0.1 98680 28188 ? sogo 831 0.0 0.1 98680 28188 ? sogo 832 0.0 0.1 98680 28188 ? sogo 833 0.2 0.9 260792 194976 ? sogo 834 0.0 0.1 98680 28188 ? sogo 835 0.0 0.1 98680 28188 ? sogo 836 0.0 0.1 98680 28188 ? sogo 837 0.0 0.1 98680 28188 ? sogo 838 0.0 0.1 98680 28188 ? sogo 839 0.0 0.1 98680 28188 ? sogo 840 0.0 0.1 98680 28188 ? sogo 841 0.0 0.1 98680 28188 ? root 1749 0.0 0.0 21520 5004 pts/0 sogo 1750 0.0 0.0 7164 3864 pts/0 sogo 1876 0.0 0.0 18852 3492 pts/0 sogo 1877 0.0 0.0 6244 708 pts/0 STAT START TIME COMMAND S 03:18 0:13 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:33 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log Ss 03:18 0:00 /usr/sbin/sogod -WOWorkersCount 80 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log S 06:59 0:00 su -s /bin/bash - sogo S 06:59 0:00 -bash R+ 07:25 0:00 ps auxw S+ 07:25 0:00 grep -E sogo Possible causes for the behavior: It seems that Sogo runs into an LDAP time-out during the LDAP search and each time after such a time-out a new process is started. With several hundred ActiveSync users, the Sogo system running ActiveSync may experience significant delays, perhaps simply caused by disconnections. LDAP users are stored in "baseDN = "ou=people,dc=domain.de,dc=de". So that one can search in the calendar also groups here "baseDN = "ou=group,dc=domain.de,dc=de"" is used. In the LDAP directory there are more than 10.000 user objects. In the "/var/log/sogo/sogo.log" file you can see very often the same LDAP queries for the same user. Same text in German: Mögliche Ursachen für das Verhalten: Es scheint so, als würde Sogo bei der LDAP-Suche in einen LDAP-Time-Out hineinlaufen und jedes Mal nach so einem Time-Out wird ein neuer Prozeß gestartet. Bei mehreren Hundert ActiveSync Benutzern, läuft sich das Sogo System mit ActiveSync kommt es möglicherweise zu erheblichen Verzögerungen vielleicht auch einfach nur verursacht durch Verbindungsabbrüche. LDAP-Benutzer werden in "baseDN = "ou=people,dc=domain.de,dc=de" gespeichert. Damit man im Kalender auch Gruppen suchen kann wird hier "baseDN = "ou=group,dc=domain.de,dc=de"" verwendet. In dem LDAP-Verzeichnis befinden sich mehr als 10.000 Benutzerobjekte. In der „/var/log/sogo/sogo.log“ Datei sieht man sehr häufig die gleichen LDAP Abfragen für den gleichen Benutzer.

Colmar0 2023-01-16 08:03 reporter ~0016548	Important additional information: The test machine used is a clone of a production machine with a modified host name. The process termination described above takes place on a test machine on which only one user is working! Same text in German: Wichtige Zusatz Information: Die verwendete Testmaschine ist ein Klone einer Produktivmaschine mit abgeändertem Host Namen. Der oben beschriebene Prozeßabbruch findet auf einer Testmaschine statt, auf der nur ein einziger Benutzer arbeitet!

Colmar0 2023-01-16 11:40 reporter ~0016552	MS Outlook (2016) synchronization has now stopped completely and Outlook shows the status "Disconnected". The .ost file has reached a size of 1.95 GB. Same text in German: Die MS Outlook (2016) Synchronisation hat nun vollständig gestoppt und Outlook zeigt den Status „Getrennt“ an. Die .ost Datei hat eine Größe von 1,95 GB erreicht. The essential error messages are: Same text in German: Die wesentlichen Fehlermeldungen sind: “Jan 16 03:18:01 sogod [756]: <0x0x561b17594c10[WOWatchDogChild]> sending terminate signal to pid 834 2023-01-16 03:18:01.907 sogod[840:840] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17594dc0[WOWatchDogChild]> sending terminate signal to pid 833” und “Jan 16 12:07:21 sogod [3431]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/view HTTP/1.1" 200 24607/0 0.055 94660 74% 3M - 13 Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: 141.82.146.66 "GET /SOGo/so/bidmon/Calendar/alarmslist?browserTime=1673867242 HTTP/1.1" 200 60/0 0.021 - - 0 - 13 Jan 16 12:07:22 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/0/folderINBOX/changes HTTP/1.1" 200 27/126 0.079 - - 0 - 13 Jan 16 12:07:22 sogod [3105]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/0/view HTTP/1.1" 200 6576/0 0.077 - - 0 - 13 Jan 16 12:07:23 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/0/folderINBOX/view HTTP/1.1" 200 99862/48 0.338 - - 3M - 14 Jan 16 12:07:24 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/unseenCount HTTP/1.1" 200 22/31 0.081 - - -1580K - 13 Jan 16 12:07:24 sogod [3105]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/0/folderINBOX/labels HTTP/1.1" 200 131/0 0.073 - - 0 - 14 Jan 16 12:07:33 sogod [3105]: 141.82.146.66 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 49/37 0.310 - - 11M - 13 Jan 16 12:07:38 sogod [3105]: <0x0x5627963c80e0[SOGoActiveSyncDispatcher]> Cache cleanup needed for device E2B7D5A65C234BDB8566EF3D73982ED7 - user: bidmon syncKey: 14491-42000 cache: 14491-42006 Jan 16 12:07:38 sogod [3105]: <0x0x5627964ce690[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:07:38 sogod [3105]: <0x0x5627964ce690[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:07:40 sogod [756]: <0x0x562795c5ea10[WOWatchDogChild]> child 3105 exited Jan 16 12:07:40 sogod [756]: <0x0x562795c5ea10[WOWatchDogChild]> (terminated due to signal 11) Jan 16 12:07:40 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 3432” An excerpt from the “/var/log/sogo/sogo.log” file. Same text in German: Ein Auszug aus der „/var/log/sogo/sogo.log“ Datei: /var/log/sogo/sogo.log: Jan 16 00:41:59 sogod [839]: 107.174.172.167 "GET /SOGo HTTP/1.1" 302 0/0 0.003 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo/ HTTP/1.1" 200 10607/0 0.017 37916 72% 0 - 11 Jan 16 02:39:48 sogod [839]: 167.94.138.63 "GET /SOGo HTTP/1.1" 302 0/0 0.002 - - 0 - 11 Jan 16 02:39:49 sogod [839]: 167.94.138.63 "GET /SOGo/ HTTP/1.1" 200 10608/0 0.011 37916 72% 0 - 11 Jan 16 03:18:01 sogod [756]: <0x0x561b174fd890[WOWatchDog]> Terminating with SIGINT or SIGTERM Jan 16 03:18:01 sogod [756]: <0x0x561b1764aa10[WOWatchDogChild]> sending terminate signal to pid 840 Jan 16 03:18:01 sogod [756]: <0x0x561b17645d30[WOWatchDogChild]> sending terminate signal to pid 839 Jan 16 03:18:01 sogod [756]: <0x0x561b17595650[WOWatchDogChild]> sending terminate signal to pid 838 Jan 16 03:18:01 sogod [756]: <0x0x561b1758a5d0[WOWatchDogChild]> sending terminate signal to pid 837 Jan 16 03:18:01 sogod [756]: <0x0x561b1758ba60[WOWatchDogChild]> sending terminate signal to pid 836 Jan 16 03:18:01 sogod [756]: <0x0x561b17594b30[WOWatchDogChild]> sending terminate signal to pid 835 Jan 16 03:18:01 sogod [756]: <0x0x561b17594c10[WOWatchDogChild]> sending terminate signal to pid 834 2023-01-16 03:18:01.907 sogod[840:840] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17594dc0[WOWatchDogChild]> sending terminate signal to pid 833 Jan 16 03:18:01 sogod [756]: <0x0x561b17594f70[WOWatchDogChild]> sending terminate signal to pid 832 Jan 16 03:18:01 sogod [756]: <0x0x561b17595370[WOWatchDogChild]> sending terminate signal to pid 831 2023-01-16 03:18:01.907 sogod[838:838] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17589cd0[WOWatchDogChild]> sending terminate signal to pid 830 Jan 16 03:18:01 sogod [756]: <0x0x561b17590830[WOWatchDogChild]> sending terminate signal to pid 829 Jan 16 03:18:01 sogod [756]: <0x0x561b17588fd0[WOWatchDogChild]> sending terminate signal to pid 828 Jan 16 03:18:01 sogod [756]: <0x0x561b175890b0[WOWatchDogChild]> sending terminate signal to pid 827 Jan 16 03:18:01 sogod [756]: <0x0x561b17589200[WOWatchDogChild]> sending terminate signal to pid 826 Jan 16 03:18:01 sogod [756]: <0x0x561b175893b0[WOWatchDogChild]> sending terminate signal to pid 825 Jan 16 03:18:01 sogod [756]: <0x0x561b175897b0[WOWatchDogChild]> sending terminate signal to pid 824 Jan 16 03:18:01 sogod [756]: <0x0x561b17589a90[WOWatchDogChild]> sending terminate signal to pid 823 Jan 16 03:18:01 sogod [756]: <0x0x561b17572650[WOWatchDogChild]> sending terminate signal to pid 822 Jan 16 03:18:01 sogod [756]: <0x0x561b17570fd0[WOWatchDogChild]> sending terminate signal to pid 821 Jan 16 03:18:01 sogod [756]: <0x0x561b175710d0[WOWatchDogChild]> sending terminate signal to pid 820 Jan 16 03:18:01 sogod [756]: <0x0x561b17571280[WOWatchDogChild]> sending terminate signal to pid 819 2023-01-16 03:18:01.907 sogod[839:839] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17571430[WOWatchDogChild]> sending terminate signal to pid 818 ... Jan 16 00:41:59 sogod [839]: 107.174.172.167 "GET /SOGo HTTP/1.1" 302 0/0 0.003 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo/ HTTP/1.1" 200 10607/0 0.017 37916 72% 0 - 11 Jan 16 02:39:48 sogod [839]: 167.94.138.63 "GET /SOGo HTTP/1.1" 302 0/0 0.002 - - 0 - 11 Jan 16 02:39:49 sogod [839]: 167.94.138.63 "GET /SOGo/ HTTP/1.1" 200 10608/0 0.011 37916 72% 0 - 11 Jan 16 03:18:01 sogod [756]: <0x0x561b174fd890[WOWatchDog]> Terminating with SIGINT or SIGTERM Jan 16 03:18:01 sogod [756]: <0x0x561b1764aa10[WOWatchDogChild]> sending terminate signal to pid 840 Jan 16 03:18:01 sogod [756]: <0x0x561b17645d30[WOWatchDogChild]> sending terminate signal to pid 839 Jan 16 03:18:01 sogod [756]: <0x0x561b17595650[WOWatchDogChild]> sending terminate signal to pid 838 Jan 16 03:18:01 sogod [756]: <0x0x561b1758a5d0[WOWatchDogChild]> sending terminate signal to pid 837 Jan 16 03:18:01 sogod [756]: <0x0x561b1758ba60[WOWatchDogChild]> sending terminate signal to pid 836 Jan 16 03:18:01 sogod [756]: <0x0x561b17594b30[WOWatchDogChild]> sending terminate signal to pid 835 Jan 16 03:18:01 sogod [756]: <0x0x561b17594c10[WOWatchDogChild]> sending terminate signal to pid 834 2023-01-16 03:18:01.907 sogod[840:840] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17594dc0[WOWatchDogChild]> sending terminate signal to pid 833 Jan 16 03:18:01 sogod [756]: <0x0x561b17594f70[WOWatchDogChild]> sending terminate signal to pid 832 Jan 16 03:18:01 sogod [756]: <0x0x561b17595370[WOWatchDogChild]> sending terminate signal to pid 831 2023-01-16 03:18:01.907 sogod[838:838] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17589cd0[WOWatchDogChild]> sending terminate signal to pid 830 Jan 16 03:18:01 sogod [756]: <0x0x561b17590830[WOWatchDogChild]> sending terminate signal to pid 829 Jan 16 03:18:01 sogod [756]: <0x0x561b17588fd0[WOWatchDogChild]> sending terminate signal to pid 828 Jan 16 03:18:01 sogod [756]: <0x0x561b175890b0[WOWatchDogChild]> sending terminate signal to pid 827 Jan 16 03:18:01 sogod [756]: <0x0x561b17589200[WOWatchDogChild]> sending terminate signal to pid 826 Jan 16 03:18:01 sogod [756]: <0x0x561b175893b0[WOWatchDogChild]> sending terminate signal to pid 825 Jan 16 03:18:01 sogod [756]: <0x0x561b175897b0[WOWatchDogChild]> sending terminate signal to pid 824 Jan 16 03:18:01 sogod [756]: <0x0x561b17589a90[WOWatchDogChild]> sending terminate signal to pid 823 Jan 16 03:18:01 sogod [756]: <0x0x561b17572650[WOWatchDogChild]> sending terminate signal to pid 822 Jan 16 03:18:01 sogod [756]: <0x0x561b17570fd0[WOWatchDogChild]> sending terminate signal to pid 821 Jan 16 03:18:01 sogod [756]: <0x0x561b175710d0[WOWatchDogChild]> sending terminate signal to pid 820 Jan 16 03:18:01 sogod [756]: <0x0x561b17571280[WOWatchDogChild]> sending terminate signal to pid 819 2023-01-16 03:18:01.907 sogod[839:839] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17571430[WOWatchDogChild]> sending terminate signal to pid 818 ... Jan 16 00:41:59 sogod [839]: 107.174.172.167 "GET /SOGo HTTP/1.1" 302 0/0 0.003 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo/ HTTP/1.1" 200 10607/0 0.017 37916 72% 0 - 11 Jan 16 02:39:48 sogod [839]: 167.94.138.63 "GET /SOGo HTTP/1.1" 302 0/0 0.002 - - 0 - 11 Jan 16 02:39:49 sogod [839]: 167.94.138.63 "GET /SOGo/ HTTP/1.1" 200 10608/0 0.011 37916 72% 0 - 11 Jan 16 03:18:01 sogod [756]: <0x0x561b174fd890[WOWatchDog]> Terminating with SIGINT or SIGTERM Jan 16 03:18:01 sogod [756]: <0x0x561b1764aa10[WOWatchDogChild]> sending terminate signal to pid 840 Jan 16 03:18:01 sogod [756]: <0x0x561b17645d30[WOWatchDogChild]> sending terminate signal to pid 839 Jan 16 03:18:01 sogod [756]: <0x0x561b17595650[WOWatchDogChild]> sending terminate signal to pid 838 Jan 16 03:18:01 sogod [756]: <0x0x561b1758a5d0[WOWatchDogChild]> sending terminate signal to pid 837 Jan 16 03:18:01 sogod [756]: <0x0x561b1758ba60[WOWatchDogChild]> sending terminate signal to pid 836 Jan 16 03:18:01 sogod [756]: <0x0x561b17594b30[WOWatchDogChild]> sending terminate signal to pid 835 Jan 16 03:18:01 sogod [756]: <0x0x561b17594c10[WOWatchDogChild]> sending terminate signal to pid 834 2023-01-16 03:18:01.907 sogod[840:840] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17594dc0[WOWatchDogChild]> sending terminate signal to pid 833 Jan 16 03:18:01 sogod [756]: <0x0x561b17594f70[WOWatchDogChild]> sending terminate signal to pid 832 Jan 16 03:18:01 sogod [756]: <0x0x561b17595370[WOWatchDogChild]> sending terminate signal to pid 831 2023-01-16 03:18:01.907 sogod[838:838] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17589cd0[WOWatchDogChild]> sending terminate signal to pid 830 Jan 16 03:18:01 sogod [756]: <0x0x561b17590830[WOWatchDogChild]> sending terminate signal to pid 829 Jan 16 03:18:01 sogod [756]: <0x0x561b17588fd0[WOWatchDogChild]> sending terminate signal to pid 828 Jan 16 03:18:01 sogod [756]: <0x0x561b175890b0[WOWatchDogChild]> sending terminate signal to pid 827 Jan 16 03:18:01 sogod [756]: <0x0x561b17589200[WOWatchDogChild]> sending terminate signal to pid 826 Jan 16 03:18:01 sogod [756]: <0x0x561b175893b0[WOWatchDogChild]> sending terminate signal to pid 825 Jan 16 03:18:01 sogod [756]: <0x0x561b175897b0[WOWatchDogChild]> sending terminate signal to pid 824 Jan 16 03:18:01 sogod [756]: <0x0x561b17589a90[WOWatchDogChild]> sending terminate signal to pid 823 Jan 16 03:18:01 sogod [756]: <0x0x561b17572650[WOWatchDogChild]> sending terminate signal to pid 822 Jan 16 03:18:01 sogod [756]: <0x0x561b17570fd0[WOWatchDogChild]> sending terminate signal to pid 821 Jan 16 03:18:01 sogod [756]: <0x0x561b175710d0[WOWatchDogChild]> sending terminate signal to pid 820 Jan 16 03:18:01 sogod [756]: <0x0x561b17571280[WOWatchDogChild]> sending terminate signal to pid 819 2023-01-16 03:18:01.907 sogod[839:839] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17571430[WOWatchDogChild]> sending terminate signal to pid 818 ... Jan 16 00:41:59 sogod [839]: 107.174.172.167 "GET /SOGo HTTP/1.1" 302 0/0 0.003 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Jan 16 00:51:49 sogod [839]: 167.94.138.60 "GET /SOGo/ HTTP/1.1" 200 10607/0 0.017 37916 72% 0 - 11 Jan 16 02:39:48 sogod [839]: 167.94.138.63 "GET /SOGo HTTP/1.1" 302 0/0 0.002 - - 0 - 11 Jan 16 02:39:49 sogod [839]: 167.94.138.63 "GET /SOGo/ HTTP/1.1" 200 10608/0 0.011 37916 72% 0 - 11 Jan 16 03:18:01 sogod [756]: <0x0x561b174fd890[WOWatchDog]> Terminating with SIGINT or SIGTERM Jan 16 03:18:01 sogod [756]: <0x0x561b1764aa10[WOWatchDogChild]> sending terminate signal to pid 840 Jan 16 03:18:01 sogod [756]: <0x0x561b17645d30[WOWatchDogChild]> sending terminate signal to pid 839 Jan 16 03:18:01 sogod [756]: <0x0x561b17595650[WOWatchDogChild]> sending terminate signal to pid 838 Jan 16 03:18:01 sogod [756]: <0x0x561b1758a5d0[WOWatchDogChild]> sending terminate signal to pid 837 Jan 16 03:18:01 sogod [756]: <0x0x561b1758ba60[WOWatchDogChild]> sending terminate signal to pid 836 Jan 16 03:18:01 sogod [756]: <0x0x561b17594b30[WOWatchDogChild]> sending terminate signal to pid 835 Jan 16 03:18:01 sogod [756]: <0x0x561b17594c10[WOWatchDogChild]> sending terminate signal to pid 834 2023-01-16 03:18:01.907 sogod[840:840] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17594dc0[WOWatchDogChild]> sending terminate signal to pid 833 Jan 16 03:18:01 sogod [756]: <0x0x561b17594f70[WOWatchDogChild]> sending terminate signal to pid 832 Jan 16 03:18:01 sogod [756]: <0x0x561b17595370[WOWatchDogChild]> sending terminate signal to pid 831 2023-01-16 03:18:01.907 sogod[838:838] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17589cd0[WOWatchDogChild]> sending terminate signal to pid 830 Jan 16 03:18:01 sogod [756]: <0x0x561b17590830[WOWatchDogChild]> sending terminate signal to pid 829 Jan 16 03:18:01 sogod [756]: <0x0x561b17588fd0[WOWatchDogChild]> sending terminate signal to pid 828 Jan 16 03:18:01 sogod [756]: <0x0x561b175890b0[WOWatchDogChild]> sending terminate signal to pid 827 Jan 16 03:18:01 sogod [756]: <0x0x561b17589200[WOWatchDogChild]> sending terminate signal to pid 826 Jan 16 03:18:01 sogod [756]: <0x0x561b175893b0[WOWatchDogChild]> sending terminate signal to pid 825 Jan 16 03:18:01 sogod [756]: <0x0x561b175897b0[WOWatchDogChild]> sending terminate signal to pid 824 Jan 16 03:18:01 sogod [756]: <0x0x561b17589a90[WOWatchDogChild]> sending terminate signal to pid 823 Jan 16 03:18:01 sogod [756]: <0x0x561b17572650[WOWatchDogChild]> sending terminate signal to pid 822 Jan 16 03:18:01 sogod [756]: <0x0x561b17570fd0[WOWatchDogChild]> sending terminate signal to pid 821 Jan 16 03:18:01 sogod [756]: <0x0x561b175710d0[WOWatchDogChild]> sending terminate signal to pid 820 Jan 16 03:18:01 sogod [756]: <0x0x561b17571280[WOWatchDogChild]> sending terminate signal to pid 819 2023-01-16 03:18:01.907 sogod[839:839] Forcing termination of EAS loop. Jan 16 03:18:01 sogod [756]: <0x0x561b17571430[WOWatchDogChild]> sending terminate signal to pid 818 ... Jan 16 03:18:33 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 789 Jan 16 03:18:33 sogod [766]: <0x0x562795ceb800[WOHttpAdaptor]> notified the watchdog that we are readyJan 16 03:18:33 sogod [758]: <0x0x562795ae51e0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [760]: <0x0x562795ec8620[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [761]: <0x0x562795cf7ef0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [759]: <0x0x562795ec8620[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [765]: <0x0x562795ced860[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [762]: <0x0x562795cf37c0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [768]: <0x0x562795ceb800[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [772]: <0x0x562795ce4ea0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [767]: <0x0x562795cec8f0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [770]: <0x0x562795ec8620[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 03:18:33 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 790 Jan 16 03:18:33 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 791 Jan 16 03:18:33 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 792 Jan 16 03:18:33 sogod [771]: <0x0x562795ce6010[WOHttpAdaptor]> notified the watchdog that we are ready ... Jan 16 12:06:54 sogod [3429]: <0x0x56279590e2b0[SOGoCache]> Cache cleanup interval set every 900.000000 seconds Jan 16 12:06:54 sogod [3429]: <0x0x56279590e2b0[SOGoCache]> Using host(s) 'sogo1.rz.Domain.de' as server(s) Jan 16 12:06:54 sogod [3429]: [WARN] <0x0x5627958c7170[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table Jan 16 12:06:54 sogod [3429]: [WARN] <0x0x5627958c7170[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table Jan 16 12:06:54 sogod [3429]: [WARN] <0x0x5627958c7170[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table Jan 16 12:06:54 sogod [3429]: 141.82.146.66 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 49/37 0.324 - - 20M - 12 Jan 16 12:06:55 sogod [3429]: <0x0x562795cee2d0[SOGoActiveSyncDispatcher]> Cache cleanup needed for device E2B7D5A65C234BDB8566EF3D73982ED7 - user: bidmon syncKey: 14491-42000 cache: 14491-42006 Jan 16 12:06:55 sogod [3429]: <0x0x562795917900[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:06:55 sogod [3429]: <0x0x562795917900[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:06:56 sogod [756]: <0x0x562795c59d30[WOWatchDogChild]> child 3429 exited Jan 16 12:06:56 sogod [756]: <0x0x562795c59d30[WOWatchDogChild]> (terminated due to signal 11) Jan 16 12:06:56 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 3431 Jan 16 12:06:56 sogod [3431]: <0x0x56279589b340[WOHttpAdaptor]> notified the watchdog that we are ready Jan 16 12:07:10 sogod [3431]: <0x0x56279594bb60[SOGoCache]> Cache cleanup interval set every 900.000000 seconds Jan 16 12:07:10 sogod [3431]: <0x0x56279594bb60[SOGoCache]> Using host(s) 'sogo1.rz.Domain.de' as server(s) Jan 16 12:07:10 sogod [3431]: [WARN] <0x0x7f0731537f60[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder Jan 16 12:07:10 sogod [3431]: 141.82.146.66 "GET /SOGo HTTP/1.1" 302 0/0 0.017 - - 2M - 11 Jan 16 12:07:10 sogod [3431]: 141.82.146.66 "GET /SOGo/ HTTP/1.1" 200 10613/0 0.016 37922 72% 920K - 11 Jan 16 12:07:11 sogod [3431]: 141.82.146.66 "POST /SOGo/so/passwordRecoveryEnabled HTTP/1.1" 403 0/35 0.002 - - 0 - 11 Jan 16 12:07:18 sogod [3431]: SOGoRootPage successful login from '141.82.146.66' for user 'bidmon' - expire = -1 grace = -1 Jan 16 12:07:18 sogod [3431]: 141.82.146.66 "POST /SOGo/connect HTTP/1.1" 200 45/77 0.081 - - 5M - 13 Jan 16 12:07:19 sogod [3431]: 141.82.146.66 "GET /SOGo/bidmon HTTP/1.1" 302 0/0 0.005 - - 0 - 13 Jan 16 12:07:19 sogod [3431]: 141.82.146.66 "GET /SOGo/bidmon/view HTTP/1.1" 302 0/0 0.011 - - 0 - 13 Jan 16 12:07:20 sogod [3431]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail HTTP/1.1" 302 0/0 0.004 - - 612K - 13 Jan 16 12:07:21 sogod [3431]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/view HTTP/1.1" 200 24607/0 0.055 94660 74% 3M - 13 Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: [WARN] <0x0x562795ef9830[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table Jan 16 12:07:22 sogod [3431]: 141.82.146.66 "GET /SOGo/so/bidmon/Calendar/alarmslist?browserTime=1673867242 HTTP/1.1" 200 60/0 0.021 - - 0 - 13 Jan 16 12:07:22 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/0/folderINBOX/changes HTTP/1.1" 200 27/126 0.079 - - 0 - 13 Jan 16 12:07:22 sogod [3105]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/0/view HTTP/1.1" 200 6576/0 0.077 - - 0 - 13 Jan 16 12:07:23 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/0/folderINBOX/view HTTP/1.1" 200 99862/48 0.338 - - 3M - 14 Jan 16 12:07:24 sogod [3105]: 141.82.146.66 "POST /SOGo/so/bidmon/Mail/unseenCount HTTP/1.1" 200 22/31 0.081 - - -1580K - 13 Jan 16 12:07:24 sogod [3105]: 141.82.146.66 "GET /SOGo/so/bidmon/Mail/0/folderINBOX/labels HTTP/1.1" 200 131/0 0.073 - - 0 - 14 Jan 16 12:07:33 sogod [3105]: 141.82.146.66 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=bidmon&DeviceId=E2B7D5A65C234BDB8566EF3D73982ED7&DeviceType=WindowsOutlook15 HTTP/1.1" 200 49/37 0.310 - - 11M - 13 Jan 16 12:07:38 sogod [3105]: <0x0x5627963c80e0[SOGoActiveSyncDispatcher]> Cache cleanup needed for device E2B7D5A65C234BDB8566EF3D73982ED7 - user: bidmon syncKey: 14491-42000 cache: 14491-42006 Jan 16 12:07:38 sogod [3105]: <0x0x5627964ce690[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:07:38 sogod [3105]: <0x0x5627964ce690[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Jan 16 12:07:40 sogod [756]: <0x0x562795c5ea10[WOWatchDogChild]> child 3105 exited Jan 16 12:07:40 sogod [756]: <0x0x562795c5ea10[WOWatchDogChild]> (terminated due to signal 11) Jan 16 12:07:40 sogod [756]: <0x0x562795b11890[WOWatchDog]> child spawned with pid 3432

sebastien 2023-01-17 08:39 administrator ~0016554	You have a segfault : `Jan 16 12:07:40 sogod [756]: <0x0x562795c5ea10[WOWatchDogChild]> (terminated due to signal 11)` When starting with gdb with breakpoints described in https://www.sogo.nu/support/faq/how-do-i-debug-sogo.html you should have break in `abort`. Then type bt to get backtrace. Procedure : Stop sogo su -s /bin/bash - sogo gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 127.0.0.1:20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid Type `b [NSException raise]` and enter Type `b abort` and enter Type `r` and enter Reproduce the case When it breaks in abort, type `bt` and enter and give the result Sebastien

Colmar0 2023-01-17 08:56 reporter ~0016557	I type the following: systemctl stop sogo su -s /bin/bash - sogo gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 127.0.0.1:20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid Type `b [NSException raise]` and enter 'Here I Type 'y', I hope this is correct ?' Make breakpoint pending on future shared library load? (y or [n]) Type `b abort` and enter Type `r` and enter

Colmar0 2023-01-17 08:56 reporter ~0016558	I hope this was correct.

Colmar0 2023-01-17 12:16 reporter ~0016559	The first breakpoint shows following error message and MS Outlook shows the status "Connection attempt" and nothing happens: Same text in German: Der erste Haltepunkt zeigt folgende Fehlermeldung und MS Outlook zeigt den Status "Verbindungsversuch" an und nichts passiert: Breakpoint 1, -[NSException raise] (self=0x555555e1ce00, _cmd=0x7ffff770fa40 <_OBJC_SELECTOR_TABLE+512>) at NSException.m:1574 1574 NSException.m: No such file or directory. (gdb) bt #0 -[NSException raise] (self=0x555555e1ce00, _cmd=0x7ffff770fa40 <_OBJC_SELECTOR_TABLE+512>) at NSException.m:1574 0000001 0x00007ffff76f83d3 in -[NGLdapConnection bindWithMethod:binddn:credentials:] (self=0x55555642aea0, _cmd=0x7ffff7fa3060 <_OBJC_SELECTOR_TABLE+736>, _method=0x7ffff7fa1200 <_OBJC_INSTANCE_56.85>, _login=0x555555de2210, _cred=0x555556aa27c0) at NGLdapConnection.m:305 0000002 0x00007ffff7f15fb8 in -[LDAPSource checkLogin:password:perr:expire:grace:] (self=0x5555555c6080, _cmd=0x7ffff7f9df80 <_OBJC_SELECTOR_TABLE+768>, _login=0x555555717e10, _pwd=0x555556aa27c0, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at LDAPSource.m:630 0000003 0x00007ffff7f0e29d in -[SOGoUserManager _sourceCheckLogin:andPassword:domain:perr:expire:grace:] (self=0x55555579aa30, _cmd=0x7ffff7f9e0b0 <_OBJC_SELECTOR_TABLE+1072>, login=0x555555717e10, password=0x555556aa27c0, domain=0x7fffffffbf50, perr=0x7fffffffbf4c, expire=0x7fffffffbf48, grace=0x7fffffffbf44) at SOGoUserManager.m:522 0000004 0x00007ffff7f0ec61 in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:useCache:] (self=0x55555579aa30, _cmd=0x7ffff7f9dfa0 <_OBJC_SELECTOR_TABLE+800>, _login=0x555555717e10, _pwd=0x555556aa27c0, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44, useCache=1 '\001') at SOGoUserManager.m:687 0000005 0x00007ffff7f0e4cb in -[SOGoUserManager checkLogin:password:domain:perr:expire:grace:] (self=0x55555579aa30, _cmd=0x7ffff7fb74d0 <_OBJC_SELECTOR_TABLE+48>, _login=0x555555717e10, _pwd=0x555556aa27c0, _domain=0x7fffffffbf50, _perr=0x7fffffffbf4c, _expire=0x7fffffffbf48, _grace=0x7fffffffbf44) at SOGoUserManager.m:564 0000006 0x00007ffff7f36884 in -[SOGoDAVAuthenticator checkLogin:password:] (self=0x555555755e60, _cmd=0x7ffff7b93f10 <_OBJC_SELECTOR_TABLE+496>, _login=0x555555717e10, _pwd=0x555556aa27c0) at SOGoDAVAuthenticator.m:69 0000007 0x00007ffff7a4fe86 in -[SoHTTPAuthenticator preprocessCredentialsInContext:] (self=0x555555755e60, _cmd=0x7ffff7b97f60 <_OBJC_SELECTOR_TABLE+1408>, _ctx=0x5555571bebb0) at SoHTTPAuthenticator.m:272 0000008 0x00007ffff7a5665f in -[SoObjectRequestHandler handleRequest:inContext:session:application:] (self=0x555555a8dd40, _cmd=0x7ffff7b18c30 <_OBJC_SELECTOR_TABLE+848>, _rq=0x555556400b00, _ctx=0x5555571bebb0, _sn=0x0, app=0x555555984130) at SoObjectRequestHandler.m:537 0000009 0x00007ffff79e0c7a in -[WORequestHandler handleRequest:] (self=0x555555a8dd40, _cmd=0x7ffff7ae11b0 <_OBJC_SELECTOR_TABLE+1616>, _request=0x555556400b00) at WORequestHandler.m:240 0000010 0x00007ffff79a3661 in -[WOCoreApplication dispatchRequest:usingHandler:] (self=0x555555984130, _cmd=0x7ffff7ae1200 <_OBJC_SELECTOR_TABLE+1696>, _request=0x555556400b00, handler=0x555555a8dd40) at WOCoreApplication.m:712 0000011 0x00007ffff79a3969 in -[WOCoreApplication dispatchRequest:] (self=0x555555984130, _cmd=0x5555555665c0 <_OBJC_SELECTOR_TABLE+1664>, _request=0x555556400b00) at WOCoreApplication.m:752 0000012 0x000055555555d45b in -[SOGo dispatchRequest:] (self=0x555555984130, _cmd=0x7ffff7b7f180 <_OBJC_SELECTOR_TABLE+1760>, _request=0x555556400b00) at SOGo.m:584 0000013 0x00007ffff7a45622 in -[WOHttpTransaction _run] (self=0x55555714ba40, _cmd=0x7ffff7b7f1b0 <_OBJC_SELECTOR_TABLE+1808>) at WOHttpTransaction.m:566 0000014 0x00007ffff7a45982 in -[WOHttpTransaction run] (self=0x55555714ba40, _cmd=0x7ffff7b7ceb0 <_OBJC_SELECTOR_TABLE+1168>) at WOHttpTransaction.m:619 0000015 0x00007ffff7a418a9 in -[WOHttpAdaptor runConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf50 <_OBJC_SELECTOR_TABLE+1328>, _socket=0x55555591bf30) at WOHttpAdaptor.m:373 0000016 0x00007ffff7a41ab5 in -[WOHttpAdaptor _handleAcceptedConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7cf60 <_OBJC_SELECTOR_TABLE+1344>, _connection=0x55555591bf30) at WOHttpAdaptor.m:407 0000017 0x00007ffff7a41ead in -[WOHttpAdaptor _handleConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7d000 <_OBJC_SELECTOR_TABLE+1504>, connection=0x55555591bf30) at WOHttpAdaptor.m:466 0000018 0x00007ffff7a422fe in -[WOHttpAdaptor acceptConnection:] (self=0x5555559de510, _cmd=0x7ffff7b7ce70 <_OBJC_SELECTOR_TABLE+1104>, _notification=0x5555561ffc00) at WOHttpAdaptor.m:527 0000019 0x00007ffff70e9604 in -[NSNotificationCenter _postAndRelease:] (self=0x555555738430, _cmd=<optimized out>, notification=0x5555561ffc00) at NSNotificationCenter.m:1198 0000020 0x00007ffff75fd8e4 in -[NSObject(FileObjectWatcher) receivedEvent:type:extra:forMode:] (self=0x555555bf1e40, _cmd=0x7ffff74bc550 <_OBJC_SELECTOR_TABLE+304>, _fdData=0x5, _type=ET_RDESC, _extra=0x5, _mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>) at NSRunLoop+FileObjects.m:58 0000021 0x00007ffff721198b in -[GSRunLoopCtxt pollUntil:within:] (self=<optimized out>, _cmd=0x7ffff7437ee0 <_OBJC_SELECTOR_TABLE+1184>, milliseconds=<optimized out>, contexts=0x555555ac40f0) at GSRunLoopCtxt.m:600 0000022 0x00007ffff713afde in -[NSRunLoop acceptInputForMode:beforeDate:] (self=0x5555559e9a20, _cmd=0x7ffff7437f10 <_OBJC_SELECTOR_TABLE+1232>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, limit_date=0x555555f09b90) at NSRunLoop.m:1238 0000023 0x00007ffff713ad74 in -[NSRunLoop runMode:beforeDate:] (self=0x5555559e9a20, _cmd=<optimized out>, mode=0x7ffff7438cf0 <_OBJC_INSTANCE_2>, date=0x555555f09b90) at NSRunLoop.m:1318 0000024 0x00007ffff79a2ec8 in -[WOCoreApplication run] (self=0x555555984130, _cmd=0x555555566320 <_OBJC_SELECTOR_TABLE+992>) at WOCoreApplication.m:584 0000025 0x000055555555c664 in -[SOGo run] (self=0x555555984130, _cmd=0x7ffff7b03eb0 <_OBJC_SELECTOR_TABLE+208>) at SOGo.m:337 0000026 0x00007ffff79cbf95 in WOApplicationMain (_appClassName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOApplicationMain.m:42 0000027 0x00007ffff79ebe04 in WOWatchDogApplicationMain (appName=0x555555564160 <_OBJC_INSTANCE_0.1>, argc=13, argv=0x7fffffffec48) at WOWatchDogApplicationMain.m:1049 0000028 0x000055555555b2fe in main (argc=13, argv=0x7fffffffec48, env=0x7fffffffecb8) at sogod.m:51 (gdb)

Colmar0 2023-01-18 09:39 reporter ~0016564	My current problem is that MS Outlook stopped syncing yesterday and today after reopening Outlook it resumes syncing, but since I closed my Putty yesterday for the terminal session I got "kicked out" of the "(gdb)" Debugging Console . With MS Outlook synchronization still running, how do I get back into this "(gdb)" debugging console for the currently running process? Because it is aggravating that constantly new processes with a new process ID are started to continue the synchronization after each "NSException". Same text in German: Mein aktuelles Problem ist, daß MS Outlook gestern aufgehört hat zu synchronisieren und heute nach einem erneuten Öffnen von Outlook die Synchronisation zwar wieder fortsetzt, da ich aber gestern meinen Putty für die Terminal Sitzung geschlossen habe, bin ich aus der „(gdb)“ Debugging Konsole "herausgeflogen". Wie komme ich bei noch laufender MS Outlook Synchronisation wieder in diese „(gdb)“ Debugging Konsole für den gerade laufenden Prozeß hinein? Denn es kommt erschwerend hinzu, daß ja ständig neue Prozesse mit einer neuen Prozeß-ID zur Fortsetzung der Synchronisation nach jeder „NSException“ gestartet werden.

sebastien 2023-01-18 09:55 administrator ~0016565	It seems that SOGo could not bind LDAP. This is usually caused by error in configuration, please check LDAP settings in sogo.conf try to access to your LDAP server from the SOGo server if not on the same server (maybe a firewall issue) Sebastien

Colmar0 2023-01-18 10:34 reporter ~0016566	Is the LDAP configuration, as it can be seen in the attached sogo.conf file, correct or do I have to change or improve something? In principle the LDAP query with "ldapsearch" works over the Sogo user, if one starts a query for this used user over: Same text in German: Ist die LDAP-Konfiguration, wie sie in der angehängten sogo.conf Datei zu sehen ist, denn so korrekt, oder muß man da noch etwas ändern oder verbessern? Prinzipiell funktioniert die LDAP Abfrage mit „ldapsearch“ über den Sogo Benutzer, wenn man eine Abfrage für diesen verwendeten Benutzer startet über: su -s /bin/bash - sogo ldapsearch -x -h ldap.Domain.de -b ou=people,dc=Domain,dc=de uid=bidmon extended LDIF # LDAPv3 base <ou=people,dc=Domain,dc=de> with scope subtree filter: uid=bidmon requesting: ALL # bidmon, People, Domain.de dn: uid=bidmon,ou=People,dc=Domain,dc=de shadowFlag: 0 shadowInactive: -1 shadowMax: -1 shadowMin: -1 shadowWarning: -1 sambaAcctFlags: [U ] sambaSID: S-1-5-21-228503547-3738263332-2093544078-68236 sambaHomePath: \rzdepot.Domain.de\bidmon dfnEduPersonFieldOfStudyString: Singularis objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount objectClass: shadowAccount objectClass: organizationalPerson objectClass: inetLocalMailRecipient objectClass: sambaSamAccount objectClass: dfnEduPerson objectClass: schacPersonalCharacteristics objectClass: schacLinkageIdentifiers objectClass: eduPerson objectClass: schacContactLocation objectClass: ldapPublicKey givenName: S. sn: Bidmon cn: S. Bidmon displayName: S. Bidmon o: Domain Town schacHomeOrganization: Domain.de gecos: S. Bidmon uid: bidmon uidNumber: 33618 If you perform a general LDAP query on the user "Sogo" with the determination of the runtime using the command "time", it will look like this: Same text in German: Wenn man eine allgemeine LDAP Abfrage über den Benutzer „Sogo“ durchführt mit der Ermittlung der Laufzeit über das Kommando „time“ durchführt, dann sieht diese so aus: time ldapsearch -x -H ldaps://ldap.Domain -b ou=people,dc=Domain,dc=de '(&(objectclass=dfneduperson)(employeetype=angestellte))' dn extended LDIF # LDAPv3 base <ou=people,dc=Domain,dc=de> with scope subtree filter: (&(objectclass=dfneduperson)(employeetype=angestellte)) requesting: dn ... bidmon, People, Domain.de dn: uid=bidmon,ou=People,dc=Domain,dc=de ... search result search: 2 result: 0 Success numResponses: 665 numEntries: 664 real 0m0.069s user 0m0.018s sys 0m0.021s

Colmar0 2023-02-13 15:56 reporter ~0016656	While further searching the Sogo log files, I noticed the following error: Same text in German: Bei der weiteren Durchsuchung der Sogo Protokolldateien ist mir noch folgender Fehler aufgefallen: Feb 07 18:16:47 sogod [4513]: [WARN] <0x0x7f3329f01f60[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder Feb 07 18:16:47 sogod [4513]: 176.58.107.239 "GET /SOGo HTTP/1.1" 302 0/0 0.012 - - 3M - 11 Feb 07 18:16:47 sogod [4513]: 176.58.107.239 "GET /SOGo/ HTTP/1.1" 200 10610/0 0.011 37919 72% 860K - 11 Feb 07 18:21:54 sogod [4513]: 183.136.225.32 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Feb 07 20:19:12 sogod [4513]: <0x0x5611ccb70f10[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>' and base 'https://sogo-debug.Domain.de' ... Feb 07 20:19:12 sogod [4513]: <0x0x5611ccb70f10[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>' and base 'https://sogo-debug.Domain.de' ... Feb 07 20:19:12 sogod [4513]: <0x0x5611ccb70f10[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>' and base 'https://sogo-debug.Domain.de' ... Feb 07 20:19:12 sogod [4513]: <0x0x5611ccb70f10[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>' and base 'https://sogo-debug.Domain.de' ... Feb 07 20:19:12 sogod [4513]: 152.89.196.211 "GET /SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php> HTTP/1.1" 200 10665/0 0.014 37968 71% 756K - 11 Feb 07 20:51:39 sogod [4513]: 162.142.125.219 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Feb 07 20:51:40 sogod [4513]: 162.142.125.219 "GET /SOGo/ HTTP/1.1" 200 10608/0 0.007 37919 72% 4K - 11 Feb 08 01:14:44 sogod [4513]: 198.235.24.18 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Feb 08 01:14:45 sogod [4513]: 198.235.24.18 "GET /SOGo/ HTTP/1.1" 200 2594/0 0.003 - - 0 - 11 Feb 08 03:07:57 sogod [4513]: 180.149.125.159 "GET /SOGo HTTP/1.1" 302 0/0 0.001 - - 0 - 11 Feb 08 03:07:58 sogod [4513]: 180.149.125.159 "GET /SOGo/ HTTP/1.1" 200 10610/0 0.007 37919 72% 4K - 11 Feb 08 03:18:01 sogod [674]: <0x0x5611cc661890[WOWatchDog]> Terminating with SIGINT or SIGTERM Feb 08 03:18:01 sogod [674]: <0x0x5611cc7aea10[WOWatchDogChild]> sending terminate signal to pid 755 Feb 08 03:18:01 sogod [674]: <0x0x5611cc7a9d30[WOWatchDogChild]> sending terminate signal to pid 4513 What does the error "[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>'" mean? Where or by what is this error generated? What is wrong with the "NSURL" construct? Same text in German: Was bedeutet der Fehler "[WOContext]> could not construct NSURL for uri '/SOGo?a=fetch&content=<php>die%28@md5%28HelloThinkCMF%29%29</php>'"? Wo oder durch was wird dieser Fehler generiert? Was ist der dem "NSURL" Konstrukt fehlerhaft?

Date Modified	Username	Field	Change
2022-07-08 10:28	Colmar0	New Issue
2022-07-08 10:28	Colmar0	Tag Attached: active sync
2022-07-14 10:02	Christian Mack	Relationship added	has duplicate 0005555
2022-07-14 10:03	Christian Mack	Relationship added	has duplicate 0005556
2022-07-14 10:03	Christian Mack	Relationship added	has duplicate 0005557
2022-10-07 07:09	Colmar0	Note Added: 0016267
2022-10-07 07:09	Colmar0	File Added: sogo.conf
2022-10-07 07:15	Colmar0	Note Added: 0016268
2022-12-01 06:28	Colmar0	Note Added: 0016447
2022-12-01 07:44	sebastien	Note Added: 0016448
2022-12-01 10:12	Colmar0	Note Added: 0016449
2022-12-01 10:48	sebastien	Note Added: 0016450
2022-12-01 10:48	sebastien	Note Edited: 0016450
2022-12-01 12:31	Colmar0	Note Added: 0016451
2022-12-01 13:21	sebastien	Note Added: 0016452
2022-12-02 06:01	Colmar0	Note Added: 0016453
2022-12-12 11:13	Colmar0	Note Added: 0016481
2022-12-13 14:59	Colmar0	Note Added: 0016496
2022-12-14 06:57	Colmar0	Note Added: 0016499
2023-01-12 11:07	Colmar0	Note Added: 0016541
2023-01-12 11:12	Colmar0	Note Added: 0016542
2023-01-13 11:54	Colmar0	Note Added: 0016546
2023-01-16 08:03	Colmar0	Note Added: 0016548
2023-01-16 11:40	Colmar0	Note Added: 0016552
2023-01-17 08:39	sebastien	Note Added: 0016554
2023-01-17 08:56	Colmar0	Note Added: 0016557
2023-01-17 08:56	Colmar0	Note Added: 0016558
2023-01-17 12:16	Colmar0	Note Added: 0016559
2023-01-18 09:39	Colmar0	Note Added: 0016564
2023-01-18 09:55	sebastien	Note Added: 0016565
2023-01-18 10:34	Colmar0	Note Added: 0016566
2023-02-13 15:56	Colmar0	Note Added: 0016656
2023-08-02 08:25	sebastien	Assigned To	=> sebastien
2023-08-02 08:25	sebastien	Status	new => closed
2023-08-02 08:25	sebastien	Resolution	open => duplicate

View Issue Details

Relationships

Activities

extended LDIF

LDAPv3

base <ou=people,dc=Domain,dc=de> with scope subtree

filter: uid=bidmon

requesting: ALL

bidmon, People, Domain.de

extended LDIF

LDAPv3

base <ou=people,dc=Domain,dc=de> with scope subtree

filter: (&(objectclass=dfneduperson)(employeetype=angestellte))

requesting: dn

bidmon, People, Domain.de

search result

numResponses: 665

numEntries: 664

Issue History

has duplicate	0005555	closed	sebastien	MS Outlook 2016 with active Sync stops synchronizing and shows status disconnected
has duplicate	0005556	closed	sebastien	MS Outlook 2016 with active Sync stops synchronizing and shows status disconnected
has duplicate	0005557	new		MS Outlook 2016 with active Sync stops synchronizing and shows status disconnected