Now that's an explicit message in the log. Profit!Īnd now when the power button is pressed, a line like below appears in /var/log/messages, /var/log/syslog and /var/log/user.log: logger: in /etc/acpi/powerbtn.sh, presumably Power button pressed Also, Debian 8 probably does it differently. Notice than Ubuntu 14.04 does it differently ( /etc/acpi/powerbtn.sh already exists with different content from acpid package).
#How to check why citect io server stopped upgrade
The latter option would probably lose its effect on next upgrade of package acpi-support-base. Logger in /etc/acpi/powerbtn.sh, presumably "Power button pressed"ĭoing it this way will probably make a longer lasting change than modifying /etc/acpi/powerbtn-acpi-support.sh. Adjusting for better logsĪnyway, to get an explicit message I put the text below (as root) in a newly created /etc/acpi/powerbtn.sh made executable with chmod a+x /etc/acpi/powerbtn.sh I would expect that string to be logged automatically by the shutdown program. Notice that an explicit text is given as parameter of the shutdown command. sbin/shutdown -h -P now "Power button pressed" # which is still around because it was changed by the admin # Compatibility with old config script from acpid packageĮlif then Reading /etc/acpi/powerbtn-acpi-support.sh which includes:
The other solutions mentioned ( last -x) did not help much. Grep through /var/log would tell the time the machine was shut down, show proper daemons shutdown, etc, but not the initial reason. I had a similar need on a Debian 7.8 and observe that basically there's no clear and explicit message in log, which is a little surprising. We use head to keep the latest 10 events and we use tac to invert the ordering so that we don't get confused by the fact that last prints from most recent to least recent event. The special users reboot and shutdown log in when the system reboots Records are printed from most recent to least recent. *: Here's the description of last from its man page: last prints information about connect times of users. If you have a UPS and running a daemon to monitor power and shutdown you should obviously check its logs (NUT logs on /var/log/messages but apcupsd logs on /var/log/apcupsd*)
When the system shuts down due to overheating you get logs like this: critical temperature reached.,shutting down Only when the system shuts down orderly you get logs like this: rsyslogd. When the system powers off because user pressed the power button you get logs like this: systemd-logind: Power key pressed. Systemd-journald: File /var/log/journal/./system.journal corrupted or uncleanly shut down, renaming and replacing. When an unexpected power off or hardware failure occurs the filesystems will not be properly unmounted so in the next boot you may get logs like this: EXT4-fs. *: Power Button\|watching system buttons\|Stopped Cleaning Up\|Started Crash recovery kernel' \ Sun Jun 17 15:40 - 09:51 (18:11)Ī bash command to filter the most interesting log messages is this: grep -iv ': starting\|kernel. <- then we've a boot WITHOUT a prior shutdown <- the system was running since this momemnt Fri Aug 10 15:58 - 15:32 (2+23:34)Īn unexpected shutdown from power loss looks like this (note that you have a system boot event without a prior system shutdown event): runlevel (to lvl 3). <- first the system shuts down (init level 0) In some cases you may see this (note that there is no line about the shutdown but the system was at runlevel 0 which is the "halt state"): runlevel (to lvl 0). Run this command* and compare the output to the examples below: last -x | head | tacĪ normal shutdown and power-up looks like this (note that you have a shutdown event and then a system boot event): runlevel (to lvl 0) 2.6.32- Sat Mar 17 08:48 - 08:51 (00:02) | grep -iw 'recover*\|power*\|shut*down\|rsyslogd\|ups'ġ) Regarding the output of last -x command var/log/messages /var/log/syslog /var/log/apcupsd* \ Use these 2 commands and keep reading for more information.
0 kommentar(er)
