Collabora office, what means log error : CALLBACK_ERROR in zipapi

What does mean log error :

vm-colla-01-prod docker/collabora-app-1[19602]: kit-668563-669353 2026-02-12 10:29:25.897299 +0000 [ kitbgsv_1dee_003 ] ERR  ToMaster-1a790: CALLBACK_ERROR: {
vm-colla-01-prod docker/collabora-app-1[19602]:     "code": "0x20d(Error Area:Io Class:General Code:13) arg1=The stream seems to be broken! at \/opt\/collaboraoffice\/debugsource\/package\/source\/zipapi\/XUnbufferedStream.cxx:302",
vm-colla-01-prod docker/collabora-app-1[19602]:     "kind": "",
vm-colla-01-prod docker/collabora-app-1[19602]:     "cmd": "",
vm-colla-01-prod docker/collabora-app-1[19602]:     "message": "Erreur générale.\nGeneral input\/output error."

hi @adhfr

Welcome to collabora online forum

Collabora tried to open or save a document and the document’s ZIP stream was incomplete or corrupt — the file content it received didn’t match the file’s own internal structure.

If you can share the log lines immediately before this CALLBACK_ERROR (the WOPI request/transfer entries for the same session), I can help pin down whether it’s a broken transfer or an actually corrupt document.

This is a sensitive topic only in the sense of data integrity — if it turns out to be a corrupt file, the user may have lost recent edits, so it’s worth checking whether a prior good version exists in the storage backend’s version history.

Thank Darshan ,

Previous errors I can see :

2026-02-12T11:29:24.704131+01:00 nov-11-vm-colla-01-prod docker/collabora-app-1[19602]: sh: 1: /usr/bin/coolmount: Operation not permitted
2026-02-12T11:29:24.704850+01:00 nov-11-vm-colla-01-prod docker/collabora-app-1[19602]: sh: 1: /usr/bin/coolmount: Operation not permitted
2026-02-12T11:29:24.705890+01:00 nov-11-vm-colla-01-prod docker/collabora-app-1[19602]: sh: 1: /usr/bin/coolmount: Operation not permitted
2026-02-12T11:29:25.120422+01:00 nov-11-vm-colla-01-prod docker/collabora-app-1[19602]: kit-664371-664371 2026-02-12 10:29:25.120109 +0000 [ kitbroker_1db9 ] WRN #26: Background save process disconnected but not terminated 669340| kit/KitWebSocket.cpp:339

hi @adhfr :waving_hand:

Those lines are the root cause: coolmount: Operation not permitted means your Docker container can’t perform mount operations. That kills the background save process mid-write, so the document stream comes out truncated — which is exactly what the zipapi “stream seems to be broken” error is complaining about. Your files in storage are most likely fine.

Fix: run the container with --cap-add MKNOD --cap-add SYS_ADMIN (compose: cap_add: [MKNOD, SYS_ADMIN]). If you’re on rootless Docker or a NAS where mounts aren’t possible, add -e "extra_params=--o:mount_jail_tree=false" instead.