A couple of questions on some Syslog notifications:

 

Should I be concerned about this warning?

 

Oct 11 11:06:44 Tower kernel: ACPI Warning (tbutils-0242): Incorrect checksum in table [OEMB] - 98, should be 97 [20081204]

 

All of my drives are connected via MB and I only have a PCI Express graphics card installed:

 

Are these messages normal if I'm using unmenu on a PC and monitoring my server simultaneously:

 

Oct 11 10:40:33 Tower unmenu[1372]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory

Oct 11 10:41:06 Tower unmenu[1372]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory

Oct 11 10:41:30 Tower unmenu[1372]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory

Oct 11 10:43:44 Tower unmenu[1372]: gawk: ./08-unmenu-array_mgmt.awk:115: warning: escape sequence `\'' treated as plain `''

 

Also, I noticed this warning in my syslog:

 

Oct 11 10:40:00 Tower atd[1754]: Exec failed for mail command: No such file or directory

 

Any thoughts?

 

EDIT:  I tried to test the mail notification by unplugging my UPC cable and this is what was reported in my Syslog:

 

Oct 11 10:50:00 Tower atd[1751]: Exec failed for mail command: No such file or directory

Oct 11 10:50:00 Tower kernel: usb 7-2: USB disconnect, address 2

 

I followed Joe's steps from here and created the /boot/custom/bin directory as well as typing the commands as listed:

 

http://lime-technology.com/forum/index.php?topic=1528.msg40231#msg40231

Reply #170

A couple of questions on some Syslog notifications:

 

Should I be concerned about this warning?

 

Oct 11 11:06:44 Tower kernel: ACPI Warning (tbutils-0242): Incorrect checksum in table [OEMB] - 98, should be 97 [20081204]

 

I can help with the above.  This is fairly common with certain motherboards, and although it is right that it is being reported, should be ignored.  It is harmless.  Probably in the future with either a kernel upgrade or a BIOS upgrade, it will go away.

 

The other syslog messages all appear to be related to Add Ons, they are not from unRAID itself, and they all look harmless.  You may not have had the full custom folder structure set up, and there are some very minor bugs in a few of the scripts you have added.  Of course, you may also not have mail set up correctly, others can help you with that.

The second warning message about mail is easy to explain too.  unRAID does not have a working "mail" command unless you installed one.  The "at" command you are using to invoke some add-on process sends mail to alert the person running it it invoked it at the time specified... but it could not send the mail...  (It needs a real mail command executable, the script versions will not do)  You can just ignore it too.

 

 

Thanks guys!  I'm still having trouble getting e-mail notifications to work though.  It could be that I didnt have this in my go file:

 

echo "[email protected]" >/root/.forward

 

Otherwise, I'm lost.  I'm just trying to make sure that if my UPC kicks in that I will be notified.