[Solved] Errors in syslog after upgrade to v6.2


weirdcrap

Recommended Posts

Hi all,

 

Just upgraded to unRAID v6.2 on Sunday and when I was looking through my system log to resolve what I think is an unrelated issue I noticed some errors coming up.

 

dlandon suggested that the stack traces from my CPU might be related to my CPU over heating. When Plex is transcoding at full bore (97% cpu utilization) my CPU is reporting its temp as 60C which is toasty but not near the thermal threshold of the CPU. I cranked up the fan controller to high and it is still sitting at 60C so I will either need to invest in fans that push more CFMs of air or get an after market CPU cooler if I want to get the temps down further.

 

Specifically I seem to have had Python segfault on me which based on the log time occured a couple hours after upgrading from 6.19 to 6.2:

Sep 18 10:41:42 Node kernel: python[17518]: segfault at 2b043cd61ff8 ip 00002b0438283d9b sp 00002b043cd62000 error 6 in libpython2.7.so.1.0[2b0438214000+341000]
Sep 18 10:41:44 Node kernel: python[10080]: segfault at 2afc522c9ff8 ip 00002afc4a04fd9b sp 00002afc522ca000 error 6 in libpython2.7.so.1.0[2afc49fe0000+341000]
Sep 18 10:41:45 Node kernel: python[10132]: segfault at 2b4ffcbecff8 ip 00002b4ff494f57f sp 00002b4ffcbed000 error 6 in libpython2.7.so.1.0[2b4ff48ed000+341000]
Sep 18 10:41:47 Node kernel: python[10207]: segfault at 2ac0a7019ff8 ip 00002ac09ed9fd9b sp 00002ac0a701a000 error 6 in libpython2.7.so.1.0[2ac09ed30000+341000]
Sep 18 10:41:48 Node kernel: python[10268]: segfault at 2afc2b390ff8 ip 00002afc2310957f sp 00002afc2b391000 error 6 in libpython2.7.so.1.0[2afc230a7000+341000]

 

Plus some stack traces from my CPU:

Sep 19 22:30:42 Node kernel: WARNING: CPU: 0 PID: 27309 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Sep 19 22:30:42 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii
Sep 19 22:30:42 Node kernel: CPU: 0 PID: 27309 Comm: Threadpool work Not tainted 4.4.19-unRAID #1
Sep 19 22:30:42 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015
Sep 19 22:30:42 Node kernel: 0000000000000000 ffff8803c77ebee0 ffffffff8136a68e 0000000000000000
Sep 19 22:30:42 Node kernel: 00000000000000ec ffff8803c77ebf18 ffffffff8104a39a ffffffff81055502
Sep 19 22:30:42 Node kernel: fffffffffffffdfe 0000000000014f98 000000000000000d 000000000000a0b7
Sep 19 22:30:42 Node kernel: Call Trace:
Sep 19 22:30:42 Node kernel: [] dump_stack+0x61/0x7e
Sep 19 22:30:42 Node kernel: [] warn_slowpath_common+0x8f/0xa8
Sep 19 22:30:42 Node kernel: [] ? SyS_rt_sigsuspend+0x8f/0x9e
Sep 19 22:30:42 Node kernel: [] warn_slowpath_null+0x15/0x17
Sep 19 22:30:42 Node kernel: [] SyS_rt_sigsuspend+0x8f/0x9e
Sep 19 22:30:42 Node kernel: [] entry_SYSCALL_64_fastpath+0x12/0x6d
Sep 19 22:30:42 Node kernel: ---[ end trace 753ae045f3fb133e ]---

 

Sep 19 23:23:13 Node kernel: ------------[ cut here ]------------
Sep 19 23:23:13 Node kernel: WARNING: CPU: 2 PID: 14557 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Sep 19 23:23:13 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii
Sep 19 23:23:13 Node kernel: CPU: 2 PID: 14557 Comm: mono Tainted: G        W       4.4.19-unRAID #1
Sep 19 23:23:13 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015
Sep 19 23:23:13 Node kernel: 0000000000000000 ffff88075590bee0 ffffffff8136a68e 0000000000000000
Sep 19 23:23:13 Node kernel: 00000000000000ec ffff88075590bf18 ffffffff8104a39a ffffffff81055502
Sep 19 23:23:13 Node kernel: fffffffffffffdfe 0000000000015604 0000000000000002 0000000000000000
Sep 19 23:23:13 Node kernel: Call Trace:
Sep 19 23:23:13 Node kernel: [] dump_stack+0x61/0x7e
Sep 19 23:23:13 Node kernel: [] warn_slowpath_common+0x8f/0xa8
Sep 19 23:23:13 Node kernel: [] ? SyS_rt_sigsuspend+0x8f/0x9e
Sep 19 23:23:13 Node kernel: [] warn_slowpath_null+0x15/0x17
Sep 19 23:23:13 Node kernel: [] SyS_rt_sigsuspend+0x8f/0x9e
Sep 19 23:23:13 Node kernel: [] entry_SYSCALL_64_fastpath+0x12/0x6d
Sep 19 23:23:13 Node kernel: ---[ end trace 753ae045f3fb133f ]---

 

Here is my hardware info:

M/B: Gigabyte Technology Co., Ltd. - B85M-DS3H-A

CPU: Intel® Core™ i5-4460 CPU @ 3.20GHz

HVM: Enabled

IOMMU: Enabled

Cache: 256 kB, 1024 kB, 6144 kB

Memory: 32 GB (max. installable capacity 32 GB)

Network: eth0: 1000 Mb/s, full duplex, mtu 1500

 

I have the following Plugins installed: CA, DenyHosts, Dynamix Schedule, SSD Trim, Dynamix System Statistics, System Temperature, Enhanced Log Viewer, Fix Common Problems, Open Files, Pre Clear Disk, Recycle Bin, Server Layout, SSH, User Scripts, & Unassigned Devices.

 

I have the following Dockers: cadvisor, CouchPotato, Sonarr, Jackett, Headphones, Plex, & NZBGet.

node-diagnostics-20160920-0936.zip

Link to comment

That's Python 2.7, which is for 6.1.  When you upgrade to 6.2, you need to go to NerdTools and toggle all your installs off, then back on and Apply (I think?), to get the correct versions for 6.2 installed.  Then you may need to reboot.  I've added it to the Additional Upgrade Advice.

I did have to re-apply my sshfs install in NerdPack to get it working and when I applied that I recall that it went through and re-applied all of my packages including updating python (which is still on v2.7, specifically 2.7.12). I think that Python error was just a one time thing and I haven't seen it since.

 

I am a bit more concerned about those CPU stack traces.

Link to comment

But this is the diagnostics where it started with the 6.1 python, then it was uninstalled and the 6.2 one was installed, and you haven't rebooted yet.  I don't completely trust a system when major stuff has been replaced, especially when it means every vestige of a dependency has to be disentangled.  And then the segfaults occur, probably because of the earlier python or other upgrades.  After the segfaults, there's little point in looking at issues afterward, until after a reboot.  Please reboot and test again, see if it still happens.

Link to comment

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.