-
Notifications
You must be signed in to change notification settings - Fork 68
Documents won't open from Nextcloud unless the container is restarted #16
Comments
Can Confirm with current docker image. |
I did notice in a few cases that the fork couldn't finish in time during the first start on some system setups, which resulted in "FTL Failed to fork child processes" error (somewhat similar to, and likely partially behind #10, but it only occurs once). In the next release the initial timeout will be extended, so if that's the reason behind this issue, it should be gone then. |
I had the same problem today. Here are my Docker logs for the latest collabora image:
|
I have the same problem runningloolwsd installed from deb packages. So this is not only a docker issue. But for me the workaround with just restart loolwsd doesn'T work if installed from .deb |
I have the same problem with docker-compose and nextcloud. |
hi !
I restart the single container with
docker-compose restart collabora-code
It ist part of a docker-compose file
Am 22.08.2018 um 20:34 schrieb Brylie Christopher Oxley:
…
@xundeenergie <https://github.com/xundeenergie> what command do you
use to restart the container? e.g. do you re-issue the command:
|docker run -t -d -p 127.0.0.1:9980:9980 -e
'domain=example\\.domain\\.org' --restart always --cap-add MKNOD
collabora/code |
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFnyrciyc7IE1UYLFGrntHSU_vjMFEvgks5uTaQ3gaJpZM4N-whR>.
|
I am using CODE 2.1
The first time I start the container, if I try to open a document from Nextcloud it fails with the following message:
If I 'restart' the container, it works fine after that.
I noticed that the first time I start the container, it always prints a log message like this:
When I restart the container, the error does not appear. Coincidence?
As a test, I appended some extra code to the start script to kill and relaunch loolwsd, and now it works fine without a restart after 60 seconds.
There's definitely something unique about the first run.
The text was updated successfully, but these errors were encountered: