Error: Timeout
Unsolved
Etherpad Lite
-
Hi folks,
I think that this happens after the cloudron upgrade.
Etherpad is unable to re-start following the instructions.
The log indicates an odd error of :
Error: Timeout Did not receive an init message from worker after 10000ms. Make sure the worker calls expose() at Timeout.onTimeout (/app/code/src/node_modules/threads/dist/master/spawn.js:35:53) at processTimers /internal/timers.js:497:7)
I have no idea what to do next. Thanks for helping out.
-
I'm honestly not sure if I'm misunderstanding something but I haven't been able to remove plugins while the app is on recovery mode, as indicated on the Troubleshooting.
root@3f3407ba-5f2f-40ee-b2b6-437caffd738d:/app/code# npm ls 2> /dev/null | grep ep_ +-- ep_author_neat2@2.0.1 +-- ep_cloudron@4.2.4 +-- ep_etherpad-lite@1.8.14 -> /app/code/src +-- ep_mypads@1.7.21 root@3f3407ba-5f2f-40ee-b2b6-437caffd738d:/app/code# npm rm ep_author_neat2@2.0.1 npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/.npm/_cacache/tmp/c8d52bf2 npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/.npm/_cacache/tmp/c8d52bf2' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/.npm/_cacache/tmp/120805ff npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/.npm/_cacache/tmp/120805ff' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/.npm/_cacache/tmp/e3d1a4d6 npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/.npm/_cacache/tmp/e3d1a4d6' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
-
to update everyone else, the server disk I/O is for some unknown reason very slow thus etherpad hits timeouts. I was able to get it up and running mostly by chance to not timeout right away, so there is no real issue with the instance but hopefully the server provider can sort out this slowness somehow.