Error Setting Owner

[Fiservedpi]

Received this error today via email not sure what it's pertaining to besides the obvious something with nginx

error: error setting owner of /var/log/nginx/error.log to uid 0 and gid 0: Operation not permitted

 

tower-diagnostics-20190711-2120.zip

Edited July 11, 2019 by Fiservedpi

[Frank1940]

This is what I got looking at the details for this file: 

 

root@Rose:~# ls -al /var/log/nginx
total 4
drwxr-x--- 2 nobody root  60 Jul  2 11:55 ./
drwxr-xr-x 9 root   root 600 Jul  7 01:40 ../
-rw-r--r-- 1 root   root 444 Jul  4 19:31 error.log

What are you seeing?

[Fiservedpi]

2 hours ago, Frank1940 said:

This is what I got looking at the details for this file: 

 

root@Rose:~# ls -al /var/log/nginx
total 4
drwxr-x--- 2 nobody root  60 Jul  2 11:55 ./
drwxr-xr-x 9 root   root 600 Jul  7 01:40 ../
-rw-r--r-- 1 root   root 444 Jul  4 19:31 error.log

What are you seeing?

root@Tower:~# ls -al /var/log/nginx
total 6292                                                                                                                 
drwxr-x---  2 nobody root       80 Jul 11 04:40 ./
drwxr-xr-x 10 root   root      720 Jul 11 04:40 ../
-rw-------  1 nobody users       0 Jul 11 04:40 error.log                                                                  
-rw-r--r--  1 root   root  6439274 Jul 12 03:09 error.log.1   

i was reading an article pertaining to an issue with Safari Here in another forum but i do not use Safari, pulled some of the data from errolog1 and googled it 

 

"shpool alloc failed" this concerns me google eludes to pertaining to gpu mining nicehash, why would nginx be trying to allocate to a "pool" or i t may have to do with AES 

 

Jul 10 03:35:45 Tower nginx: 2019/07/10 03:35:45 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [crit] 7886#7886: ngx_slab_alloc() failed: no memory
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: shpool alloc failed
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: nchan: Out of shared memory while allocating message of size 9960. Increase nchan_max_reserved_memory.
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: *2021857 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost"
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks

 

Edited July 12, 2019 by Fiservedpi

[Frank1940]

I have now looked at my second server and the size of the error.log file is zero bytes and on the first server it is 444 bytes.  (The first server's error.log would be zero also if I have tried to log in with the CapsLock key on!  😏  )  Both of these servers have been running for more than ten days.  Yours after one (or two) days, has a size larger than 6.4million bytes.   I would suggest that you have a good look at the contents of error.log.1 and see if you can figure out what is going on.

 

you could get the file back to your flash drive (If it would be easier for you view the file there) with this command:

cp /var/log/nginx/error.log.1 /boot/logs  

One Question.  Have you exposed this server to the Internet in any fashion?  

[Fiservedpi]

One Question.  Have you exposed this server to the Internet in any fashion? = yes via port forwarding for plex, sab 

the majority 85% of error.log.1 is this repeated, 

looking into the nchan portion it seems to be some type of pub sub client that i have not installed i think there is something nefarious happening

 

Jul 10 03:35:45 Tower nginx: 2019/07/10 03:35:45 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [crit] 7886#7886: ngx_slab_alloc() failed: no memory
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: shpool alloc failed
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: nchan: Out of shared memory while allocating message of size 9960. Increase nchan_max_reserved_memory.
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: *2021857 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost"
Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks

 

Edited July 12, 2019 by Fiservedpi

[Frank1940]

I hope someone else can jump in here with some insight as I am out of my league with this type of problem.  

 

I will say that the problem is probably in 15% of the log before the repeated lines.  They are the result of those problems.  (As I said, this log file should be empty.)  

 

I would also boot the server in the safe mode and see if the problem is gone.  

2 hours ago, Fiservedpi said:

yes via port forwarding for plex, sab 

Is this access for clients to access content on the server, or to access Internet resources for media? 

[Fiservedpi]

Access to the docker the media lives on an Unmounted NAS

[golli53]

@Fiservedpi wondering what ended up happening here and if you got any resolution. I just got the same error on my server.

[Fiservedpi]

I don't believe I ever solved it it just went away with an Unraid update