pim.etesync.com failing to sync (both android & linux) for several days?

[m10d]

I use several devices synced against etesync cloud for contacts & calendar, two android devices and linux/ubuntu. None of them At time of submission, neither android device, nor my linux desktop running etesync-dav were syncing anything successfully to/from the cloud or between each other. As of 10/28 I see that the android devices seem to be syncing successfully to the cloud.

All were working well / as expected a few days ago.

• android/fdroid v2.4.4 (latest available, albeit march 2024)
• linux 0.31.2 (old I know; i can't upgrade due to 0.35.1 fails to load on libpython3.10-->libm-->GLIBC dependancy #358 and no binaries appear to be available for any builds between what i have downloaded locally (0.31.2) and latest 0.35.1 as only infrequently are build artifacts (which expire by default) being promoted to release assets (?))

stopping etesync-dav in systemd and running directly with -D I see the following (fwiw -D works fine for me #355)

[2025-10-23 ... ] [2599585/Thread-8] [INFO] Successful login: '<USER>'
[2025-10-23 ... ] [2599585/Thread-3] [DEBUG] Client provided sync token: ''
[2025-10-23 ... ] [2599585/Thread-4] [DEBUG] '<USER>' has write access to collection with tag '<...>'
[2025-10-23 ... ] [2599585/Thread-4] [DEBUG] Response content:

....

and several more responses, some with a lot of xml data ... however as best i can tell that is all just the (local) server responding to my thunderbird (?)

The first few lines of output running locally don't explicitly say anything about cloud auth, but i also don't see any failures in that -D output until later, after plenty of valid xml data has been exchanged. Then i get this repeating

[2025-10-23 ...] [2599585/Thread-11] [ERROR] An exception occurred during PROPFIND request on '/<USER>/<longstring>/': Server error
Traceback (most recent call last):
  File "radicale/app/__init__.py", line 127, in __call__
  File "radicale/app/__init__.py", line 267, in _handle_request
  File "contextlib.py", line 113, in __enter__
  File "etesync_dav/radicale/storage.py", line 622, in acquire_lock
  File "etesync_dav/radicale/storage.py", line 74, in wait_for_sync
  File "etesync_dav/radicale/storage.py", line 84, in run
  File "etesync_dav/local_cache/__init__.py", line 92, in sync
  File "etesync_dav/local_cache/__init__.py", line 157, in sync_collection
  File "etesync_dav/local_cache/__init__.py", line 220, in push_collection
  File "etebase/__init__.py", line 298, in batch
etebase_python.Error: Server error
[2025-10-23 ...] [2599585/Thread-7] [ERROR] Server error
Traceback (most recent call last):
  File "etesync_dav/radicale/storage.py", line 84, in run
  File "etesync_dav/local_cache/__init__.py", line 92, in sync
  File "etesync_dav/local_cache/__init__.py", line 157, in sync_collection
  File "etesync_dav/local_cache/__init__.py", line 220, in push_collection
  File "etebase/__init__.py", line 298, in batch
etebase_python.Error: Server error

[m10d]

I've updated the issue to reflect this, on 10/28 it appears the android issues are resolved and this is specific to etesync-dav. No change in app or config/settings, but new events seem to be showing up from one device to another (and as expected, but I did verify, they show in the web app as well).