June 30, 20233 yr 9 hours ago, itimpi said: The log filling up is abnormal behaviour. Have you looked in the /var/log folder to see what is taking up too much space? If it is the syslog file then you should look at the contents of that file to see if you have some sort of error message being continually repeated? Without knowing the answer to those questions nobody is going to be able to know if the update might have addressed your issue. 6 hours ago, Kilrah said: Someone answered (me), but you didn't even go to check it seems. I spoke too soon. I have this error repeating every one second between Jun 30 03:30:47 through Jun 30 03:31:07. Then it stops. I know that I didn't intervene because I was asleep. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [crit] 9772#9772: ngx_slab_alloc() failed: no memory Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: shpool alloc failed Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: nchan: Out of shared memory while allocating message of size 25353. Increase nchan_max_reserved_memory. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: *192051 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: MEMSTORE:00: can't create shared message for channel /devices Help again please?
June 30, 20233 yr 9 hours ago, RikStigter said: I've been having the same for a while now on my HP Microserver Gen10. Replacing the USB drive did not solve this. After I run chkdsk on a Windows system on this drive, it updates normally, although it doesn't find any problems with the drive. I'm curious to know if you have the same experience once you done that. Checking on windows took time and generated lots of chunks in FOUND.000 on the drive. I didn't do much more with it. Restored backup to old drive I had at home for like 10+ years so I have to replace it again soon. Only strange thing I see now is that the write/read led on the USB-stick is always on. It shouldn't be. The old one didn't have any leds so can't compare. Had trouble accessing the drive and had to reboot. I don't know if it's hardware or software.. Edited June 30, 20233 yr by Niklas
June 30, 20233 yr 9 minutes ago, craigr said: I spoke too soon. I have this error repeating every one second between Jun 30 03:30:47 through Jun 30 03:31:07. Then it stops. I know that I didn't intervene because I was asleep. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [crit] 9772#9772: ngx_slab_alloc() failed: no memory Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: shpool alloc failed Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: nchan: Out of shared memory while allocating message of size 25353. Increase nchan_max_reserved_memory. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: *192051 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: MEMSTORE:00: can't create shared message for channel /devices Help again please? Do you leave a browser tab open on android device or similar? If tab is not active the messages are queue until browser can recv. But runs out of mem
June 30, 20233 yr Upgrade both of my unRAID servers, one successfully, but another boots immediately into an error. No getting around this so have to resort to backup
June 30, 20233 yr 52 minutes ago, SimonF said: Do you leave a browser tab open on android device or similar? If tab is not active the messages are queue until browser can recv. But runs out of mem I don't own any android devices except for Shield TV's that are used for video playback with Kodi and Plex, never browsers. It's possible that I had another Windows or Ubuntu machine open last night with another browser on unRAID. Typically, the only unRAID browser open is on the Windows 11 VM running on unRAID its self.
June 30, 20233 yr 54 minutes ago, SimonF said: Do you leave a browser tab open on android device or similar? If tab is not active the messages are queue until browser can recv. But runs out of mem OK, I had my Windows 11 laptop on an unRAID browser last night while I was working on the upgrade from 6.12.1 to 6.12.2. I think I left the laptop on and the battery ran out at 03:31:07. Does this seem like a plausible scenario? Thank you!
June 30, 20233 yr 1 hour ago, craigr said: OK, I had my Windows 11 laptop on an unRAID browser last night while I was working on the upgrade from 6.12.1 to 6.12.2. I think I left the laptop on and the battery ran out at 03:31:07. Does this seem like a plausible scenario? Thank you! Not seen on windows but could be
June 30, 20233 yr On 6/29/2023 at 8:24 PM, Kilrah said: What's the docker downgrade expected to solve? I am hoping it fixed /run running out of space ??
July 1, 20233 yr just a warning to others, going to 6.12.1 half of my dockers disappeared and had to be reinstalled, now I had to reinstalled all my dockers as they all disappeared after this update to 6.12.2, lucky the appdata and xml are all there. Edited July 1, 20233 yr by mickr777
July 1, 20233 yr 5 hours ago, NAStyBox said: Where can I download 6.11.5? https://unraid.net/download
July 1, 20233 yr I haven't noticed any major increase in memory usage from Docker, so I'll be staying on 6.12.1 for a while. I hope that 6.12.3 or later releases will reintroduce Docker v23. Fingers crossed
July 1, 20233 yr 21 hours ago, NAStyBox said: Actually I have the backup file for 6.11.4. How does one roll back to it? You can use the Unraid USB Creator - choose "Local Zip" instead of "Stable" and point it to your backup.
July 3, 20233 yr The Wireguard changes to this release locked me out of a remote server. This is because the interfaces properties PostUp and PostDown in the WG Interfaces config section are overwritten instead of appending the new config there. In my instance, PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started';/usr/local/emhttp/webGui/scripts/update_services PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped';/usr/local/emhttp/webGui/scripts/update_services Should have been PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started';ip rule add sport 22 table main;/usr/local/emhttp/webGui/scripts/update_services PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped';ip rule del sport 22 table main;/usr/local/emhttp/webGui/scripts/update_services Edited July 3, 20233 yr by realies
July 3, 20233 yr Is there a documented process of converting the main cache from BTRFS to a ZFS cache? Thanks for any help.
July 3, 20233 yr One of the Docker containers got unresponsive in 6.12.1 and attempting to reboot to 6.12.2 got the machine stuck in an unknown state. Had to manually press the reset button.
July 3, 20233 yr 2 minutes ago, JoeUnraidUser said: Is there a documented process of converting the main cache from BTRFS to a ZFS cache? Thanks for any help. Check this out
July 3, 20233 yr On 7/1/2023 at 3:02 AM, NAStyBox said: Where can I download 6.11.5, and how can I roll back to it from this 6.12.1/2 trash? NO, I don't want to send in any data or fix something that never should have been released. Actually I have the backup file for 6.11.4. How does one roll back to it? Wow a bit toxic.. what went so wrong that you have to be that salty?
July 3, 20233 yr On 6/30/2023 at 9:58 AM, craigr said: I spoke too soon. I have this error repeating every one second between Jun 30 03:30:47 through Jun 30 03:31:07. Then it stops. I know that I didn't intervene because I was asleep. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [crit] 9772#9772: ngx_slab_alloc() failed: no memory Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: shpool alloc failed Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: nchan: Out of shared memory while allocating message of size 25353. Increase nchan_max_reserved_memory. Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: *192051 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jun 30 03:30:55 unRAID nginx: 2023/06/30 03:30:55 [error] 9772#9772: MEMSTORE:00: can't create shared message for channel /devices Help again please? I got the same issue here.....and I can't find any answer. Please someone ..... and for now my server stop working for no reason and that begins I'm pretty sure after 6.12.x update. bugz-diagnostics-20230703-1340.zip bugz-syslog-20230703-1739.zip
July 3, 20233 yr 36 minutes ago, Jimmy said: I got the same issue here.....and I can't find any answer. Please someone ..... and for now my server stop working for no reason and that begins I'm pretty sure after 6.12.x update. Your system has call traces related to macvlan, see https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues Doing a lot of back and forth in a release post is tough, I'd recommend making your own thread for further discussion
July 3, 20233 yr 3 hours ago, ljm42 said: Your system has call traces related to macvlan, see https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues Doing a lot of back and forth in a release post is tough, I'd recommend making your own thread for further discussion I'll start a thread, but I'm Coffee Lake here. unraid-diagnostics-20230703-1654.zip unraid-syslog-20230703-2156.zip Edited July 3, 20233 yr by craigr
July 3, 20233 yr 26 minutes ago, craigr said: I'll start a thread, but I'm Coffee Lake here. There are two known issues mentioned in the release notes
July 3, 20233 yr Since this update the webgui will work for a day or so but then it stops displaying the drives in NAS and doesn't have any info for the CPU, GPU, interface, system, etc. Only a reboot brings them back. All my dockers work and the System Stats app shows this info.
July 3, 20233 yr Upgraded from 6.11.X, and got same error as this user when trying to start docker container that binds to port 443 on host: Quote Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use. As with OP, I had to change 'HTTPS port' to some random value under Settings/ManagementAccess, although 'Use SSL/TLS' has always been set to No. Is this an intentional change or a regression?
July 4, 20233 yr 6 hours ago, ljm42 said: There are two known issues mentioned in the release notes I don't have a Rocket lake CPU and I already have my Docker set to ipvlan. What am I missing here? Edited July 4, 20233 yr by craigr
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.