View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006089SOGoBackend Calendarpublic2025-02-10 10:412025-02-18 12:03
Reporterjordi Assigned Toqhivert  
PrioritynormalSeveritymajorReproducibilitysometimes
Status assignedResolutionopen 
Product Version5.11.2 
Summary0006089: SOGo blocks randomly with hung children
Description

Since we upgraded to 5.11.2 in early December, we've been having issues with hanged sogods which end up with the calendar not being responsive at all. From the logs:

Feb 10 11:26:41 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:43 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:44 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:44 sogod [155543]: [WARN] <0x0x55c0181632a0[WOWatchDogChild]> pid 619234 has been hanging in the same request for 9 minutes
Feb 10 11:26:45 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:46 sogod [155543]: [WARN] <0x0x55c018121b90[WOWatchDogChild]> pid 619184 has been hanging in the same request for 8 minutes
Feb 10 11:26:46 sogod [155543]: [WARN] <0x0x55c018171bf0[WOWatchDogChild]> pid 645258 has been hanging in the same request for 8 minutes
Feb 10 11:26:47 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:48 sogod [155543]: [WARN] <0x0x55c0181360e0[WOWatchDogChild]> pid 583540 has been hanging in the same request for 8 minutes
Feb 10 11:26:48 sogod [155543]: [WARN] <0x0x55c018129f60[WOWatchDogChild]> pid 619250 has been hanging in the same request for 8 minutes
Feb 10 11:26:48 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Feb 10 11:26:49 sogod [155543]: [WARN] <0x0x55c0181717e0[WOWatchDogChild]> pid 583463 has been hanging in the same request for 9 minutes
Feb 10 11:26:49 sogod [155543]: [WARN] <0x0x55c01812b530[WOWatchDogChild]> pid 583538 has been hanging in the same request for 8 minutes
Feb 10 11:26:49 sogod [155543]: [WARN] <0x0x55c018129e40[WOWatchDogChild]> pid 619235 has been hanging in the same request for 9 minutes
Feb 10 11:26:50 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!

This looks like a regression in 5.11.x.

Steps To Reproduce

It's not easy to reproduce, the calendar can be working ok for days and suddenly it enters this condition.

Note we currently only use sogo for Calendaring, so the mail part of it is completely disabled.

Additional Information

Using downstream Debian packages 5.11.2 rebuilt for bookworm.

TagsNo tags attached.

Activities

qhivert

qhivert

2025-02-10 13:18

administrator   ~0018063

Hello,
Log like this:
Feb 10 11:26:44 sogod [155543]: [WARN] &lt;0x0x55c0181632a0[WOWatchDogChild]> pid 619234 has been hanging in the same request for 9 minutes
Means a child/worker is hanging. To know which request did it add this to your sogo.conf and restart sogo
SOGoDebugRequests = YES;

It will show the requests received like this
Feb 10 10:22:12 sogod [100]: |SOGo| starting method 'POST' on uri '/SOGo/so/sogo-tests1@example.org/Mail/0/folderINBOX/view'
The number between the brackets is the pid of the process. So you match the pid in the hanging log and the last request made on this pid. Could you tell me what are the requests?
I know there are problems with the export of calendars, it can take a lot of time and keep the worker busy.

Log like this
Feb 10 11:26:41 sogod [155543]: [ERROR] <0x0x55c0180b3e30[WOWatchDog]> No child available to handle incoming request!
Means all the workers are already busy, probably because of the hanging request
jordi

jordi

2025-02-11 11:01

reporter   ~0018081

I've changed our production config to enable requests debugging. I'll come back here the next time it blocks.
qhivert

qhivert

2025-02-11 11:05

administrator   ~0018082

Do users use ActiveSync by any chance?
jordi

jordi

2025-02-12 16:54

reporter   ~0018085

No, we don't even have the package installed.
jordi

jordi

2025-02-18 12:03

reporter   ~0018090

Hi @qhivert, I've had SOGo hanging a few times yesterday and today, and after looking closely at the SOGo logs and the matching rproxy logs, I think I have some patterns.

I see some heavy users of the calendar doing some REPORT requests, and soon after, those threads die and stop taking requests. These requests come from client "dataaccessd" (Apple devices), which first appears to do an unauthenticated REPORT request, which fails, and then retries with authentication.

See the following sequence: (rproxy logs first, then sogo)

X.Y.Z.141 - - [18/Feb/2025:07:44:34 +0000] "OPTIONS /SOGo/dav/user8/ HTTP/2.0" 401 0 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"
X.Y.Z.141 - user8 [18/Feb/2025:07:44:34 +0000] "OPTIONS /SOGo/dav/user8/ HTTP/2.0" 200 0 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"
X.Y.Z.141 - - [18/Feb/2025:07:44:34 +0000] "REPORT /SOGo/dav/user8/ HTTP/2.0" 401 0 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"
X.Y.Z.141 - user8 [18/Feb/2025:07:44:34 +0000] "REPORT /SOGo/dav/user8/ HTTP/2.0" 207 404 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"
X.Y.Z.141 - - [18/Feb/2025:07:44:34 +0000] "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/2.0" 401 0 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"
X.Y.Z.141 - user8 [18/Feb/2025:07:44:34 +0000] "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/2.0" 207 2043 "-" "macOS/15.0.1 (24A348) dataaccessd/1.0"

Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'OPTIONS' on uri '/SOGo/dav/user8/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.006724 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "OPTIONS /SOGo/dav/user8/ HTTP/1.1" 401 0/0 0.009 - - 0 - 14
Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'OPTIONS' on uri '/SOGo/dav/user8/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.003697 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "OPTIONS /SOGo/dav/user8/ HTTP/1.1" 200 0/0 0.005 - - 0 - 14
Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user8/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.000831 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "REPORT /SOGo/dav/user8/ HTTP/1.1" 401 0/768 0.002 - - 0 - 14
Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user8/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.034553 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "REPORT /SOGo/dav/user8/ HTTP/1.1" 207 404/768 0.037 1380 70% 0 - 13
Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'PROPFIND' on uri '/SOGo/dav/user8/Calendar/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.000864 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/1.1" 401 0/2237 0.002 - - 0 - 13
Feb 18 08:44:34 sogod [1014543]: |SOGo| starting method 'PROPFIND' on uri '/SOGo/dav/user8/Calendar/'
Feb 18 08:44:34 sogod [1014543]: |SOGo| request took 0.041733 seconds to execute
Feb 18 08:44:34 sogod [1014543]: X.Y.Z.141, 192.168.21.100 "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/1.1" 207 2043/2237 0.043 23464 91% 0 - 13

[ ... ]

Feb 18 08:44:48 sogod [1014543]: |SOGo| starting method 'PROPFIND' on uri '/SOGo/dav/user25/Contacts/ldaplocal/'
Feb 18 08:44:48 sogod [1014543]: |SOGo| request took 0.415206 seconds to execute
Feb 18 08:44:48 sogod [1014543]: D.E.F.136, 192.168.21.100 "PROPFIND /SOGo/dav/user25/Contacts/ldaplocal/ HTTP/1.1" 207 2803/231 0.417 51721 94% 0 - 13
Feb 18 08:44:50 sogod [1014543]: |SOGo| starting method 'OPTIONS' on uri '/SOGo/dav/user14/Calendar/mycompany_1AC-674D9580-F5-2EDD2A80/'
Feb 18 08:45:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 1 minutes
Feb 18 08:46:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 2 minutes
Feb 18 08:47:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 3 minutes
Feb 18 08:48:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 4 minutes
Feb 18 08:49:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 5 minutes
Feb 18 08:50:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 6 minutes
Feb 18 08:51:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 7 minutes
Feb 18 08:52:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 8 minutes
Feb 18 08:53:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> pid 1014543 has been hanging in the same request for 9 minutes
Feb 18 08:54:50 sogod [1011081]: [WARN] <0x0x56321433b420[WOWatchDogChild]> safety belt -- sending KILL signal to pid 1014543
Feb 18 08:54:50 sogod [1011081]: <0x0x56321433b420[WOWatchDogChild]> child 1014543 exited

As you can see, the thread 1014543 interacted with dataaccessd and soon after, just 14 seconds later, interacts with another process but then dies until sogod is restarted.

I have seen this with other users. The following one has a lot of subscriptions, and his Apple client did a tsunami of REPORTS. Immediately after that, all 22 threads were dead. (note the missing newlines are verbatim, it's how they were logged in sogo.log, for some reason).

Feb 17 10:23:45 sogod [1004377]: z.x.y.144, 192.168.21.100 "PROPFIND /SOGo/dav/user26/Calendar/ HTTP/1.1" 207 1727/2237 0.020 14696 88% 0 - 14
Feb 17 10:23:50 sogod [1004377]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user23_personal/'Feb 17 10:23:50 sogod [1004360]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user22_personal/'

Feb 17 10:23:50 sogod [1004380]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/personal/'
Feb 17 10:23:50 sogod [1004298]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user5_personal/'
Feb 17 10:23:50 sogod [1004296]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user6_personal/'
Feb 17 10:23:50 sogod [1004374]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/personal/'
Feb 17 10:23:50 sogod [1004365]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/39008A-63FFC180-5-263FAB40/'
Feb 17 10:23:51 sogod [1004369]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user7_personal/'
Feb 17 10:23:51 sogod [1004375]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user8_personal/'
Feb 17 10:23:51 sogod [1004317]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user9_personal/'
Feb 17 10:23:51 sogod [1004363]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/mycompany/Calendar/3E2B-5F152900-1-2789DE40/'
Feb 17 10:23:51 sogod [1004319]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user10_personal/'
Feb 17 10:23:51 sogod [1004314]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user11_personal/'
Feb 17 10:23:51 sogod [1004381]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/3911C3-63FFEC00-1-78222400/'
Feb 17 10:23:51 sogod [1004300]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user12_personal/'
Feb 17 10:23:51 sogod [1004311]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user13_personal/'
Feb 17 10:23:51 sogod [1004297]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/mycompany_personal/'
Feb 17 10:23:51 sogod [1004301]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user14_personal/'
Feb 17 10:23:51 sogod [1004313]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user15_personal/'
Feb 17 10:23:51 sogod [1004303]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user16_personal/'
Feb 17 10:23:51 sogod [1004384]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/mycompany-holidays_personal/' Feb 17 10:23:51 sogod [1004304]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user1/Calendar/user4_personal/'
Feb 17 10:23:52 sogod [1004303]: [ERROR] <0x0x55eae17268c0[LDAPSource]> Could not bind to the LDAP server ldap://sogo.service.mycompany.com (389) using the bind DN: cn=admin,dc=sogo,dc=local,dc=mycompany,dc=com Feb 17 10:23:52 sogod [1004303]: [ERROR] <0x0x55eae17268c0[LDAPSource]> <NSException: 0x55eae1898610> NAME:LDAPException REASON:operation bind failed: Can't contact LDAP server (0xFFFFFFFF) INFO:{"error_code" = "-1"; login = "cn=admin,dc=sogo,dc=local,dc=mycompany,dc=com"; }
Feb 17 10:23:57 sogod [1004306]: |SOGo| starting method 'GET' on uri '/SOGo/so/user18/Calendar/view' Feb 17 10:24:07 sogod [1004302]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user17/Calendar/personal/'Feb 17 10:24:07 sogod [1004385]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user17/Calendar/mycompany-holidays_personal/'

Feb 17 10:24:07 sogod [1004299]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user17/Calendar/mycompany_personal/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'OPTIONS' on uri '/SOGo/dav/user8/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.000834 seconds to execute
Feb 17 10:24:35 sogod [1004307]: X.Y.Z.141, 192.168.21.100 "OPTIONS /SOGo/dav/user8/ HTTP/1.1" 401 0/0 0.002 - - 0 - 12 Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'OPTIONS' on uri '/SOGo/dav/user8/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.001694 seconds to execute Feb 17 10:24:35 sogod [1004307]: X.Y.Z.141, 192.168.21.100 "OPTIONS /SOGo/dav/user8/ HTTP/1.1" 200 0/0 0.003 - - 0 - 12
Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'GET' on uri '/SOGo/so/user19/Calendar/eventslist?asc=1&day=20250217&filterpopup=view_next7&search=title_Category_Location&sort=start&value=' Feb 17 10:24:35 sogod [1004308]: |SOGo| starting method 'GET' on uri '/SOGo/so/user19/Calendar/eventsblocks?ed=20250223&sd=20250217&view=weekview'
Feb 17 10:24:35 sogod [1004352]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user8/'
Feb 17 10:24:35 sogod [1004308]: |SOGo| request took 0.102340 seconds to execute
Feb 17 10:24:35 sogod [1004352]: |SOGo| request took 0.001017 seconds to execute
Feb 17 10:24:35 sogod [1004352]: X.Y.Z.141, 192.168.21.100 "REPORT /SOGo/dav/user8/ HTTP/1.1" 401 0/768 0.002 - - 0 - 12
Feb 17 10:24:35 sogod [1004308]: A.B.C.44, 192.168.21.100 "GET /SOGo/so/user19/Calendar/eventsblocks?ed=20250223&sd=20250217&view=weekview HTTP/1.1" 200 9412/0 0.106 - - 2M - 13
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.123402 seconds to execute
Feb 17 10:24:35 sogod [1004307]: A.B.C.44, 192.168.21.100 "GET /SOGo/so/user19/Calendar/eventslist?asc=1&day=20250217&filterpopup=view_next7&search=title_Category_Location&sort=start&value= HTTP/1.1" 200 8040/0 0.125 - - 5M - 13
Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'REPORT' on uri '/SOGo/dav/user8/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.023053 seconds to execute
Feb 17 10:24:35 sogod [1004307]: X.Y.Z.141, 192.168.21.100 "REPORT /SOGo/dav/user8/ HTTP/1.1" 207 400/768 0.025 1380 71% 0 - 13
Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'PROPFIND' on uri '/SOGo/dav/user8/Calendar/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.000833 seconds to execute
Feb 17 10:24:35 sogod [1004307]: X.Y.Z.141, 192.168.21.100 "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/1.1" 401 0/2237 0.002 - - 0 - 13
Feb 17 10:24:35 sogod [1004307]: |SOGo| starting method 'PROPFIND' on uri '/SOGo/dav/user8/Calendar/'
Feb 17 10:24:35 sogod [1004307]: |SOGo| request took 0.042530 seconds to execute
Feb 17 10:24:35 sogod [1004307]: X.Y.Z.141, 192.168.21.100 "PROPFIND /SOGo/dav/user8/Calendar/ HTTP/1.1" 207 2043/2237 0.044 23464 91% 200K - 13
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae14caeb0[WOWatchDogChild]> pid 1004377 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae14bbc30[WOWatchDogChild]> pid 1004360 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae14ca7d0[WOWatchDogChild]> pid 1004380 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae1470780[WOWatchDogChild]> pid 1004298 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae146f830[WOWatchDogChild]> pid 1004296 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae14cb100[WOWatchDogChild]> pid 1004374 has been hanging in the same request for 1 minutes
Feb 17 10:24:50 sogod [1004291]: [WARN] <0x0x55eae14bb140[WOWatchDogChild]> pid 1004365 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae14baaf0[WOWatchDogChild]> pid 1004369 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae14cafe0[WOWatchDogChild]> pid 1004375 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1479280[WOWatchDogChild]> pid 1004317 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae14bb420[WOWatchDogChild]> pid 1004363 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae147a0b0[WOWatchDogChild]> pid 1004319 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1479520[WOWatchDogChild]> pid 1004314 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae14ca6a0[WOWatchDogChild]> pid 1004381 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1470130[WOWatchDogChild]> pid 1004300 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1479a40[WOWatchDogChild]> pid 1004311 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1478cf0[WOWatchDogChild]> pid 1004297 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae146fec0[WOWatchDogChild]> pid 1004301 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae1479850[WOWatchDogChild]> pid 1004313 has been hanging in the same request for 1 minutes
Feb 17 10:24:51 sogod [1004291]: [WARN] <0x0x55eae146fa40[WOWatchDogChild]> pid 1004303 has been hanging in the same request for 1 minutes

Note we have Evolution clients also doing REPORT requests, but the difference is the unauthenticated request is not done, unlike with Apple, Evo tries authenticated REPORT requests directly. These interactions don't seem to zombify the server threads.

Hopefully these findings provide some useful clue. We're available to provide more info!

Issue History

Date Modified Username Field Change
2025-02-10 10:41 jordi New Issue
2025-02-10 13:18 qhivert Note Added: 0018063
2025-02-10 13:18 qhivert Assigned To => qhivert
2025-02-10 13:18 qhivert Status new => feedback
2025-02-11 11:01 jordi Note Added: 0018081
2025-02-11 11:01 jordi Status feedback => assigned
2025-02-11 11:05 qhivert Note Added: 0018082
2025-02-11 11:05 qhivert Status assigned => feedback
2025-02-12 16:54 jordi Note Added: 0018085
2025-02-12 16:54 jordi Status feedback => assigned
2025-02-18 12:03 jordi Note Added: 0018090