Thelounge v. 4.0.0 "System limit for number of file watchers reached"

LSIO Discussion Container Support
1

Hi all,

I wanted to update thelounge to the latest version 4.0 on my Synology.
However, I receive the following error and I don’t know what to make of it. Every previous version from you guys worked fine.
this is the log:

date stream content
2020-01-03 10:22:02 stdout [s6-finish] sending all processes the KILL signal and exiting.
2020-01-03 10:21:59 stdout [s6-finish] sending all processes the TERM signal.
2020-01-03 10:21:58 stdout [s6-finish] waiting for services.
2020-01-03 10:21:58 stdout [cont-finish.d] done.
2020-01-03 10:21:58 stdout [cont-finish.d] executing container finish scripts…
2020-01-03 10:21:57 stdout }
2020-01-03 10:21:57 stdout filename: e[32m’/config/packages/package.json’e[39m
2020-01-03 10:21:57 stdout path: e[32m’/config/packages/package.json’e[39m,
2020-01-03 10:21:57 stdout code: e[32m’ENOSPC’e[39m,
2020-01-03 10:21:57 stdout syscall: e[32m’watch’e[39m,
2020-01-03 10:21:57 stdout errno: e[33m-28e[39m,
2020-01-03 10:21:57 stdout e[90m at processTicksAndRejections (internal/process/task_queues.js:79:21)e[39m {
2020-01-03 10:21:57 stdout e[90m at emitListeningNT (net.js:1335:10)e[39m
2020-01-03 10:21:57 stdout e[90m at Server.emit (events.js:210:5)e[39m
2020-01-03 10:21:57 stdout e[90m at Object.onceWrapper (events.js:299:28)e[39m
2020-01-03 10:21:57 stdout at Server. (/usr/lib/node_modules/e[4mtheloungee[24m/src/server.js:187:12)
2020-01-03 10:21:57 stdout at Object.loadPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:140:2)
2020-01-03 10:21:57 stdout at watchPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:144:5)
2020-01-03 10:21:57 stdout e[90m at Object.watch (fs.js:1329:11)e[39m
2020-01-03 10:21:57 stdout e[90m at FSWatcher.start (internal/fs/watchers.js:165:26)e[39m
2020-01-03 10:21:57 stdout Error: ENOSPC: System limit for number of file watchers reached, watch ‘/config/packages/package.json’
2020-01-03 10:21:57 stdout
2020-01-03 10:21:57 stdout ^
2020-01-03 10:21:57 stdout throw error;
2020-01-03 10:21:57 stdout internal/fs/watchers.js:173
2020-01-03 10:21:57 stdout e[2m2020-01-03 10:21:57e[22m e[34m[INFO]e[39m Available at e[32mhttp://[::]:9000/e[39m in e[1mprivatee[22m mode
2020-01-03 10:21:57 stdout e[2m2020-01-03 10:21:57e[22m e[34m[INFO]e[39m Configuration file: e[32m/config/config.jse[39m
2020-01-03 10:21:57 stdout e[2m2020-01-03 10:21:57e[22m e[34m[INFO]e[39m The Lounge e[32mv4.0.0e[39m (Node.js e[32m12.14.0e[39m on e[32mlinuxe[39m x64)
2020-01-03 10:21:56 stdout }
2020-01-03 10:21:56 stdout filename: e[32m’/config/packages/package.json’e[39m
2020-01-03 10:21:56 stdout path: e[32m’/config/packages/package.json’e[39m,
2020-01-03 10:21:56 stdout code: e[32m’ENOSPC’e[39m,
2020-01-03 10:21:56 stdout syscall: e[32m’watch’e[39m,
2020-01-03 10:21:56 stdout errno: e[33m-28e[39m,
2020-01-03 10:21:56 stdout e[90m at processTicksAndRejections (internal/process/task_queues.js:79:21)e[39m {
2020-01-03 10:21:56 stdout e[90m at emitListeningNT (net.js:1335:10)e[39m
2020-01-03 10:21:56 stdout e[90m at Server.emit (events.js:210:5)e[39m
2020-01-03 10:21:56 stdout e[90m at Object.onceWrapper (events.js:299:28)e[39m
2020-01-03 10:21:56 stdout at Server. (/usr/lib/node_modules/e[4mtheloungee[24m/src/server.js:187:12)
2020-01-03 10:21:56 stdout at Object.loadPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:140:2)
2020-01-03 10:21:56 stdout at watchPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:144:5)
2020-01-03 10:21:56 stdout e[90m at Object.watch (fs.js:1329:11)e[39m
2020-01-03 10:21:56 stdout e[90m at FSWatcher.start (internal/fs/watchers.js:165:26)e[39m
2020-01-03 10:21:56 stdout Error: ENOSPC: System limit for number of file watchers reached, watch ‘/config/packages/package.json’
2020-01-03 10:21:56 stdout
2020-01-03 10:21:56 stdout ^
2020-01-03 10:21:56 stdout throw error;
2020-01-03 10:21:56 stdout internal/fs/watchers.js:173
2020-01-03 10:21:56 stdout e[2m2020-01-03 10:21:56e[22m e[34m[INFO]e[39m Available at e[32mhttp://[::]:9000/e[39m in e[1mprivatee[22m mode
2020-01-03 10:21:56 stdout e[2m2020-01-03 10:21:56e[22m e[34m[INFO]e[39m Configuration file: e[32m/config/config.jse[39m
2020-01-03 10:21:56 stdout e[2m2020-01-03 10:21:56e[22m e[34m[INFO]e[39m The Lounge e[32mv4.0.0e[39m (Node.js e[32m12.14.0e[39m on e[32mlinuxe[39m x64)
2020-01-03 10:21:54 stdout }
2020-01-03 10:21:54 stdout filename: e[32m’/config/packages/package.json’e[39m
2020-01-03 10:21:54 stdout path: e[32m’/config/packages/package.json’e[39m,
2020-01-03 10:21:54 stdout code: e[32m’ENOSPC’e[39m,
2020-01-03 10:21:54 stdout syscall: e[32m’watch’e[39m,
2020-01-03 10:21:54 stdout errno: e[33m-28e[39m,
2020-01-03 10:21:54 stdout e[90m at processTicksAndRejections (internal/process/task_queues.js:79:21)e[39m {
2020-01-03 10:21:54 stdout e[90m at emitListeningNT (net.js:1335:10)e[39m
2020-01-03 10:21:54 stdout e[90m at Server.emit (events.js:210:5)e[39m
2020-01-03 10:21:54 stdout e[90m at Object.onceWrapper (events.js:299:28)e[39m
2020-01-03 10:21:54 stdout at Server. (/usr/lib/node_modules/e[4mtheloungee[24m/src/server.js:187:12)
2020-01-03 10:21:54 stdout at Object.loadPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:140:2)
2020-01-03 10:21:54 stdout at watchPackages (/usr/lib/node_modules/e[4mtheloungee[24m/src/plugins/packages/index.js:144:5)
2020-01-03 10:21:54 stdout e[90m at Object.watch (fs.js:1329:11)e[39m
2020-01-03 10:21:54 stdout e[90m at FSWatcher.start (internal/fs/watchers.js:165:26)e[39m
2020-01-03 10:21:54 stdout Error: ENOSPC: System limit for number of file watchers reached, watch ‘/config/packages/package.json’
2

Please could you provide more information? How did you deploy the container? how are you trying to update the container? what your docker run/compose information?

3

I used the Synology web gui to download the image and started it the same way. I have been using the linuxserver images for a long time and I already had all the parameters set up (https://hub.docker.com/r/linuxserver/thelounge). The problem I described just occured with thelounge v.4. the previous version 3.3 works just fine.

I hope this helps. Let me know if you need any more information.

4

Unfortunately no one within the team uses Synology so no idea what their GUI offers. Going by the test results for the container here: https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/thelounge/latest/index.html the image should work fine.