Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

nginx running out of shared memory

Featured Replies

Hi there, I'm running 6.8.

 

I noticed all the live updating to the Dashboard webpage stopped working (no disk utilization bars updating, stuff like that) and under the Memory section the log bar was red+full. Here's are the types of messages in the logs:

 

Quote

Dec 12 12:31:09 Truesource nginx: 2019/12/12 12:31:09 [error] 25449#25449: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Dec 12 12:31:09 Truesource nginx: 2019/12/12 12:31:09 [error] 25449#25449: *330240 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [crit] 25449#25449: ngx_slab_alloc() failed: no memory
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [error] 25449#25449: shpool alloc failed
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [error] 25449#25449: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory.
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [error] 25449#25449: *330244 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [crit] 25449#25449: ngx_slab_alloc() failed: no memory
Dec 12 12:31:10 Truesource nginx: 2019/12/12 12:31:10 [error] 25449#25449: shpool alloc failed

I did a few searches and found sometimes the wrong web browser can cause this. I'm using Brave  Version 1.1.20 Chromium: 79.0.3945.74 (Official Build) (64-bit). I tried completely rebooting the client machine to see if the errors cleaned up. I'm going to leave the browser down overnight and see if any sort of self-healing occurs.

 

I'm attempting to use the gui to generate a diagnostics zip. It's been running for about 5 hours. If I can't get it to complete, what's the most useful information I can hand pull from the command line? Syslogs have seized up at size 70MB of error messages similar to the above with a final message that only partially got written to disk. Haven't had anything new in syslog since 12:31 am this morning. I can hand-execute the diagnostics steps and post something, just let me know if what may be useful. In the meantime, I've attached a snapshot of the memory section on the Dashboard.

 

Thank you for any help you can offer.

Annotation 2019-12-13 063345.png

  • Replies 268
  • Views 66.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • There is a possible fix for this in upcoming v7.0.1 release.

  • A probable fix for this is in 6.12 which is currently undergoing internal beta testing...

  • echocabinet
    echocabinet

    After another week, I have determined a few things:   Closing all tabs prevents the errors from building up/cascading.  The browser type doesnt seem to matter. Crashes/logs growing

Posted Images

  • Author

Syslogs attached. They compressed quite nicely.

syslog.7z

  • 4 weeks later...

I have the same issue. Have you been able to fix this?

  • 3 weeks later...

I'm running into the same issue. Any ideas on what's going on? 

Same issue here.

Same Issue here.  

Following.

 

However, did this and it seems to have fixed it.  Will keep an eye on the log and see if the errors come back on.

/etc/rc.d/rc.nginx restart

I have the exact same problem. restarting the service does seem to fix the issue for now. I will keep tabs on it as well

  • Author

When I captured that I was using Brave  Version 1.1.20 Chromium: 79.0.3945.74 (Official Build) (64-bit).

3 hours ago, DBJordan said:

When I captured that I was using Brave  Version 1.1.20 Chromium: 79.0.3945.74 (Official Build) (64-bit).

Please try FireFox or actual Chrome and see if issue persists.  This might give us a starting point.

  • 6 months later...

Anything come out of this ?  I have the max red bar on memory for the log and just keep getting this in the log ...

 

Aug 24 10:28:38 Vishnu nginx: 2020/08/24 10:28:38 [crit] 22944#22944: ngx_slab_alloc() failed: no memory
Aug 24 10:28:38 Vishnu nginx: 2020/08/24 10:28:38 [error] 22944#22944: shpool alloc failed
Aug 24 10:28:38 Vishnu nginx: 2020/08/24 10:28:38 [error] 22944#22944: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserved_memory.
Aug 24 10:28:38 Vishnu nginx: 2020/08/24 10:28:38 [error] 22944#22944: *444191 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/dockerload?buffer_length=0 HTTP/1.1", host: "localhost"

  • 2 weeks later...

run into the same problem with this message filling up the log

  • 2 months later...

Same problem here. 

 

System log is suddenly full of these messages: 

Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [alert] 7525#7525: worker process 21758 exited on signal 11
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [crit] 21883#21883: ngx_slab_alloc() failed: no memory
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21883#21883: shpool alloc failed
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21883#21883: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory.
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [alert] 21883#21883: *483824 header already sent while keepalive, client: 192.168.2.165, server: 0.0.0.0:80
Nov 29 10:05:45 Monsterservern kernel: nginx[21883]: segfault at 0 ip 0000000000000000 sp 00007fff9d8f5f58 error 14 in nginx[400000+22000]
Nov 29 10:05:45 Monsterservern kernel: Code: Bad RIP value.
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [alert] 7525#7525: worker process 21883 exited on signal 11
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [crit] 21884#21884: ngx_slab_alloc() failed: no memory
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: shpool alloc failed
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory.
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: *483826 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [crit] 21884#21884: ngx_slab_alloc() failed: no memory
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: shpool alloc failed
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: *483827 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [crit] 21884#21884: ngx_slab_alloc() failed: no memory
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: shpool alloc failed
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [error] 21884#21884: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserved_memory.
Nov 29 10:05:45 Monsterservern nginx: 2020/11/29 10:05:45 [alert] 21884#21884: *483828 header already sent while keepalive, client: 192.168.2.165, server: 0.0.0.0:80
Nov 29 10:05:45 Monsterservern kernel: nginx[21884]: segfault at 0 ip 0000000000000000 sp 00007fff9d8f5f58 error 14 in nginx[400000+22000]

On the dashboard the memory for the log is 100% full. 

monsterservern-diagnostics-20201129-1235.zip

Mine just happened again today...  @limetech, any thoughts on this?  It seems like there are several of us that have this issue?

  • 3 weeks later...

I am also having this exact same problem

What Unraid OS release?  Please update to 6.9 if not already on 6.9

I'm on 6.8.3 ...  Which I thought was the latest stable??  Are you saying we should try the latest beta?

28 minutes ago, jbuszkie said:

I'm on 6.8.3 ...  Which I thought was the latest stable??  Are you saying we should try the latest beta?

Yes, though it is "-rc" now.

I was just having an issue with what I thought was my USB stick, and after a long day of re-establishing my Unraid server on a new USB stick, I still seem to have issues. A little bit more digging and come to find out, I have a log at 100% and it is getting blasted with:

ngx_slab_alloc() failed: no memory
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: shpool alloc failed
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory.
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: *3142714 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [crit] 12904#12904: ngx_slab_alloc() failed: no memory
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: shpool alloc failed
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Dec 21 04:36:50 Kioshi nginx: 2020/12/21 04:36:50 [error] 12904#12904: *3142715 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"

So you are telling us to update to an RC version of Unraid and this issue will magically go away? Why did this just randomly start happening? I have been on 6.8.3 since it was released and just now I am having these issues? Something isn't adding up. Can you please explain further?

On 1/26/2020 at 6:15 PM, hugenbdd said:

Same Issue here.  

Following.

 

However, did this and it seems to have fixed it.  Will keep an eye on the log and see if the errors come back on.

/etc/rc.d/rc.nginx restart

Doing this temporarily fixes the issue, I'm much more interested in a permanent fix...

  • 4 weeks later...

Same issue here... Still on 6.8.3 and don't want to upgrade to an -rc branch as I don't have enough time to provide feedback on it.

/etc/rc.d/rc.nginx restart temporarily solved it, but we'll see for how long.

I'm having this problem too!

Jan 21 10:41:37 unraid nginx: 2021/01/21 10:41:37 [alert] 13333#13333: worker process 13334 exited on signal 6

repeats about 400,000 times between 1041 and 1331, and then just numerous numerous repeats of 

Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [crit] 32524#32524: ngx_slab_alloc() failed: no memory
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32524#32524: shpool alloc failed
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32524#32524: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory.
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [alert] 32524#32524: *9212036 header already sent while keepalive, client: 192.168.2.156, server: 0.0.0.0:80
Jan 21 13:31:19 unraid kernel: nginx[32524]: segfault at 0 ip 0000000000000000 sp 00007fff47105b28 error 14 in nginx[400000+21000]
Jan 21 13:31:19 unraid kernel: Code: Bad RIP value.
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [alert] 13333#13333: worker process 32524 exited on signal 11
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [crit] 32527#32527: ngx_slab_alloc() failed: no memory
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: shpool alloc failed
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory.
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: *9212037 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [crit] 32527#32527: ngx_slab_alloc() failed: no memory
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: shpool alloc failed
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: nchan: Out of shared memory while allocating channel /shares. Increase nchan_max_reserved_memory.
Jan 21 13:31:19 unraid nginx: 2021/01/21 13:31:19 [error] 32527#32527: *9212038 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/shares?buffer_length=1 HTTP/1.1", host: "localhost"
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [crit] 32527#32527: ngx_slab_alloc() failed: no memory
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32527#32527: shpool alloc failed
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32527#32527: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32527#32527: *9212039 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [crit] 32527#32527: ngx_slab_alloc() failed: no memory
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32527#32527: shpool alloc failed
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32527#32527: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [alert] 32527#32527: *9212040 header already sent while keepalive, client: 192.168.2.156, server: 0.0.0.0:80
Jan 21 13:31:20 unraid kernel: nginx[32527]: segfault at 0 ip 0000000000000000 sp 00007fff47105b28 error 14 in nginx[400000+21000]
Jan 21 13:31:20 unraid kernel: Code: Bad RIP value.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [alert] 13333#13333: worker process 32527 exited on signal 11
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [crit] 32534#32534: ngx_slab_alloc() failed: no memory
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32534#32534: shpool alloc failed
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32534#32534: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [alert] 32534#32534: *9212041 header already sent while keepalive, client: 192.168.2.100, server: 0.0.0.0:80
Jan 21 13:31:20 unraid kernel: nginx[32534]: segfault at 0 ip 0000000000000000 sp 00007fff47105b28 error 14 in nginx[400000+21000]
Jan 21 13:31:20 unraid kernel: Code: Bad RIP value.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [alert] 13333#13333: worker process 32534 exited on signal 11
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [crit] 32535#32535: ngx_slab_alloc() failed: no memory
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32535#32535: shpool alloc failed
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [error] 32535#32535: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
Jan 21 13:31:20 unraid nginx: 2021/01/21 13:31:20 [alert] 32535#32535: *9212042 header already sent while keepalive, client: 192.168.2.100, server: 0.0.0.0:80
Jan 21 13:31:20 unraid kernel: nginx[32535]: segfault at 0 ip 0000000000000000 sp 00007fff47105b28 error 14 in nginx[400000+21000]
Jan 21 13:31:20 unraid kernel: Code: Bad RIP value.

continuing until my logs file is full.

  • 1 month later...

My server has been doing this lately also.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.