[SOLVED] Document cannot be saved - Stragner Things

Hi, we have run Collabora using WOPI protocol. At the beginning everything was ok, but after few hours using we noticed that when client switch to inactive mode it bloked file. After that there is no option to save document state (“Document cannot be saved. Check your permissions or contact the storage server administrator”). It’s really strange because it’s possible to edit and save “non-locked” files but when you wait and allow client to switch in inactive this is the end. We reset docker and host machine.

Here is an error in logs:

wsd-00025-00042 07:18:16.256906 [ docbroker_002 ] TRC Poll completed with 1 live polls max (5000ms)| ./net/Socket.hpp:405
wsd-00025-00042 07:18:16.256944 [ docbroker_002 ] TRC #19: Incoming data buffer 143 bytes, closeSocket? false| ./net/Socket.hpp:856
wsd-00025-00042 07:18:16.256953 [ docbroker_002 ] TRC #19: Incoming WebSocket data of 143 bytes.| ./net/WebSocketHandler.hpp:129
wsd-00025-00042 07:18:16.256959 [ docbroker_002 ] TRC #19: Incoming WebSocket message code 1, fin? true, mask? true, payload length: 135, residual socket data: 0 bytes.| ./net/WebSocketHandler.hpp:195
wsd-00025-00042 07:18:16.256992 [ docbroker_002 ] TRC #19 Prisoner message [client-0004 unocommandresult: {…].| wsd/LOOLWSD.cpp:1661
wsd-00025-00042 07:18:16.257005 [ docbroker_002 ] TRC Message o238 unocommandresult: {…| ./common/Message.hpp:76
wsd-00025-00042 07:18:16.257017 [ docbroker_002 ] TRC DocumentBroker handling child message: [o238 unocommandresult: {…].| wsd/DocumentBroker.cpp:1124
wsd-00025-00042 07:18:16.257025 [ docbroker_002 ] TRC Forwarding payload to [client-0004]: o238 unocommandresult: {…| wsd/DocumentBroker.cpp:1459
wsd-00025-00042 07:18:16.257036 [ docbroker_002 ] TRC Message o239 unocommandresult: {…| ./common/Message.hpp:76
wsd-00025-00042 07:18:16.257041 [ docbroker_002 ] TRC ToClient-0004: handling kit-to-client [o239 unocommandresult: {…].| wsd/ClientSession.cpp:552
wsd-00025-00042 07:18:16.257047 [ docbroker_002 ] INF ToClient-0004: Command: unocommandresult: {
“commandName”: “.uno:Save”,
“success”: “false”,
“result”: {
“type”: “void”
}
}
| wsd/ClientSession.cpp:568
wsd-00025-00042 07:18:16.266626 [ docbroker_002 ] TRC Saving to storage docKey [/test_2017/wopi/files/21308] for session [0004]. Success: false, result: | wsd/DocumentBroker.cpp:695
wsd-00025-00042 07:18:16.266681 [ docbroker_002 ] ERR Cannot save docKey [/test_2017/wopi/files/21308], the .uno:Save has failed in LOK.| wsd/DocumentBroker.cpp:714
wsd-00025-00042 07:18:16.266696 [ docbroker_002 ] TRC Message o240 error: cmd=storage kind=savefailed| ./common/Message.hpp:76
wsd-00025-00042 07:18:16.266702 [ docbroker_002 ] TRC ToClient-0004 enqueueing client message o240| wsd/ClientSession.hpp:81
wsd-00025-00042 07:18:16.266712 [ docbroker_002 ] TRC ToClient-0004 enqueueing client message o239| wsd/ClientSession.hpp:81
wsd-00025-00042 07:18:16.266744 [ docbroker_002 ] TRC ToClient-0004 ClientSession has 2 write message(s) queued.| wsd/ClientSession.cpp:512
wsd-00025-00042 07:18:16.266777 [ docbroker_002 ] TRC Poll completed with 1 live polls max (5000ms)| ./net/Socket.hpp:405
wsd-00025-00042 07:18:16.266837 [ docbroker_002 ] TRC Socket #27 SSL error: WANT_READ (2).| ./net/SslSocket.hpp:202
wsd-00025-00042 07:18:16.266847 [ docbroker_002 ] TRC #27: Incoming data buffer 0 bytes, closeSocket? false| ./net/Socket.hpp:856
wsd-00025-00042 07:18:16.266855 [ docbroker_002 ] DBG ToClient-0004 ClientSession: performing writes| wsd/ClientSession.cpp:521
wsd-00025-00042 07:18:16.266870 [ docbroker_002 ] TRC ToClient-0004: Send: [error: cmd=storage kind=savefailed].| common/Session.cpp:67
wsd-00025-00042 07:18:16.266993 [ docbroker_002 ] TRC #27: Wrote outgoing data 36 bytes.| ./net/Socket.hpp:922
wsd-00025-00042 07:18:16.267755 [ docbroker_002 ] DBG ToClient-0004 ClientSession: performed write| wsd/ClientSession.cpp:545

It’s problem with damaging file during save operation. Issue solved.

Hello macieg_b

Could you explain a bit more ? How do you locate the damaged file ?

Thanks.

Hello,
After months… I still get the

Document cannot be saved to storage. Check your permissions or contact the storage server administrator

Any help would be welcomed. @macieg_b ?