ultimz

Upgraded and all went well. Thanks to all that contributed to this release!

Upgraded from 6.12.10 to 6.12.11 - no issues experienced. Thanks so much to everyone who worked on this!

Will do. Thanks @Squid

Hi, Hope someone can assist me. I am seeing the following error: /var/log is getting full (currently 100 % used) If I check the log I think it's due to this: Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: nchan: Out of shared memory while allocating message of size 14853. Increase nchan_max_reserved_memory. Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: *5801161 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: MEMSTORE:00: can't create shared message for channel /disks Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [crit] 29546#29546: ngx_slab_alloc() failed: no memory Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: shpool alloc failed Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: nchan: Out of shared memory while allocating message of size 14853. Increase nchan_max_reserved_memory. Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: *5801163 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: MEMSTORE:00: can't create shared message for channel /disks Jun 18 03:31:44 Server-Unraid nginx: 2024/06/18 03:31:44 [crit] 29546#29546: ngx_slab_alloc() failed: no memory Jun 18 03:31:44 Server-Unraid nginx: 2024/06/18 03:31:44 [error] 29546#29546: shpool alloc failed Diagnostic logs attached. I am rebooting now. server-unraid-diagnostics-20240620-1912.zip

Thanks @JorgeB!

Thanks @JorgeB! I was able to do a clean shutdown and checked cables. Server came back up and just had to rebuild disk3. Appreciate the assistance with this. Attached fresh diagnostics. server-unraid-diagnostics-20240606-0549.zip

Hi, I woke up to a read error and a disk that had been disabled so trying to figure out what to do. I have pulled Diagnostics (attached) and am trying to stop the array to shut down the server to check cables but the server doesn't want to stop the array... I can still logon to the server but it's not behaving correctly (e.g. CPU stats show no activity on home page). Trying to stop the array and it comes up with a Proceed or Cancel but if I click Proceed it doesn't do anything. Any assistance would be appreciated. Thanks server-unraid-diagnostics-20240605-1636.zip

I am now running 8.1.127 Is that normal behavior for the container to show it has an update even though my tag is set to 11notes/unifi:8.1.113-unraid? Seems strange...

Hi, I have my repository/tag set to 11notes/unifi:8.1.113-unraid Noticed this morning that the container said it had an update available. Did the update and the version (specified in the container) updated to 8.1.127 yet my repository/tagtag is still set to 11notes/unifi:8.1.113-unraid Is this normal? Edit: everything seems to be working fine after the update

Update went through smoothly. Thanks to the Unraid team

Just moved to this docker from the unsupported one. Thanks it seems to have worked without any issues. I did change port 1900 to 1901 to match my old docker settings. Also had to backup from v7.3.83 and do the restore on v7.5.187 which seemed to work fine as well.

Sorry my bad... I was trying to access the gui through NPM and that was stopped when I stopped the array... I had to use the IP.

Hi, I was about to do the upgrade to 6.12.6 but when trying to stop the array (running 6.12.4) it got stuck on "Stopping services"... now I can't get into the GUI but I have managed to get into the shell and download diagnostics which are attached. Is anyone able to help me figure out why it's stuck? I was going to reboot the server using powerdown -r but can wait. server-unraid-diagnostics-20240125-0839.zip

Thanks again @yogy - seems to have worked... I'll test and post back if I pick up any issues. I have just set WEBSOCKET_ENABLED to false and removed the port mapping for 3012

Perfect thanks @yogy that worked