Can anyone offer advice on the errors that I am getting in my syslog?, these only started today. (I've had to reduce the size of the syslog so that I could upload it

 

Edit: full syslog now attached

 

Thanks

 

Zaxxan

syslog-2011-02-06.zip

Can't help you with interpreting the syslog - sorry.  But you would likely be able to upload the WHOLE log if you zipped it up first.

Can't help you with interpreting the syslog - sorry.  But you would likely be able to upload the WHOLE log if you zipped it up first.

 

I can't believe I didn't think of that! anyway I have now attached the full log.

syslog-2011-02-06.zip

Can't help you with interpreting the syslog - sorry.  But you would likely be able to upload the WHOLE log if you zipped it up first.

Other than it looking like you've run out of free memory.

As mentioned, if you can zip up the entire syslog it might show the events leading to the messages.

Otherwise, nothing you can do but stop the array and reboot and see if they continue.

 

I'd do a memory test if you've not done one in a while, just to be sure it is not a contributing factor.

 

Joe L.

Hi Joe, I have attached the full zipped log. I tried rebooting but the errors returned. The only changes I have made recently are: upgraded to 4.7, upgraded unMenu (last night) and added a second SATA SIL3132 card. I have 2gb of memory.

syslog-2011-02-06.zip

I've added more memory and ran a memtest for 24hours and evrything is OK, I've tried 4.6 and 4.7 and I get the errors on both. The errors seem to start when unmenu starts, is this anything to worry about or can I ignore them?

 

Feb 12 10:26:18 unRAID unmenu-status: Starting unmenu web-server

Feb 12 10:26:22 unRAID kernel: 86

Feb 12 10:26:22 unRAID kernel:  00000000 00000000 f74b2080 00000246 f749ff88 c1033aca c6e05780 c1030970

Feb 12 10:26:22 unRAID kernel: Call Trace: (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1003398>] ? kernel_thread_helper+0x0/0x1a (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033aca>] ? prepare_to_wait+0x41/0x46 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1030970>] ? __call_usermodehelper+0x0/0x59 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c10314db>] worker_thread+0x81/0x15f (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c103391d>] ? autoremove_wake_function+0x0/0x30 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c103145a>] ? worker_thread+0x0/0x15f (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033869>] kthread+0x61/0x68 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033808>] ? kthread+0x0/0x68 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c100339f>] kernel_thread_helper+0x7/0x1a (Errors)

I've added more memory and ran a memtest for 24hours and evrything is OK, I've tried 4.6 and 4.7 and I get the errors on both. The errors seem to start when unmenu starts, is this anything to worry about or can I ignore them?

 

Feb 12 10:26:18 unRAID unmenu-status: Starting unmenu web-server

Feb 12 10:26:22 unRAID kernel: 86

Feb 12 10:26:22 unRAID kernel:  00000000 00000000 f74b2080 00000246 f749ff88 c1033aca c6e05780 c1030970

Feb 12 10:26:22 unRAID kernel: Call Trace: (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1003398>] ? kernel_thread_helper+0x0/0x1a (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033aca>] ? prepare_to_wait+0x41/0x46 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1030970>] ? __call_usermodehelper+0x0/0x59 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c10314db>] worker_thread+0x81/0x15f (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c103391d>] ? autoremove_wake_function+0x0/0x30 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c103145a>] ? worker_thread+0x0/0x15f (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033869>] kthread+0x61/0x68 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c1033808>] ? kthread+0x0/0x68 (Errors)

Feb 12 10:26:22 unRAID kernel:  [<c100339f>] kernel_thread_helper+0x7/0x1a (Errors)

I hate to put it so bluntly... but

Stop using unmenu. 

 

Post a copy of your syslog.  You are apparently trying to start unmenu multiple times?

Feb  6 12:39:10 unRAID unmenu-status: Starting unmenu web-server

Feb  6 12:43:41 unRAID in.telnetd[6293]: connect from 192.168.0.2 (192.168.0.2)

Feb  6 12:43:44 unRAID login[6294]: ROOT LOGIN  on `pts/0' from `192.168.0.2'

Feb  6 12:44:09 unRAID unmenu-status: Starting unmenu web-server

Feb  6 12:44:35 unRAID unmenu-status: Exiting unmenu web-server, exit status code = 141

Feb  6 12:44:35 unRAID unmenu-status: Starting unmenu web-server

Feb  6 12:44:35 unRAID unmenu[6003]: awk: ./unmenu.awk:306: fatal: can't open two way socket `/inet/tcp/8080/0/0' for input/output (No such file or directory)

Feb  6 12:44:35 unRAID unmenu-status: Exiting unmenu web-server, exit status code = 2

Feb  6 12:44:35 unRAID unmenu[6003]: unmenu.awk unable to open port.  It  may already be running

Feb  6 12:44:45 unRAID unmenu-status: Starting unmenu web-server

Feb  6 12:44:45 unRAID unmenu[6003]: awk: ./unmenu.awk:306: fatal: can't open two way socket `/inet/tcp/8080/0/0' for input/output (No such file or directory)

Feb  6 12:44:45 unRAID unmenu-status: Exiting unmenu web-server, exit status code = 2

Feb  6 12:44:45 unRAID unmenu[6003]: unmenu.awk unable to open port.  It  may already be running

Feb  6 12:44:55 unRAID unmenu-status: Starting unmenu web-server

Feb  6 12:44:55 unRAID unmenu[6003]: awk: ./unmenu.awk:306: fatal: can't open two way socket `/inet/tcp/8080/0/0' for input/output (No such file or directory)

Feb  6 12:44:55 unRAID unmenu-status: Exiting unmenu web-server, exit status code = 2

Feb  6 12:44:55 unRAID unmenu-error: Fatal error:Exiting uu, unmenu may already be running, exit status=2

Feb  6 13:08:59 unRAID kernel: mdcmd (12): spindown 5

Feb  6 13:22:31 unRAID kernel: mdcmd (13): spindown 0

Feb  6 13:31:12 unRAID emhttp: shcmd (28): /usr/sbin/hdparm -y /dev/hda >/dev/null

Feb  6 13:58:24 unRAID kernel: mdcmd (14): spindown 1

Feb  6 16:39:01 unRAID unmenu[6318]: No sensors found!

Feb  6 16:39:01 unRAID unmenu[6318]: Make sure you loaded all the kernel drivers you need.

Feb  6 16:39:01 unRAID unmenu[6318]: Try sensors-detect to find out which these are.

 

Hi Joe,

 

I have attached the full syslog as requested.

 

I really would not want to stop using unmenu as I find the program very useful and appreciate the time and effort that you have put into it. I have checked my 'go' file:-

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

 

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

/boot/unmenu/uu

 

ethtool -s eth0 wol g

# Execute s3.sh sleep script

fromdos < /boot/custom/bin/s3.sh | at now + 1 minute

 

Obviously I would prefer to correct any errors rather than stop using unmenu.

 

thanks

 

Zaxxan

syslog-2011-02-12.zip

fromdos < /boot/custom/bin/s3.sh | at now + 1 minute

This line is probably causing the problem.    I suspect it is not correctly using the "at" command.

 

Please attach a zipped copy of your s3.sh script.

Thanks Joe.

 

I have attached the S3 script.

 

EDIT:

 

I think I have found the culprit. I commented out the lines for the S3 script and unmenu and I was still getting the errors. I then removed the second SATA card that I had added and rebooted and the syslog is now Ok.

 

Not sure why the second card would give these errors, but I will leave it un-installed for now.

 

Sorry for wasting peoples time on this, in hindsight I should have checked this first.

 

Zaxxan

 

s3.zip