October 26, 200817 yr /etc/rc.d/rc.unRAID syslog returns a syslog on the screen then stops with: /etc/rc.d/rc.unRAID: line 90: zip: command not found chmod: cannot access `/boot/logs/syslog.zip': No such file or directory Obviously it's looking for syslog.zip and can't find it, but I don't ever remember seeing that file and I can't imagine what would've happened to it. Where do I get it and what does it do? ls -l /boot/logs returns: root@Tower1:~# ls -l /boot/logs total 2540 -rwxr-xr-x 1 root root 488418 Sep 28 19:33 syslog-20080928-193351.txt* -rwxr-xr-x 1 root root 607269 Sep 28 19:33 syslog-20080928-193358.txt* -rwxr-xr-x 1 root root 184147 Sep 30 20:11 syslog-20080930-201111.txt* -rwxr-xr-x 1 root root 170177 Sep 30 22:43 syslog-20080930-224307.txt* -rwxr-xr-x 1 root root 172016 Oct 1 22:21 syslog-20081001-222137.txt* -rwxr-xr-x 1 root root 170834 Oct 1 22:47 syslog-20081001-224711.txt* -rwxr-xr-x 1 root root 284406 Oct 1 22:47 syslog-20081001-224721.txt* -rwxr-xr-x 1 root root 165435 Oct 2 20:18 syslog-20081002-201830.txt* -rwxr-xr-x 1 root root 164994 Oct 2 22:09 syslog-20081002-220933.txt* -rwxr-xr-x 1 root root 174348 Oct 3 13:16 syslog-20081003-131636.txt* root@Tower1:~#
October 26, 200817 yr It's looking for the zip binary to create the syslog.zip. The newer version handles the case the zip binary does not exist. You should still have the unzipped syslogs in the log directory What wll be missing is the latest version of the .zip file. I'll post a new version on google code this afternoon.
October 26, 200817 yr Since I think you are running the unmenu.awk web-interface, I have a package-manager "conf" file to download and install "zip" and "unzip" It is attached to this post: http://lime-technology.com/forum/index.php?topic=2595.msg21581#msg21581 Put it in the same folder as the other unmenu files, or in the /boot/packages folder, and then use the "Package Manager" feature to download and install zip and unzip. Joe L.
October 26, 200817 yr You should still have the unzipped syslogs in the log directory Yah I have those, but my problem is that I don't have any recent ones. In my post above the results of ls -l /boot/logs show only old logs. I'm not really concerned with having them as zip files, I just don't understand why there are no newer ones there. It seems like once it fills up with ten logs it quits saving new ones? Edit: Should a log be saved by a normal shutdown from the GUI or only when the powerbutton script is invoked?
October 26, 200817 yr Edit: Should a log be saved by a normal shutdown from the GUI or only when the powerbutton script is invoked? Both You can also do it on demand with /etc/rc.d/rc.unRAID syslog I have a new google projects page http://code.google.com/p/unraid-powercontrol/
October 26, 200817 yr The new version fixed it. Thanks. How many logs will it keep now? I noticed the new log made a total of eleven instead of ten. Did you increase the number kept?
October 26, 200817 yr The new version fixed it. Thanks. How many logs will it keep now? I noticed the new log made a total of eleven instead of ten. Did you increase the number kept? No it might be the log name pattern There is a variable called LOGSAVE=10 that defines how many to save. THis can be adjusted during install with LOGSAVE=NN inststallpkg powerdown-X.YY.tgz For now: run /etc/rc.d/rc.unRAID syslog do an ls -l /boot/logs copy the screen output and post it. Mine are named as syslog-YYYYMMDD-HHMMSS.txt This version does not save smartctl info automatically. I'm going to release another version that does shortlly. In order to save the smartctrl data install as SMARTCTL=YES installpkg powerdown-X.YY.tgz where X.YY is the version number
October 26, 200817 yr Linux 2.6.24.4-unRAID. root@Tower1:~# /etc/rc.d/rc.unRAID syslog Capturing information to syslog. Please wait... version[3226]: Linux version 2.6.24.4-unRAID (root@Develop) (gcc version 4.1.2) #10 Fri Jun 27 00:06:22 MDT 2008 /etc/rc.d/rc.unRAID: line 84: /boot/config/shares/*: No such file or directory status[3290]: State: STARTED status[3290]: D# Model / Serial Status Device status[3290]: 0 WDC WD7500AAKS- / WD-WCAPT06 DISK_OK sdb status[3290]: 1 SAMSUNG HD753LJ / S13UJ1KPC25901 DISK_OK sdc status[3290]: 2 SAMSUNG HD501LJ / S0MUJ1RP300879 DISK_OK sde status[3290]: 3 WDC WD5000AAJS- / WD-WCAS820 DISK_OK sdf status[3290]: 4 WDC WD5000AAKS- / WD-WCAPW02 DISK_OK sdg status[3290]: 5 ST3500630AS / 5QG DISK_OK sdd status[3290]: 6 SAMSUNG HD400LD / S0AXJ1LLB11984 DISK_OK hdg status[3290]: 7 ST3400633A / 3NF1SS6B DISK_OK hdf status[3290]: 8 WDC WD3200JB-00 / WD-WCAMR2263649 DISK_OK hde status[3290]: 9 Maxtor 6L200P0 / L40ZYASH DISK_OK hdh status[3290]: SMART overall health assessment status[3290]: /dev/hde: Use smartctl -h to get a usage summary status[3290]: /dev/hdf: Use smartctl -h to get a usage summary status[3290]: /dev/hdg: Use smartctl -h to get a usage summary status[3290]: /dev/hdh: Use smartctl -h to get a usage summary status[3290]: /dev/sda: Use smartctl -h to get a usage summary status[3290]: /dev/sdb: Use smartctl -h to get a usage summary status[3290]: /dev/sdc: Use smartctl -h to get a usage summary status[3290]: /dev/sdd: Use smartctl -h to get a usage summary status[3290]: /dev/sde: Use smartctl -h to get a usage summary status[3290]: /dev/sdf: Use smartctl -h to get a usage summary status[3290]: /dev/sdg: Use smartctl -h to get a usage summary status[3290]: No active PIDS on the array Removing old syslog: /boot/logs/syslog-20080928-193351.txt Saving current syslog: /boot/logs/syslog-20081026-150930.txt -rw-r--r-- 1 root root 155576 Oct 26 15:09 /boot/logs/syslog-20081026-150930.txt zip not installed. Consider installing to automatically zip current syslog root@Tower1:~# ls -l /boot/logs total 2368 -rwxr-xr-x 1 root root 607269 Sep 28 19:33 syslog-20080928-193358.txt* -rwxr-xr-x 1 root root 184147 Sep 30 20:11 syslog-20080930-201111.txt* -rwxr-xr-x 1 root root 170177 Sep 30 22:43 syslog-20080930-224307.txt* -rwxr-xr-x 1 root root 172016 Oct 1 22:21 syslog-20081001-222137.txt* -rwxr-xr-x 1 root root 170834 Oct 1 22:47 syslog-20081001-224711.txt* -rwxr-xr-x 1 root root 284406 Oct 1 22:47 syslog-20081001-224721.txt* -rwxr-xr-x 1 root root 165435 Oct 2 20:18 syslog-20081002-201830.txt* -rwxr-xr-x 1 root root 164994 Oct 2 22:09 syslog-20081002-220933.txt* -rwxr-xr-x 1 root root 174348 Oct 3 13:16 syslog-20081003-131636.txt* -rwxr-xr-x 1 root root 156868 Oct 26 13:11 syslog-20081026-131130.txt* -rw-r--r-- 1 root root 155576 Oct 26 15:09 syslog-20081026-150930.txt root@Tower1:~#
October 26, 200817 yr It's keeping 10 prior logs, then making the current one, so it ends up being 11 logs. My math logic is off a bit. As for the smartctl -h messages, this is probably due to different versions of smartctl, when the new version is installed on unRAID it should work ok. This particular test is for basic quick Health status I'll update it more as new tools are installed. My next goal is to include the spin control/power control inetd shell script in the install so it;s one bundled power control package.
November 3, 200817 yr I just give this power down script a try. the one i download is 1.02 from this link http://code.google.com/p/unraid-powercontrol/downloads/list However after i power up my unRAID again i found the parity check has kicked in apparently the power down script did not properly shutdown system. When i browse through log file i found the rc.unRAID did execute but there are two error in the shutdown process. i attached those errors in the following and would like to know anyone has this same issue or not. The unRAID software i am using is 4.3.3 /etc/rc.d/unRaid.rc:70, 294 -------------------------------------------------------------------------------------------- Nov 2 17:40:35 Tower smartctl[2553]: smartctl version 5.36 [i486-slackware-linux-gnu] Copyright © 200 2-6 Bruce Allen^M Nov 2 17:40:35 Tower smartctl[2553]: Home page is http://smartmontools.sourceforge.net/^M Nov 2 17:40:35 Tower smartctl[2553]: ^M Nov 2 17:40:35 Tower smartctl[2553]: =======> UNRECOGNIZED OPTION: n^M Nov 2 17:40:35 Tower smartctl[2553]: ^M Nov 2 17:40:35 Tower smartctl[2553]: Use smartctl -h to get a usage summary^M Nov 2 17:40:35 Tower smartctl[2553]: ^M Nov 2 17:40:35 Tower smartctl[2553]: smartctl version 5.36 [i486-slackware-linux-gnu] Copyright © 200 2-6 Bruce Allen^M **************************************************************************************** /etc/rc.d/rc.unRAID:74 Nov 2 17:40:35 Tower pspci[2561]: /etc/rc.d/rc.unRAID: line 74: lspci: command not found^M Nov 2 17:40:35 Tower lsmod[2564]: Module Size Used by^M Nov 2 17:40:35 Tower lsmod[2564]: md_mod 49992 0 ^M Nov 2 17:40:35 Tower lsmod[2564]: fuse 34580 1 ^M Nov 2 17:40:35 Tower lsmod[2564]: ide_disk 11904 0 ^M Nov 2 17:40:35 Tower lsmod[2564]: pata_jmicron 3712 0 ^M Nov 2 17:40:35 Tower lsmod[2564]: r8169 22148 0 ^M Nov 2 17:40:35 Tower lsmod[2564]: ahci 21508 0 ^M Nov 2 17:40:35 Tower lsmod[2564]: jmicron 2048 0 [permanent]^M Nov 2 17:40:35 Tower lsmod[2564]: ide_core 88236 2 ide_disk,jmicron^M Nov 2 17:40:35 Tower lsmod[2564]: libata 122552 2 pata_jmicron,ahci^M Nov 2 17:40:35 Tower ifconfig[2567]: eth0 Link encap:Ethernet HWaddr 00:21:85:1A:CD:0F ^M Nov 2 17:40:35 Tower ifconfig[2567]: inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:
November 3, 200817 yr Please see this FAQ entry: http://lime-technology.com/wiki/index.php?title=FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F
November 3, 200817 yr Please see this FAQ entry: http://lime-technology.com/wiki/index.php?title=FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F (1) I download package from link directly without any modification. Script was installed in GO script through installpkg (2) I check my unRAID software, the smartctl command i had in my system does not support "-n" option. this explain 1st error. (3) There is also no lspci command at my 4.3.3 unRAID server under /sbin or /bin. This explain 2nd error.
November 3, 200817 yr (1) I download package from link directly without any modification. Script was installed in GO script through installpkg (2) I check my unRAID software, the smartctl command i had in my system does not support "-n" option. this explain 1st error. (3) There is also no lspci command at my 4.3.3 unRAID server under /sbin or /bin. This explain 2nd error. Smartctl errors will not cause this problem. it will just not work and keep going. lspci not being existent will not cause this error, the script will just keep going. Enof line is not an issue because the script itself is installed from installpkg. How was the power off initiated?
November 3, 200817 yr For the end-of-line novices.... a free Windows text editor, notepad2, automatically handles end-of-line characters for both Linux and Windows files. http://www.flos-freeware.ch/notepad2.html In addition, if gives you syntax highlighting, line numbering, and a host of other features. And if you need to convert line endings, it has a simple menu option to do it.
November 3, 200817 yr Also as a test.... open a telnet window do /etc/rc.d/rc.unRAID stop capture any screen output and upload it looking for errors. Then do a df -v and a mount to see that the filesystems were unmounted. Something may be blocking it or still active or unable to be killed.
September 21, 200916 yr Bumping an old thread! Whats the status of this with 4.5b6? I admit i didn't read up about it and have been just pressing the power button on my UnRAID server an leaving it shut down, its seems to go through a shutdown procedure and then turn off (i.e. doesn't just turn off straight away, i see a load of console ext about various services shutting down). So - should I be pressing the power button to shutdown the server? Should I be shutting down some other way? The machine is headless, so dont really want to hook up a KB and monitor each time I want to shutdown!
April 13, 201016 yr Is the version of the powerdown script installed from unmenu 1.3 supposed to shut down when using the power button? Mine doesn't. Is there something I need to do besides install the script (and reinstall on reboot)? CTRL-ALT-DEL works fine just not the power button. I press the button and nothing happens on the console. I hold it down for a few seconds and the machine just turns off without running any script.
April 13, 201016 yr When installing the unRAID powerdown script, there may be an option to hook into the kernel settings. I'm not sure if you told it to or not. On my full Slackware-Current instance, I have it hooked in via: sysctl -w kernel.poweroff_cmd="/sbin/powerdown"
April 13, 201016 yr Is the version of the powerdown script installed from unmenu 1.3 supposed to shut down when using the power button? Mine doesn't. Is there something I need to do besides install the script (and reinstall on reboot)? CTRL-ALT-DEL works fine just not the power button. I press the button and nothing happens on the console. I hold it down for a few seconds and the machine just turns off without running any script. You might need to look in the BIOS to see if you can set an option for what the power button does when pressed. I do think you need to add something to the powerdown install sequence to get it to init on the press of the power button. With all that said, the easiest option is to plug in a keyboard and press CTRL-ALT-DEL. EDIT: I see I was beaten to the answer. If/When i get home tonight i will see if i can update the unmenu package so this can be given as an option when installing.
April 13, 201016 yr Is the version of the powerdown script installed from unmenu 1.3 supposed to shut down when using the power button? Mine doesn't. Is there something I need to do besides install the script (and reinstall on reboot)? CTRL-ALT-DEL works fine just not the power button. I press the button and nothing happens on the console. I hold it down for a few seconds and the machine just turns off without running any script. You might need to look in the BIOS to see if you can set an option for what the power button does when pressed. I do think you need to add something to the powerdown install sequence to get it to init on the press of the power button. With all that said, the easiest option is to plug in a keyboard and press CTRL-ALT-DEL. EDIT: I see I was beaten to the answer. If/When i get home tonight i will see if i can update the unmenu package so this can be given as an option when installing. I may have beaten you to it. I just edited my unmenu package for the powerdown add-on, and also fixed a different issue I discovered in /etc/acpi/acpi_handler.sh It was set to use the lime-tech supplied /usr/local/sbin/powerdown. It is now edited to use /sbin/powerdown when WeeboTech's powerdown command is installed via unMENU You can check to see what the current ctl-alt-del handler is set to, by typing: sysctl kernel.poweroff_cmd If it is set to /sbin/powerdown, then it is already set correctly. On my server, it was set to /sbin/poweroff. (Not what we want. That is a non-clean power off of the server.) You can set it by the command described in the previous post. (the newer unMENU package for powerdown I just uploaded to the SVN at google.code has the sysctl command to change it to point to /sbin/powerdown) Joe L.
April 15, 201016 yr (the newer unMENU package for powerdown I just uploaded to the SVN at google.code has the sysctl command to change it to point to /sbin/powerdown) I could not get mine to switch to /sbin/powerdown with unmenu_install132 using the -u update option. I resorted to cleaning out the unmenu and package directories and reinstalled completely using unmenu_install -i -d /boot/unmenu then re-enabling my packages including Clean Powerdown. That finally did the trick.
October 27, 201015 yr The last post is quite old - so it seems that this issue is fixed? Here is where I´m coming from: I can shutdown my server with the alt-ctl-del keystroke I have the powerdown script installed I can click on "powerdown" in unMENU and the server is doing the expected. There is no BIOS option where I can influence what the power button is doing ...if I push the power button nothing happens (unless I press some more seconds and it will stop immediately This is a 7 pages thread .... is someone willing to provide me with an advise to cut it short? Thanks a lot.
October 27, 201015 yr The last post is quite old - so it seems that this issue is fixed? Here is where I´m coming from: I can shutdown my server with the alt-ctl-del keystroke I have the powerdown script installed I can click on "powerdown" in unMENU and the server is doing the expected. There is no BIOS option where I can influence what the power button is doing ...if I push the power button nothing happens (unless I press some more seconds and it will stop immediately This is a 7 pages thread .... is someone willing to provide me with an advise to cut it short? Thanks a lot. Is there an option in the BIOS for ACPI? It must be enabled to capture the momentary press of a power button. The basic steps to figure out what happens when you momentarily press the power button is here: http://lime-technology.com/forum/index.php?topic=6078.0 Joe L.
October 29, 201015 yr Good morning Joe, I followed the description and here is the result: root@Tower:~# ps -ef | grep acpid | grep -v grep root 117 2 0 Oct26 ? 00:00:00 [kacpid] root 1405 1 0 Oct26 ? 00:00:00 /usr/sbin/acpid root@Tower:~# cat /proc/acpi/event button/power PWRF 00000080 00000001 root@Tower:/etc/acpi# grep power /etc/acpi/acpi_handler.sh # tmm - power off via webGui # power) /sbin/init 0 power) /usr/local/sbin/powerdown The last line indicates, that WeeboTech's powerdown package is NOT being used (....which is the only way how I'm able to power down my unRAID server. Any of the running processes e.g. Twonky Media Server do prevent to un-mount the disks and stop the array. I can´t even stop the array via the original menu). Anyhow I have to change the last line power) /sbin/powerdown to: /sbin/powerdown. Am I correct? How to do that to avoid that the change is being lost after the next reboot?
Archived
This topic is now archived and is closed to further replies.