nginx failed no memeory error filling syslog during parity check

[wirenut]

After upgrading to 6.7.0 and getting used to for the last couple weeks, decided it was time to upgrade to some larger discs. Started by rebuilding parity with two new 10TB parity drives. Rebuild went OK as anticipated, once finished kicked off a parity check to verify. Got up this morning to check progress and it was going well but noticed speed seemed about half what was expected as the parity check had completed past the point of the slower existing data discs. Took a glance at the syslog and found it to be filled with this repeating:

 

May 29 04:00:44 Tower nginx: 2019/05/29 04:00:44 [crit] 6636#6636: ngx_slab_alloc() failed: no memory May 29 04:00:44 Tower nginx: 2019/05/29 04:00:44 [error] 6636#6636: shpool alloc failed May 29 04:00:44 Tower nginx: 2019/05/29 04:00:44 [error] 6636#6636: nchan: Out of shared memory while allocating message of size 10567. Increase nchan_max_reserved_memory. May 29 04:00:44 Tower nginx: 2019/05/29 04:00:44 [error] 6636#6636: *100136 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost" May 29 04:00:44 Tower nginx: 2019/05/29 04:00:44 [error] 6636#6636: MEMSTORE:00: can't create shared message for channel /disks May 29 04:00:45 Tower nginx: 2019/05/29 04:00:45 [crit] 6636#6636: ngx_slab_alloc() failed: no memory May 29 04:00:45 Tower nginx: 2019/05/29 04:00:45 [error] 6636#6636: shpool alloc failed

 

I let it run awhile to see if errors stop and speed improves, even tried new pause feature, errors seem to have stopped but speed remained the same.

Not sure what is going on or what it means. only thing ive found from some time ago was tied to safari browser but i am using chrome and/or firefox.

Is it connected to disc speed not being what is expected during parity check verify or some other issue to be concerned with??

tower-diagnostics-20190530-1829.zip

[Fiservedpi]

I'm experiencing this to have you figured out if this is normal or something nefarious? why would nginx be pub/disk messaging 

Edited July 12, 2019 by Fiservedpi

[Squid]

2 minutes ago, Fiservedpi said:

why would nginx be pub/disk messaging 

The browser is communicating back and forth with the server.  Completely 100% normal

[Fiservedpi]

Ok thanks @Squid it occurred to me that this appears during party check I'm going to be adding a new 3.5 hd today then run a party check to see if it happens again

[Squid]

diagnostics might be a clue if you catch them while the error happens, but I suspect it may be a transient thing

[Fiservedpi]

Specifically July 10 

tower-diagnostics-20190712-1522.zip