Unraid OS version 6.12.2 available

[Frank1940]

2 hours ago, JustinChase said:

What else can i do to help diagnose/troubleshoot/solve this issue?

 

You were right in one of your earlier posts.  Most people are not having a problem.  (I just upgraded to 6.12.2 on my Main server and mapped drives are working!!!)

 

First thing.  I seem to recall this is a laptop.  It is not a company issued laptop, is it?   (Check with IT dept to see that you are are trying to do may be against their policy. They may also have applied some rules to try to stop what you are trying to do.)

 

Second thing. Check to make sure that your are connecting using the 'Private network' type.  Settings  >>>   Network & Internet

 

Third thing.  Go to this thread and download the PDF from the first post.  Verify the setting recommendations and see that you haven't missed something obvious. 

 

    https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

 

If you don't find a solution, might I suggest that you open a thread in the General Support sub-forum.  Solving this type of problem in the release thread is very difficult because of the other "noise". 

 

EDIT:  Be sure to reboot your Windows computer as SMB is easily confused in trying to sort things out out peer-to-peer networks.  (I use to recommend that one shut done every SMB device on the Network.  Make sure that your Unraid server is setup to become the Local Master.  Then restore the Unraid server, wait fifteen minutes minutes and restart all of the other devices.  Then go get a cup of coffee and doughnut.  Read the newspaper.  Then go back and see if things are working.) 

Edited July 5, 2023 by Frank1940

[JustinChase]

42 minutes ago, Frank1940 said:

 

You were right in one of your earlier posts.  Most people are not having a problem.  (I just upgraded to 6.12.2 on my Main server and mapped drives are working!!!)

 

First thing.  I seem to recall this is a laptop.  It is not a company issued laptop, is it?   (Check with IT dept to see that you are are trying to do may be against their policy. They may also have applied some rules to try to stop what you are trying to do.)

 

Second thing. Check to make sure that your are connecting using the 'Private network' type.  Settings  >>>   Network & Internet

 

Third thing.  Go to this thread and download the PDF from the first post.  Verify the setting recommendations and see that you haven't missed something obvious. 

 

    https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

 

If you don't find a solution, might I suggest that you open a thread in the General Support sub-forum.  Solving this type of problem in the release thread is very difficult because of the other "noise". 

 

EDIT:  Be sure to reboot your Windows computer as SMB is easily confused in trying to sort things out out peer-to-peer networks.  (I use to recommend that one shut done every SMB device on the Network.  Make sure that your Unraid server is setup to become the Local Master.  Then restore the Unraid server, wait fifteen minutes minutes and restart all of the other devices.  Then go get a cup of coffee and doughnut.  Read the newspaper.  Then go back and see if things are working.) 

Thanks for the help.

 

it's not a company laptop.  it has worked mostly flawlessly this way for a decade.  it's just the latest upgrade of unraid that has caused the issue.  i did not change anything on the laptop.

as I posted before, a previous upgrade caused the same issue, and reverting instantly restored full functionality.  I have not reverted simply because I'm hoping there are some actual troubleshooting steps I can take.

 

i will wait until after the US holiday and create a new post in general if there isn't any more feedback here.

[craigr]

2 minutes ago, JustinChase said:

Thanks for the help.

 

it's not a company laptop.  it has worked mostly flawlessly this way for a decade.  it's just the latest upgrade of unraid that has caused the issue.  i did not change anything on the laptop.

as I posted before, a previous upgrade caused the same issue, and reverting instantly restored full functionality.  I have not reverted simply because I'm hoping there are some actual troubleshooting steps I can take.

 

i will wait until after the US holiday and create a new post in general if there isn't any more feedback here.

 

I'm not having any issues, but I always map by IP not name.  Using IP is always considered good form.  I used to use network name, but a long time ago it suddenly stopped working inexplicably.  I never even try anymore.

 

 

vssd is a zfs pool, storage is a RAID0 BTRSF pools, cache is the cache drive, Media and Media_4K are user shares, and disk7 and disk18 are disc shares.  I think that covers the gamut.

[JustinChase]

1 minute ago, craigr said:

 

I'm not having any issues, but I always map by IP not name.  Using IP is always considered good form.  I used to use network name, but a long time ago it suddenly stopped working inexplicably.  I never even try anymore.

 

 

vssd is a zfs pool, storage is a RAID0 BTRSF pools, cache is the cache drive, Media and Media_4K are user shares, and disk7 and disk18 are disc shares.  I think that covers the gamut.

thank you, I appreciate the data point.

 

I have used the server name on multiple computers for over a decade without issue.  Even if it were unreliable, that is still an error and should be fixed.  But, in my case that has not been the case, and it has worked just fine.

 

With all that said, I have tried to connect with the IP address and that also fails.

 

 

Windows sees the server name just fine, but refuses to connect.

 

[craigr]

46 minutes ago, JustinChase said:

thank you, I appreciate the data point.

 

I have used the server name on multiple computers for over a decade without issue.  Even if it were unreliable, that is still an error and should be fixed.  But, in my case that has not been the case, and it has worked just fine.

 

With all that said, I have tried to connect with the IP address and that also fails.

 

 

Windows sees the server name just fine, but refuses to connect.

 

 

Try typing this n Windows Explorer:

\\192.168.20.150

 

 

Press enter.  Windows should prompt you for credentials.  Navigate to "backup" or whatever.  Right click and select "map network drive."

 

All that said, I think you may just be missing the "\\" backslashes.

Edited July 5, 2023 by craigr

[craigr]

 

I don't think you have the two backslashes?

[JustinChase]

5 minutes ago, craigr said:

 

I don't think you have the two backslashes?

 

 

I reverted to 6.12.0 and upon unraid server restarting (not my laptop), shares were instantly available with no further input from me.

 

I guess this is, once again, a formal bug report and no longer a request for help.

 

my system did no change, only the unraid version.  this points to unraid issue, not a me issue.

 

thanks again for trying to help

[enJOyIT]

But did you check if your network share is connected correctly, with "\\" at the beginning of your folder?

[bonienl]

3 hours ago, JustinChase said:

my system did no change, only the unraid version

 

Sometimes Windows gets confused. Did you try to reboot your Windows system?

In all my tests SMB is working fine in 6.12.2

 

[Frank1940]

11 hours ago, JustinChase said:

There is something about this new version that breaks the ability to map network drives on my laptop.

Well, Samba went from version 4.17.2 (Ver6.11.2)  to Version 4.17.7 (ver6.12.0).   Without checking, I suspect there was a security patch or two included in that update...

 

Remember that security is the name of the game these days.  SMB has had gigantic security holes from the days of Windows for Workgroups 3.11 released back in 1993.  (I can remember that it was possible for any one in the world to access the shared files via dialup internet by knowing the IP address of your dialup connection!)   In fact, it was possible for Windows for Workgroups 3.11 computer to work on a SMB network until fairly recently when Microsoft finally turn-off the SMBv1 access.  As I recall, Windows for Workgroups evolved into SMB in 1996 about the time of the Windows NT release.

 

A brief history for anyone who might not know.  The SMB protocol is the outgrowth of Windows for Workgroups and is controlled by Microsoft.  Samba is reversed engineered software of that protocol for the UNIX-like OS's.

 

Many Unraid users want very simple network setup that never requires change.  This often requires changes to Windows client computers as MS ships changes/additions to SMB security settings in its monthly updates.   There are usually ways to bypass those security patches.  But that has become a whack-a-mole type of response.  It is usually easier to just take the time and setup everything as a secure system.  Then any updates that happen on either side (SMB or samba) will not affect operation. 

Edited July 5, 2023 by Frank1940

[JustinChase]

5 hours ago, enJOyIT said:

But did you check if your network share is connected correctly, with "\\" at the beginning of your folder?

No, because I'd already rolled back before I saw that image. 

 

4 hours ago, bonienl said:

 

Sometimes Windows gets confused. Did you try to reboot your Windows system?

In all my tests SMB is working fine in 6.12.2

 

I rebooted the laptop about 4 times while I was running 6.12.2 and they never worked, and I could not re-map a drive

 

34 minutes ago, Frank1940 said:

Well, Samba went from version 4.17.2 (Ver6.11.2)  to Version 4.17.7 (ver6.12.0).   Without checking, I suspect there was a security patch or two included in that update...  It is usually easier to just take the time and setup everything as a secure system.  Then any updates that happen on either side (SMB or samba) will not affect operation. 

 

makes sense.  How would you recommend one begins this update to their security?  I'm not in love with SMB, it's just what i setup long ago, and has mostly worked fine for me.

I don't open any ports to the internet, (I run a ShieldsUp test regularly) and I'm not really worried about anyone on my wifi, so I'm not sure it's "necessary", but more security is usually good.

 

Thanks all for the help

 

[Frank1940]

16 minutes ago, JustinChase said:

I don't open any ports to the internet, (I run a ShieldsUp test regularly) and I'm not really worried about anyone on my wifi, so I'm not sure it's "necessary".....

Your position is very typical.  The problem is MS is not concerned with Windows Home users.  They are concerned about the Fortune 500 companies,  DOD, Government agencies, Health Care Providers, etc.   Those folks are vitally concerned.  (You probably see that about once a week some big organization will be hit by a Ransomware attack  and faced with a very difficult set of choices.)  Oh, and there have been a few Unraid users who have been hit by ransomware attacks over the past few years.  Probably, their infection was a cockpit type of mistake but still, a bit of security can help restrict the damage.  (Example, turnoff write access (or even total access) to shares for users/client-computers that don't require it!)

Edited July 5, 2023 by Frank1940

[orlando500]

On 7/4/2023 at 12:02 PM, NAStyBox said:

No, releasing crap code without basic testing is toxic. I say that as someone that has managed QA teams for a big 5 software shop. If it were something complex I wouldn't be so aggravated. But to put out code like this with a system that doesn't allow an easy rollback beyond the patch level is worthy of criminal legislation. 

As far as toxicity? I didn't ask you, did I?

you didnt ask me, but posted in a public forum so i responded...Your tone was way off. 

[realies]

On 7/4/2023 at 9:59 AM, bonienl said:

ip rule add sport 22 table main

This is not a standard rule and not included, how is this added to the configuration?

It was added manually to wg0.conf. It allows port 22 to be accessible after starting the VPN.

 

I think this is irrelevant and that it would be better if PostUp and PostDown values are not overwritten but mutated.

 

For example the OS upgrade script could check if they exist in the current config file, and if they do, append '; /some/script/path/here' to the end of the line instead of replacing the whole line.

[bonienl]

It is not advised to do manual changes, any configuration update thru the GUI will undo them.

 

[realies]

38 minutes ago, bonienl said:

It is not advised to do manual changes, any configuration update thru the GUI will undo them.

 

It might not be advised to do manual changes, but you can't ssh into the server when the VPN is on without this change.

[SpencerJ]

 

Adding this guide here for better visibility for any users having macvlan call trace issues.

[wgstarks]

54 minutes ago, SpencerJ said:

 

Adding this guide here for better visibility for any users having macvlan call trace issues.

You should be aware though that this isn’t a solution for everyone (myself included). After making these changes the callback traces persist. Wasn’t a big issue for me since I wasn’t still using the VLAN I just went ahead and switched to IPVLAN. Not sure what problems that may cause down the road though.

[elcapitano]

Busy processor.

Advanced view in Docker doesn't reveal anything.

master-diagnostics-20230705-1406.zip

[craigr]

5 minutes ago, wgstarks said:

You should be aware though that this isn’t a solution for everyone (myself included). After making these changes the callback traces persist. Wasn’t a big issue for me since I wasn’t still using the VLAN I just went ahead and switched to IPVLAN. Not sure what problems that may cause down the road though.

 

And I am using IPVLAN and the problems persist.

[bonienl]

18 hours ago, realies said:

It might not be advised to do manual changes, but you can't ssh into the server when the VPN is on without this change.

 

SSH works fine for me using Wireguard.

There are no specific rules for wireguard tunnels to stop SSH.

 

[bonienl]

17 hours ago, craigr said:

 

And I am using IPVLAN and the problems persist.

 

Like to see diagnostics

 

[realies]

7 minutes ago, bonienl said:

SSH works fine for me using Wireguard.

There are no specific rules for wireguard tunnels to stop SSH.

For me it only works via the local IP. Connecting from an external network however does not.

[craigr]

2 hours ago, bonienl said:

 

Like to see diagnostics

 

Please help.  I am about to undo my zfs pools and go back to 6.11.5.  I'm leaving town the end of next week and the server cannot be crashing.  It hasn't crashed yet, but my log will fill to 100% in the bar graph.  I dumped my syslog last night with "truncate -s 0 /var/log/" but luckily (cough) there are many new error this morning.  I also tried to truncating EVERY log file and the log percentage used dropped, but not all the way back do to 1-2% as it used to be.

 

Thank you!!!

unraid-diagnostics-20230706-1003.zip

[craigr]

2 hours ago, bonienl said:

 

Like to see diagnostics

 

Jul  6 09:32:01 unRAID nginx: 2023/07/06 09:32:01 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:01 unRAID nginx: 2023/07/06 09:32:01 [error] 9883#9883: *1553169 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:01 unRAID nginx: 2023/07/06 09:32:01 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25488. Increase nchan_max_reserved_memory.
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: *1553175 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: *1553181 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:02 unRAID nginx: 2023/07/06 09:32:02 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:03 unRAID nginx: 2023/07/06 09:32:03 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:03 unRAID nginx: 2023/07/06 09:32:03 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:03 unRAID nginx: 2023/07/06 09:32:03 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25484. Increase nchan_max_reserved_memory.
Jul  6 09:32:03 unRAID nginx: 2023/07/06 09:32:03 [error] 9883#9883: *1553183 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:03 unRAID nginx: 2023/07/06 09:32:03 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25484. Increase nchan_max_reserved_memory.
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: *1553194 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: *1553201 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:04 unRAID nginx: 2023/07/06 09:32:04 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25480. Increase nchan_max_reserved_memory.
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: *1553204 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: *1553209 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:05 unRAID nginx: 2023/07/06 09:32:05 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25480. Increase nchan_max_reserved_memory.
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: *1553216 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: *1553244 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:06 unRAID nginx: 2023/07/06 09:32:06 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:07 unRAID nginx: 2023/07/06 09:32:07 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:07 unRAID nginx: 2023/07/06 09:32:07 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:07 unRAID nginx: 2023/07/06 09:32:07 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25487. Increase nchan_max_reserved_memory.
Jul  6 09:32:07 unRAID nginx: 2023/07/06 09:32:07 [error] 9883#9883: *1553246 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:07 unRAID nginx: 2023/07/06 09:32:07 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: *1553251 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25487. Increase nchan_max_reserved_memory.
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: *1553257 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:08 unRAID nginx: 2023/07/06 09:32:08 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 22043. Increase nchan_max_reserved_memory.
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: *1553265 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /disks
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25481. Increase nchan_max_reserved_memory.
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: *1553266 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:09 unRAID nginx: 2023/07/06 09:32:09 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices
Jul  6 09:32:10 unRAID nginx: 2023/07/06 09:32:10 [crit] 9883#9883: ngx_slab_alloc() failed: no memory
Jul  6 09:32:10 unRAID nginx: 2023/07/06 09:32:10 [error] 9883#9883: shpool alloc failed
Jul  6 09:32:10 unRAID nginx: 2023/07/06 09:32:10 [error] 9883#9883: nchan: Out of shared memory while allocating message of size 25481. Increase nchan_max_reserved_memory.
Jul  6 09:32:10 unRAID nginx: 2023/07/06 09:32:10 [error] 9883#9883: *1553323 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  6 09:32:10 unRAID nginx: 2023/07/06 09:32:10 [error] 9883#9883: MEMSTORE:00: can't create shared message for channel /devices