davidw4806 Posted February 28, 2013 Share Posted February 28, 2013 I have no idea what this all means or if it is a problem at all. I am using 5RC11. I also got this in an email. /bin/sh: line 1: 27271 Segmentation fault /usr/local/sbin/overtemp_shutdown.sh > /dev/null 2>&1 This is the log that comes up when I look at syslog. Feb 27 15:42:51 Tower sSMTP[6058]: Creating SSL connection to host Feb 27 15:42:51 Tower sSMTP[6058]: SSL connection using RC4-SHA Feb 27 15:42:56 Tower sSMTP[6058]: Sent mail for [email protected] (221 2.0.0 closing connection x5sm10171046oeb.6 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 15:47:02 Tower sSMTP[7238]: Creating SSL connection to host Feb 27 15:47:02 Tower sSMTP[7238]: SSL connection using RC4-SHA Feb 27 15:47:07 Tower sSMTP[7238]: Sent mail for root@[email protected] (221 2.0.0 closing connection ka6sm9981966obb.3 - gsmtp) uid=0 username=root outbytes=7366 Feb 27 16:04:18 Tower kernel: mdcmd (48): spindown 2 Feb 27 16:04:28 Tower kernel: mdcmd (49): spindown 1 Feb 27 16:37:01 Tower kernel: mdcmd (50): spindown 2 Feb 27 16:43:51 Tower sSMTP[22471]: Creating SSL connection to host Feb 27 16:43:52 Tower sSMTP[22471]: SSL connection using RC4-SHA Feb 27 16:43:56 Tower sSMTP[22471]: Sent mail for [email protected] (221 2.0.0 closing connection ad19sm10512759oec.0 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 16:47:02 Tower sSMTP[23389]: Creating SSL connection to host Feb 27 16:47:03 Tower sSMTP[23389]: SSL connection using RC4-SHA Feb 27 16:47:07 Tower sSMTP[23389]: Sent mail for root@[email protected] (221 2.0.0 closing connection d10sm10509696oeh.7 - gsmtp) uid=0 username=root outbytes=7357 Feb 27 17:44:43 Tower sSMTP[4855]: Creating SSL connection to host Feb 27 17:44:43 Tower sSMTP[4855]: SSL connection using RC4-SHA Feb 27 17:44:47 Tower sSMTP[4855]: Sent mail for [email protected] (221 2.0.0 closing connection gy3sm3153723igc.10 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 17:47:02 Tower sSMTP[5511]: Creating SSL connection to host Feb 27 17:47:02 Tower sSMTP[5511]: SSL connection using RC4-SHA Feb 27 17:47:06 Tower sSMTP[5511]: Sent mail for root@[email protected] (221 2.0.0 closing connection px9sm3830820igc.0 - gsmtp) uid=0 username=root outbytes=7357 Feb 27 18:24:14 Tower kernel: mdcmd (51): spindown 1 Feb 27 18:37:05 Tower kernel: mdcmd (52): spindown 2 Feb 27 18:44:45 Tower sSMTP[26195]: Creating SSL connection to host Feb 27 18:44:45 Tower sSMTP[26195]: SSL connection using RC4-SHA Feb 27 18:44:50 Tower sSMTP[26195]: Sent mail for [email protected] (221 2.0.0 closing connection s8sm3366107igs.0 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 18:47:05 Tower sSMTP[26863]: Creating SSL connection to host Feb 27 18:47:05 Tower sSMTP[26863]: SSL connection using RC4-SHA Feb 27 18:47:09 Tower sSMTP[26863]: Sent mail for root@[email protected] (221 2.0.0 closing connection wo8sm3372275igb.6 - gsmtp) uid=0 username=root outbytes=7357 Feb 27 19:45:39 Tower sSMTP[7728]: Creating SSL connection to host Feb 27 19:45:39 Tower sSMTP[7728]: SSL connection using RC4-SHA Feb 27 19:45:43 Tower sSMTP[7728]: Sent mail for davigmail.com (221 2.0.0 closing connection s8sm3581344igs.0 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 19:47:05 Tower sSMTP[8134]: Creating SSL connection to host Feb 27 19:47:06 Tower sSMTP[8134]: SSL connection using RC4-SHA Feb 27 19:47:10 Tower sSMTP[8134]: Sent mail for root@[email protected] (221 2.0.0 closing connection qn10sm7780854igc.6 - gsmtp) uid=0 username=root outbytes=7357 Feb 27 20:45:57 Tower sSMTP[24093]: Creating SSL connection to host Feb 27 20:45:57 Tower sSMTP[24093]: SSL connection using RC4-SHA Feb 27 20:46:02 Tower sSMTP[24093]: Sent mail for [email protected] (221 2.0.0 closing connection xd4sm3792716igb.3 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 20:47:05 Tower sSMTP[24530]: Creating SSL connection to host Feb 27 20:47:05 Tower sSMTP[24530]: SSL connection using RC4-SHA Feb 27 20:47:06 Tower kernel: smartctl[24533]: segfault at 3ffc ip b7586674 sp bff39990 error 4 in libc-2.11.1.so[b7510000+15c000] Feb 27 20:47:06 Tower kernel: preclear_disk.s[24537] general protection ip:809c302 sp:bfab173c error:1040 in bash[8048000+be000] Feb 27 20:47:09 Tower sSMTP[24530]: Sent mail for root@[email protected] (221 2.0.0 closing connection qn10sm7971891igc.6 - gsmtp) uid=0 username=root outbytes=7384 Feb 27 21:46:23 Tower sSMTP[7397]: Creating SSL connection to host Feb 27 21:46:23 Tower sSMTP[7397]: SSL connection using RC4-SHA Feb 27 21:46:26 Tower sSMTP[7397]: Sent mail for [email protected] (221 2.0.0 closing connection ih1sm8171066igc.3 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 21:47:05 Tower sSMTP[7650]: Creating SSL connection to host Feb 27 21:47:05 Tower sSMTP[7650]: SSL connection using RC4-SHA Feb 27 21:47:09 Tower sSMTP[7650]: Sent mail for root@[email protected] (221 2.0.0 closing connection ww6sm8175345igb.2 - gsmtp) uid=0 username=root outbytes=7384 Feb 27 22:46:47 Tower sSMTP[23864]: Creating SSL connection to host Feb 27 22:46:47 Tower sSMTP[23864]: SSL connection using RC4-SHA Feb 27 22:46:52 Tower sSMTP[23864]: Sent mail for [email protected] (221 2.0.0 closing connection wx2sm93606igb.4 - gsmtp) uid=0 username=root outbytes=7703 Feb 27 22:47:05 Tower sSMTP[24093]: Creating SSL connection to host Feb 27 22:47:05 Tower sSMTP[24093]: SSL connection using RC4-SHA Feb 27 22:47:09 Tower sSMTP[24093]: Sent mail for root@[email protected] (221 2.0.0 closing connection 3sm8343804igp.9 - gsmtp) uid=0 username=root outbytes=7384 Feb 27 23:00:02 Tower kernel: smartctl[27305]: segfault at 4 ip b778ef70 sp bfb8f670 error 4 in ld-2.11.1.so[b7780000+1d000] Feb 27 23:00:02 Tower kernel: sh[27271]: segfault at 811d96c ip 08071d3a sp bf938f60 error 4 in bash[8048000+be000] Feb 27 23:00:07 Tower crond[1125]: exit status 139 from user root /usr/local/sbin/overtemp_shutdown.sh 1>/dev/null 2>&1 Feb 27 23:00:07 Tower sSMTP[27315]: Creating SSL connection to host Feb 27 23:00:08 Tower sSMTP[27315]: SSL connection using RC4-SHA Feb 27 23:00:12 Tower sSMTP[27315]: Sent mail for root@[email protected] (221 2.0.0 closing connection vb15sm4250872igb.9 - gsmtp) uid=0 username=root outbytes=558 Feb 27 23:02:26 Tower kernel: swap_free: Bad swap file entry 00000200 Feb 27 23:02:26 Tower kernel: BUG: Bad page map in process hdparm pte:400000000000 pmd:bf6c0067 Feb 27 23:02:26 Tower kernel: addr:bfb09000 vm_flags:00100173 anon_vma:c36f7b40 mapping: (null) index:bffde Feb 27 23:02:26 Tower kernel: Pid: 27955, comm: hdparm Tainted: G B D O 3.4.26-unRAID #2 Feb 27 23:02:26 Tower kernel: Call Trace: Feb 27 23:02:26 Tower kernel: [] print_bad_pte+0x16a/0x17c Feb 27 23:02:26 Tower kernel: [] zap_pte_range+0x237/0x2fb Feb 27 23:02:26 Tower kernel: [] unmap_page_range+0x14b/0x157 Feb 27 23:02:26 Tower kernel: [] ? release_pages+0x136/0x13e Feb 27 23:02:26 Tower kernel: [] unmap_single_vma+0x68/0x70 Feb 27 23:02:26 Tower kernel: [] unmap_vmas+0x30/0x47 Feb 27 23:02:26 Tower kernel: [] exit_mmap+0x77/0xd2 Feb 27 23:02:26 Tower kernel: [] mmput+0x1f/0x90 Feb 27 23:02:26 Tower kernel: [] exit_mm+0xde/0xe6 Feb 27 23:02:26 Tower kernel: [] do_exit+0x1d4/0x29e Feb 27 23:02:26 Tower kernel: [] ? vfs_write+0xff/0x110 Feb 27 23:02:26 Tower kernel: [] do_group_exit+0x66/0x8f Feb 27 23:02:26 Tower kernel: [] sys_exit_group+0x13/0x17 Feb 27 23:02:26 Tower kernel: [] syscall_call+0x7/0xb Feb 27 23:02:26 Tower kernel: swap_free: Bad swap file entry 00000200 Feb 27 23:02:26 Tower kernel: BUG: Bad page map in process hdparm pte:400000000000 pmd:bf6c0067 Feb 27 23:02:26 Tower kernel: addr:bfb1b000 vm_flags:00100173 anon_vma:c36f7b40 mapping: (null) index:bfff0 Feb 27 23:02:26 Tower kernel: Pid: 27955, comm: hdparm Tainted: G B D O 3.4.26-unRAID #2 Feb 27 23:02:26 Tower kernel: Call Trace: Feb 27 23:02:26 Tower kernel: [] print_bad_pte+0x16a/0x17c Feb 27 23:02:26 Tower kernel: [] zap_pte_range+0x237/0x2fb Feb 27 23:02:26 Tower kernel: [] unmap_page_range+0x14b/0x157 Feb 27 23:02:26 Tower kernel: [] ? release_pages+0x136/0x13e Feb 27 23:02:26 Tower kernel: [] unmap_single_vma+0x68/0x70 Feb 27 23:02:26 Tower kernel: [] unmap_vmas+0x30/0x47 Feb 27 23:02:26 Tower kernel: [] exit_mmap+0x77/0xd2 Feb 27 23:02:26 Tower kernel: [] mmput+0x1f/0x90 Feb 27 23:02:26 Tower kernel: [] exit_mm+0xde/0xe6 Feb 27 23:02:26 Tower kernel: [] do_exit+0x1d4/0x29e Feb 27 23:02:26 Tower kernel: [] ? vfs_write+0xff/0x110 Feb 27 23:02:26 Tower kernel: [] do_group_exit+0x66/0x8f Feb 27 23:02:26 Tower kernel: [] sys_exit_group+0x13/0x17 Feb 27 23:02:26 Tower kernel: [] syscall_call+0x7/0xb Feb 27 23:02:26 Tower kernel: BUG: Bad rss-counter state mm:f7404e00 idx:2 val:-2 Quote Link to comment
Joe L. Posted February 28, 2013 Share Posted February 28, 2013 With as many different (possibly memory related) issues, I'd start with an overnight memory test. Joe L. Quote Link to comment
davidw4806 Posted February 28, 2013 Author Share Posted February 28, 2013 Ok, thank you, I will try that and see what pops up Quote Link to comment
davidw4806 Posted March 1, 2013 Author Share Posted March 1, 2013 I did a memtest and it showed 833 errors almost immediately. I decided to pull out the two 2GB sticks and only keep the remaining 1GB sticks and ran the test again, this time no errors. So the server is now running on only 2GB but it is running fine for the moment. Thanks for the help. Quote Link to comment
Joe L. Posted March 1, 2013 Share Posted March 1, 2013 I did a memtest and it showed 833 errors almost immediately. I decided to pull out the two 2GB sticks and only keep the remaining 1GB sticks and ran the test again, this time no errors. So the server is now running on only 2GB but it is running fine for the moment. Thanks for the help. It may be the memory, or it might be the voltage, clock speed, or timing settings. Usually the BIOS will set it, but some get it wrong, especially when you have a mix of memory modules. It must be set as specified by the memory manufacturer for the specific memory strips. Your other memory strips might work if you set their voltage/timing/clock speed manually. (but now, at least, you know what was your main issue) Joe L. Quote Link to comment
Recommended Posts
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.