Mancubus

I've recently upgraded to version 7.0 but I've been having this problem since before then. What essentially happens is my unRaid server becomes unresponsive from the GUI but all of the docker containers and VMs seem to function normally. When I log into the CLI and view the the tail of the syslog, I see these errors scrolling by continuously: Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: *770441 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/diagnostics?buffer_length=1 HTTP/1.1", host: "localhost" Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [crit] 2632135#2632135: ngx_slab_alloc() failed: no memory Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: shpool alloc failed Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: nchan: Out of shared memory while allocating channel /diagnostics. Increase nchan_max_reserved_memory. Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: *770442 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/diagnostics?buffer_length=1 HTTP/1.1", host: "localhost" Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [crit] 2632135#2632135: ngx_slab_alloc() failed: no memory Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: shpool alloc failed Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: nchan: Out of shared memory while allocating channel /diagnostics. Increase nchan_max_reserved_memory. Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: *770443 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/diagnostics?buffer_length=1 HTTP/1.1", host: "localhost" Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [crit] 2632135#2632135: ngx_slab_alloc() failed: no memory Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: shpool alloc failed Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: nchan: Out of shared memory while allocating channel /diagnostics. Increase nchan_max_reserved_memory. Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: *770444 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/diagnostics?buffer_length=1 HTTP/1.1", host: "localhost" Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [crit] 2632135#2632135: ngx_slab_alloc() failed: no memory Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: shpool alloc failed Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: nchan: Out of shared memory while allocating channel /diagnostics. Increase nchan_max_reserved_memory. Jan 13 20:33:55 Tower nginx: 2025/01/13 20:33:55 [error] 2632135#2632135: *770445 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/diagnostics?buffer_length=1 HTTP/1.1", host: "localhost" I was able to run diagnostics from the CLI while this is happening but I am not sure if it is anonymizing the sensitive information so I'm attaching a diagnostics that I was able to run after restarting my unraid server, which seems to be the only way I've been able to resolve this issue...until it happens again. If there is a way to anonymize the diagnostics from the CLI in case the attached doesn't highlight where my problem is since it was captured when the server was in a stable state? tower-diagnostics-20250113-2341.zip

Thanks for the information. I tried the steps for "Rebuilding a drive onto itself" and it appears to be re-creating the parity. Thanks!

As the title says, my Parity drive stopped working suddenly without reason. When I stopped the array, the drive was missing. After a power down and a jiggling of the cables, I booted the system up and it sees the drive however unRaid says that Parity is disabled, even though the drive is selected. I was able to run a full SMART test with no errors reported, but the system does not want to use it. Any suggestions on how to resolve this? I'm concerned about losing data without protection in place. TIA!

Strange, I tried to run the scrub from a different browser (Edge) and I can access the GUI page of the cache drive without issues. Not sure why that flickering is happening with Chrome and only on the cache drive gui but oh well. I have the scrub running now. In the meantime, if it finds uncorrectable errors, what should my next steps be?

Thanks for the reply. I tried running the stats command on my cache pool and had the following results: Looks like I do certainly have some integrity issues. When I try to go to the GUI to run the scrub command, the page just keeps flashing and I can't click anything. Not sure if that's related to my current issue or if its a bug. No other drives do this. I suppose I could run the scrub command from the CLI, I'll see if I can find the proper commands so that I don't accidentally delete my file system.

Hi all, I seem to be having this issue where my log file keeps filling up to 100%. When I try to view the log file through the interface, it shows up blank. I downloaded my diagnostics file and have attached it here. If someone could help me shed some light as to what or why my log keeps filling up, it would be greatly appreciated. Thanks! tower-diagnostics-20221226-0150.zip

OK, thank you for clarifying. I'll manage things manually for now until a solution is found.

Thanks, after my last post I did some research and decided to test the 6.4 RC since downgrading seemed simple. True to form (at least as it seems for me) it broke many things including my dockers (they disappeared) and I could not longer access shares from some of the systems on my network. I spent a couple hours of getting things fixed up and I am now running the latest 6.4RC and I am able to assign IPs to the dockers independent of the unRaid host IP which is what I wanted to do. The only issue I have now is that its not receiving IPs from my DHCP server but is assigning the IP itself. I do have the ability to assign the IP manually from the GUI however I prefer to leverage my DHCP server and assign reserved IPs for cleaner management. Not sure if this behavior is by design or if there's something that I can do alter it so that it behaves the way that I'd like. I'll do a search however if you have any advice to give I'd gladly accept it. Thanks!

Ah, OK. I glossed over that. I figured I was on the latest since it was reporting that there were no updates. Short of installing a RC of version 6.4, is there anything that I can do to get this working in my current version? I am running a few mission critical services on my unRaid (one of them being a Security Cam DVR) and I'd rather not risk any instability that inherently comes from early release software.

Thanks for the reply. I must be an idiot because I don't see anywhere it can be easily changed in the GUI. I did search for the instructions before and after posting this question. Every single article that I found links back to the original instructions on this thread. Is there another article that shows how this is done through the GUI?

OK, so I found this thread because I need to set up my Home Automation gateway docker to use port 80 which means it will require its own IP address. Unfortunately I'm not getting anywhere. I tried entering the commands on the first post and my unRaid manages to accept them all except for when I enter the last line: homenet When I press enter I get the following message: "docker network create" requires exactly 1 argument(s). See 'docker network create -[-help'. Specifics: I am running version 6.3.5 I have 1 nic Network info: Unraid: 192.168.0.133 Subnet 192.168.0.0/24 GW: 192.168.0.1 I did make the changes to the commands so that they reflected my subnet and not that of the instructions. Other than that, I've copied everything to the letter. Any suggestions?