Get a lot of `Failed to process EWS request: ` with empty details ```log QT_LOGGING_RULE=log_ews_resource_request.debug=true /usr/bin/akonadi_ews_resource --identifier akonadi_ews_resource_3 org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews.client: Failed to process EWS request: ```
Created attachment 169010 [details] log from akonadiconsole I have the same messages repeated in journalctl. There is also a memory leak that makes the akonadi_ews_res process grow: top with interval: 10 sec continuous increase of akonadi_ews_res RES size: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4317 mm 20 0 2545384 580612 11784 S 5.389 15.28 0:41.93 akonadi_ews_res 4317 mm 20 0 2553160 587140 11656 S 5.389 15.45 0:42.47 akonadi_ews_res 4317 mm 20 0 2562660 594564 11656 S 5.694 15.65 0:43.04 akonadi_ews_res opensuse tumbleweed kdepim-runtime-24.02.2-1.1.x86_64
This is because malformed data is sent, this is the reply from the server (you should set QT_LOGGING_RULES="*org.kde.pim.ews.client.proto*.debug=true" to have it dumped somewhere): <?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorInvalidOperation</faultcode><faultstring xml:lang="en-US">Id is malformed.</faultstring><detail><e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorInvalidOperation</e:ResponseCode><e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">Id is malformed.</e:Message></detail></s:Fault></s:Body></s:Envelope> I haven't found a way to debug *why* it's invalid.
(In reply to Luca Beltrame from comment #2) > I haven't found a way to debug *why* it's invalid. dd785b95af83fd74618b5e4ce2904fa86db771e3 in kdepim-runtime might be suspect, but I have no way of confirming it.