Coolwsd stuck with an error loop

Hello,

Since last night I have a 403 error severly polluting my apache log coming from coolwsd. The thing is even eating up a fair share of my servers load.

192.168.1.1 - - [12/Jul/2022:09:30:09 +0200] “POST /index.php/apps/richdocuments/wopi/files/<some_id>/contents?access_token=<some_access_token>&access_token_ttl=0%2Fws%3FWOPISrc%3Dhttps%3A%2F%2Fmyserverdns%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%<same_id>&compat= HTTP/1.1” 403 6216 “-” "COOLWSD HTTP Agent 22.05.3.1

I found coolwsd’s log in /tmp//tmp/coolwsd.randomdigits/ and it has the following:

wsd-1509325-1509376 2022-07-12 09:35:56.943897 +0200 [ docbroker_001 ] ERR Cannot upload docKey [https://myserverdns:443/index.php/apps/richdocuments/wopi/files/<the_id>] to storage URI [https://myserverdns/index.php/apps/richdocuments/wopi/files/<the_id>?access_token=<the_access_token>&access_token_ttl=0%2Fws%3FWOPISrc%3Dhttps%3A%2F%2Fmyserverdns%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%<the_id>&compat=]. Invalid or expired access token. Notifying client.| wsd/DocumentBroker.cpp:1751
wsd-1509325-1509376 2022-07-12 09:35:56.943993 +0200 [ docbroker_001 ] ERR ToClient-00a: error: cmd=storage kind=saveunauthorized| common/Session.hpp:148

How can I refresh that token? Where is that actually coming from? Any idea?

edit: I restarted apache and the error went away but I would still like to know what was going on.

1 Like

I have the same problem.

Is this related to Invalid or expired access token · Issue #89 · CollaboraOnline/Docker-CODE · GitHub ?
Finding the same messages in the logs. I am investigating a period of 3 hours of very high CPU load that suddenly started and the ended again. During that time these message were repeated all the time in the logs.