Peter Bieringer
Peter Bieringer
no further feedback received, closing now
please reopen if still an issue with current version.
Thank you for the code adjustment suggestion
Is this happening during idling or because of processing ongoing requests? In case of high-load, usually the processing times per request are increasing. Are you able to sort out which...
Logging: start with "[logging] level = debug", others can be leftout for now as they are specific and more related to bug hunting. Locking: "nolock" is safe unless more than...
Created a wiki page with instructions...logwatch is not even required to be installed, only Perl must be usable -> https://github.com/Kozea/Radicale/wiki/Server-Statistics
Strange results...the sync-token issue need to be solved by on client side, looks like they got lost, check cache folder. For ``` Bad PUT request on '/kg/b82ef0ae-7d5f-7f28-f1a9-a66d884526da/040000008200E00074C5B7101A82E008000000005D7DC5362DC0DB010000000000000000100000005281FB9C9E9E164393852EF76B486F2E.ics' (prepare): can't compare...
Also check that the sync interval is not that low...so e.g. at least 15 min.
`bad_put_request_content = True` was seldom and I would keep it enabled to trace down and potentially fix an unexpected issue. > In Thunderbird, that is one minute That is for...
> [2025-12-09 10:06:09 +0100] [8128/Thread-16 (process_request_thread)] [ERROR] An exception occurred during REPORT request on '/dk/022c3850-3199-dd46-3697-bdf7de0fe0e6/': Another profiling tool is already active Hmm, potentially "per_request_method" is not that thread-safe as assumed...