spacecops

My log usage is now suddenly at 100%. After some investigation, I believe this is the log spamming thats causing this: Mar 4 05:37:20 rima-server nginx: 2022/03/04 05:37:20 [error] 11170#11170: shpool alloc failed Mar 4 05:37:20 rima-server nginx: 2022/03/04 05:37:20 [error] 11170#11170: nchan: Out of shared memory while allocating message of size 5614. Increase nchan_max_reserved_memory. Mar 4 05:37:20 rima-server nginx: 2022/03/04 05:37:20 [error] 11170#11170: *14051935 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/shares?buffer_length=1 HTTP/1.1", host: "localhost" Mar 4 05:37:20 rima-server nginx: 2022/03/04 05:37:20 [error] 11170#11170: MEMSTORE:00: can't create shared message for channel /shares Mar 4 05:37:21 rima-server nginx: 2022/03/04 05:37:21 [crit] 11170#11170: ngx_slab_alloc() failed: no memory Mar 4 05:37:21 rima-server nginx: 2022/03/04 05:37:21 [error] 11170#11170: shpool alloc failed Mar 4 05:37:21 rima-server nginx: 2022/03/04 05:37:21 [error] 11170#11170: nchan: Out of shared memory while allocating message of size 5861. Increase nchan_max_reserved_memory. Mar 4 05:37:21 rima-server nginx: 2022/03/04 05:37:21 [error] 11170#11170: *14051937 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Mar 4 05:37:21 rima-server nginx: 2022/03/04 05:37:21 [error] 11170#11170: MEMSTORE:00: can't create shared message for channel /disks Mar 4 05:37:22 rima-server nginx: 2022/03/04 05:37:22 [crit] 11170#11170: ngx_slab_alloc() failed: no memory Mar 4 05:37:22 rima-server nginx: 2022/03/04 05:37:22 [error] 11170#11170: shpool alloc failed Mar 4 05:37:22 rima-server nginx: 2022/03/04 05:37:22 [error] 11170#11170: nchan: Out of shared memory while allocating message of size 5861. Increase nchan_max_reserved_memory. (This keeps being spammed). I attached the logs, what is the best way to free up log space and prevent this from happening again? rima-server-diagnostics-20220306-2000.zip

unfortunately it seems to get stuck in some sort of loop when the docker is started the second time onwards. lambdawars.txt

Wow, I never would have guessed! I'll give it a spin and let you know if all is good. Thanks so much for your work!

Is it possible to set up a plugin for lambda wars? seems to be a straight forward SCRDS server

Neat, didn't even know it existed, thanks!

Mainly a quality of life thing. It would be neat to be able to group/tag dockers into categories within the UI, such that you can update/stop/etc all the dockers for a specific group instead of doing them one by one or all of them at once

More of a quality of life improvement in the UI. As of now, it seems all dockers are listed as a giant list in the docker page. A great time saver would be if you could "group" dockers as you choose into named groups, and have each group have a button to turn off and on dockers within the group (preferably with a settable order for how the dockers spin up and down)

Hey man, thanks for looking at the PA container! However, the issue now is it seems to be looking for a GPU when starting up. is there a way to fix that as well?

Hey, Noticed that the planetary annihilation server is spitting out this error: /serverdata/serverfiles/stable/server: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /serverdata/serverfiles/stable/server) The dependency may need to be updated

I am on the most recent version of Unraid, and I was not using a cache. There is a good chance this is a Gmod issue, since your SCP server runs just fine with near identical settings on the same share (only difference being port)

Every time I try running a Gmod server, even as a fresh install without any addons, it never starts and the log shows this: Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Mon 16 Mar 2020 06:50:40 PM EDT: Server restart in 10 seconds tcmalloc: large alloc 4291928064 bytes == (nil) @ tcmalloc: large alloc 4291928064 bytes == (nil) @ Setting breakpad minidump AppID = 4000 tcmalloc: large alloc 4291928064 bytes == (nil) @ Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Mon 16 Mar 2020 06:50:53 PM EDT: Server restart in 10 seconds tcmalloc: large alloc 4287995904 bytes == (nil) @ tcmalloc: large alloc 4287995904 bytes == (nil) @ Setting breakpad minidump AppID = 4000 tcmalloc: large alloc 4287995904 bytes == (nil) @ Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Mon 16 Mar 2020 06:51:05 PM EDT: Server restart in 10 seconds tcmalloc: large alloc 4291805184 bytes == (nil) @ tcmalloc: large alloc 4291813376 bytes == (nil) @ Setting breakpad minidump AppID = 4000 tcmalloc: large alloc 4291813376 bytes == (nil) @ Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Mon 16 Mar 2020 06:51:18 PM EDT: Server restart in 10 seconds

I wanted to hop in and say that the original docker image does not seem to be updating anymore, leaving in quite a few bugs (I was unable to parse any PDFS at all). this is the newer docker repo ive been using thats up to date, my "paperless" instance started working right when I switched to it https://hub.docker.com/r/thepaperlessproject/paperless you can easily switch to it by editing both (the webgui and consumer) your docker unraid configs, changing the "Repository:" to "thepaperlessproject/paperless"