errors in syslog - anything important?


Recommended Posts

Server is running great and no issues with performance, or anything else.  However I did notice a few log entries that I don't recall seeing the past.  They may have nothing to do with 6.5.3.

 

Server has been up for about 2 days and 9 hours, and I see 3 entries in my syslog:

 

Jun 29 03:41:13 Tower nginx: 2018/06/29 03:41:13 [error] 10391#10391: *296946 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost", referrer: "http://localhost/Main"
Jun 29 03:41:13 Tower php-fpm[10365]: [WARNING] [pool www] child 21260 exited on signal 7 (SIGBUS) after 264.591907 seconds from start


Jun 29 20:40:49 Tower nginx: 2018/06/29 20:40:49 [error] 10391#10391: *457950 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost", referrer: "http://localhost/Main"
Jun 29 20:40:49 Tower php-fpm[10365]: [WARNING] [pool www] child 9358 exited on signal 7 (SIGBUS) after 337.768022 seconds from start


Jun 30 16:16:14 Tower nginx: 2018/06/30 16:16:14 [error] 10391#10391: *618350 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost", referrer: "http://localhost/Main"
Jun 30 16:16:14 Tower php-fpm[10365]: [WARNING] [pool www] child 17068 exited on signal 7 (SIGBUS) after 289.569545 seconds from start

 

I also see the following warnings in my log:

 

Jun 28 07:46:17 Tower kernel: ACPI: Early table checksum verification disabled


Jun 28 07:46:17 Tower kernel: spurious 8259A interrupt: IRQ7.


Jun 28 07:46:17 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting


Jun 28 07:46:18 Tower rpc.statd[1769]: Failed to read /var/lib/nfs/state: Success
Jun 28 07:46:18 Tower rpc.statd[1769]: Initializing NSM state
Jun 28 07:46:18 Tower sshd[1787]: Server listening on 0.0.0.0 port 22.
Jun 28 07:46:18 Tower sshd[1787]: Server listening on :: port 22.


Jun 28 07:46:39 Tower sshd[1787]: Received signal 15; terminating.
Jun 28 07:46:39 Tower acpid: client connected from 10225[0:0]
Jun 28 07:46:39 Tower acpid: 1 client rule loaded
Jun 28 07:46:40 Tower sshd[10242]: Server listening on 0.0.0.0 port 22.
Jun 28 07:46:40 Tower sshd[10242]: Server listening on :: port 22.


Jun 28 07:46:41 Tower avahi-daemon[10335]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

 

Other than these few warnings / errors, my log is clean.

 

Do any of these look serious or important?

 

Thanks!

Link to comment

I found a couple more errors in the syslog.

 

Jul  5 04:29:24 Tower kernel: diskload cpuset=/ mems_allowed=0
Jul  5 04:29:24 Tower kernel: CPU: 5 PID: 10492 Comm: diskload Not tainted 4.14.49-unRAID #1
Jul  5 04:29:24 Tower kernel: Hardware name: Supermicro Super Server/X11SSM-F, BIOS 2.0a 03/09/2017
Jul  5 04:29:24 Tower kernel: Call Trace:

 

In the efforts to see if a clean syslog can be true, I post here again, and this time I include full syslog file.

 

Thank you

 

syslog.txt

Edited by Switchblade
wrong file
Link to comment
  • 4 weeks later...
18 minutes ago, Switchblade said:

I was hoping that LT would jump in here and help us figure out what these errors are,  but no luck so far.

 

Unlikely they have seen this thread. Looks like you failed in your attempt to get their attention since you did it wrong:

 

On 7/10/2018 at 10:01 AM, Switchblade said:

@ Limetech - any help here with these errors?  How can I resolve these so I have no errors?

 

You must type the 'at' sign, begin to type the name and then you must choose from the selections presented in order for the forum software to take any action.

 

Like this:

 

@Switchblade

Link to comment
54 minutes ago, Switchblade said:

thank you Trurl!

 

@Limetech - any help here with these errors?  How can I resolve these so I have no errors?

Looks like another fail. If you look at my post above you can see that @Switchblade is highlighted, but your attempt to "page" Limetech is not. What are you using to post to the forum?

  • Like 1
Link to comment

Those error messages in your first post are about resending web information between client (GUI) and server (unRAID). A reset indicates to start again with communication exchange.

Is expected to see if client and server have a misunderstanding between themselves, e.g. some packet loss or corruption. Can be ignored unless you have difficulties with the GUI, e.g. it is hanging.

 

Edited by bonienl
Link to comment

@limetech can you please see below errors and advise on how to resolve?

 

Aug 17 17:35:32 Tower nginx: 2018/08/17 17:35:32 [error] 10387#10387: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.
Aug 17 17:35:32 Tower nginx: 2018/08/17 17:35:32 [error] 10387#10387: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.

 

 

 

Link to comment
1 hour ago, Switchblade said:

@limetech can you please see below errors and advise on how to resolve?

 

Aug 17 17:35:32 Tower nginx: 2018/08/17 17:35:32 [error] 10387#10387: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.
Aug 17 17:35:32 Tower nginx: 2018/08/17 17:35:32 [error] 10387#10387: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.

 

 

 

 

Maybe drifting time that got corrected when the time client got in contact with a time server.

 

Maybe a time server that is bad at keeping track of time.

 

Have you configured the use of ntp to set the clock? And have you specified a good time server?

Link to comment
12 minutes ago, pwm said:

 

Maybe drifting time that got corrected when the time client got in contact with a time server.

 

Maybe a time server that is bad at keeping track of time.

 

Have you configured the use of ntp to set the clock? And have you specified a good time server?

 

I did not change anything from defaults.

 

What do you recommend?

 

timeserver.JPG

Link to comment
  • 1 month later...

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.