-
6.12.8 - Log getting spammed and unstable server
Changing that fixed the logs. The stability seems a lot better aswell. Marking your answer as solution. Thank you so much.
-
6.12.8 - Log getting spammed and unstable server
Always Close UI: Check, will do! Change the docker network to ipvlan: Do you know of a guide that could help me do that? I found it mentioned in Settings->Docker, but not changeable. Disk1 - Replacement is ordered! Thank you so much for the insights and help so far.
-
Acrisium started following 6.12.8 - Log getting spammed and unstable server
-
6.12.8 - Log getting spammed and unstable server
Hi, My log is getting spammed and the server is unstable atm. The Log-spam is as follows: Mar 8 15:57:44 TheVault nginx: 2024/03/08 15:57:44 [error] 4602#4602: nchan: Out of shared memory while allocating message of size 13568. Increase nchan_max_reserved_memory. Mar 8 15:57:44 TheVault nginx: 2024/03/08 15:57:44 [error] 4602#4602: *668103 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Mar 8 15:57:44 TheVault nginx: 2024/03/08 15:57:44 [error] 4602#4602: MEMSTORE:00: can't create shared message for channel /disks Mar 8 15:57:45 TheVault nginx: 2024/03/08 15:57:45 [crit] 4602#4602: ngx_slab_alloc() failed: no memory Mar 8 15:57:45 TheVault nginx: 2024/03/08 15:57:45 [error] 4602#4602: shpool alloc failed Searching for information really only told me to post diagnostics for my server, so here it comes. Instability has shown itself as frozen, docker failing to update/restarting/starting/stopping containers, even if the containers themselves might or might not still work. The problems started after migrating to new hardware a little while back, but I am unable to migrate back (old hw no longer exist). I might be able to score some other memory if that ends up being the culprit. Any help in pointing me in the right direction or next steps would be greatly apreciated. thevault-diagnostics-20240308-1623.zip
-
Upgraded from 6.9.2 to 6.10. device eth0 does not exist
If you found the problem and worked it out, do you mind sharing the solution, or did you follow JorgeBs advice and move some settings at a time?
Acrisium
Members
-
Joined
-
Last visited