LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 04-29-2012, 10:23 PM   #1
packets
Member
 
Registered: Oct 2005
Posts: 282

Rep: Reputation: 30
shutdown on its own


This is the first time I experience this issue on Fedora 15. Most of the server I manage is running RHEL and CentOS and haven't encountered this kind of issue. The issue is the server sometimes turn off by itself usually 2 - 3 days. The reason I know it because when I tried to check it physically, the PSU is not running anymore. There is no shutdown commands in cron. I'm not sure if the PSU is defective but I'm wondering if there are daemon running on the server that doing this shutdown.

I notice this daemon running.

Code:
gdm       2575  2470  0 10:05 ?        00:00:00 gnome-power-manager
Could this be somehow related to my server? This server has been running a year now and this just happen a couple of weeks ago.

Below is the last log from boot.log

Code:
Failed to load SELinux policy.

Welcome to ESC[0;34mFedora release 15 (Lovelock)ESC[0m!

Starting Collect Read-Ahead Data...
Starting Replay Read-Ahead Data...
Starting Bootup hack...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Started Lock Directory.
Starting Media Directory...
Started Runtime Directory.
Started Collect Read-Ahead Data.
Started Replay Read-Ahead Data.
Started Load legacy module configuration.
Started File System Check on Root Device.
Starting Remount Root FS...
Starting Remount API VFS...
Started Load Kernel Modules.
Started Set Up Additional Binary Formats.
Starting Apply Kernel Variables...
Starting Setup Virtual Console...
Starting Apply System Clock UTC Offset...
Starting Stdio Syslog Bridge...
Started Stdio Syslog Bridge.
Started Apply Kernel Variables.
Started Media Directory.
Started Bootup hack.
Started Remount API VFS.
Started Remount Root FS.
Starting Configure read-only root support...
Started Setup Virtual Console.
Started Apply System Clock UTC Offset.
Starting udev Kernel Device Manager...
Started udev Kernel Device Manager.
Starting udev Coldplug all Devices...
Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
Started udev Kernel Device Manager.
Started Configure read-only root support.
Starting /dev/mapper/vg_officesystem-lv_swap...
Started /dev/mapper/vg_officesystem-lv_swap.
Starting File System Check on /dev/disk/by-uuid/55f92803-b9a1-44c8-8c6e-2109db23d35d...
systemd-fsck[605]: /dev/sda1: recovering journal
systemd-fsck[605]: /dev/sda1: clean, 46/128016 files, 86222/512000 blocks
Started File System Check on /dev/disk/by-uuid/55f92803-b9a1-44c8-8c6e-2109db23d35d.
Starting /boot...
Started udev Wait for Complete Device Initialization.
Starting Wait for storage scan...
Started Show Plymouth Boot Screen.
Started /boot.
Started Wait for storage scan.
Starting Initialize storage subsystems (RAID, LVM, etc.)...
Starting File System Check on /dev/mapper/vg_officesystem-lv_home...
Started Initialize storage subsystems (RAID, LVM, etc.).
Starting Initialize storage subsystems (RAID, LVM, etc.)...
systemd-fsck[642]: /dev/mapper/vg_officesystem-lv_home: recovering journal
Started Initialize storage subsystems (RAID, LVM, etc.).
systemd-fsck[642]: /dev/mapper/vg_officesystem-lv_home: clean, 232362/26959872 files, 23329399/107823104 blocks
Started File System Check on /dev/mapper/vg_officesystem-lv_home.
Starting /home...
Started /home.
Started Mark the need to relabel after reboot.
Starting Enable all detected swap partitions...
Started Relabel all filesystems, if necessary.
Started Reconfigure the system on administrator request.
Starting Load Random Seed...
Starting Tell Plymouth To Write Out Runtime Data...
Starting Recreate Volatile Files and Directories...
Started Enable all detected swap partitions.
Started Load Random Seed.
Started Tell Plymouth To Write Out Runtime Data.
Started Recreate Volatile Files and Directories.
Starting Console System Startup Logging...
Starting Restore Sound Card State...
Starting Bootup unhack...
Starting Job spooling tools...
Started Job spooling tools.
Starting Network Manager...
Starting Network Time Service...
Started Network Time Service.
Starting Avahi mDNS/DNS-SD Stack...
Starting System Logging Service...
Starting ABRT Automated Bug Reporting Tool...
Starting SYSV: Init script for live image....
Starting Command Scheduler...
Started Command Scheduler.
Starting irqbalance daemon...
Starting Machine Check Exception Logging Daemon...
Starting System Setup Keyboard...
Started System Setup Keyboard.
Starting D-Bus System Message Bus...
Started Console System Startup Logging.
Started Restore Sound Card State.
Started Bootup unhack.
Started SYSV: Init script for live image..
Started irqbalance daemon.
Started Machine Check Exception Logging Daemon.
Starting SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot.  This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off....
Started D-Bus System Message Bus.
Started SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot.  This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off..
Starting LSB: Port reservation utility...
Starting LSB: Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Starting LSB: start and stop ip6tables firewall...
Starting LSB: Starts and stops login iSCSI daemon....
Started Avahi mDNS/DNS-SD Stack.
Started ABRT Automated Bug Reporting Tool.
Stopping Syslog Kernel Log Buffer Bridge...
Stopped Syslog Kernel Log Buffer Bridge.
Started LSB: Port reservation utility.
Started System Logging Service.
Started Network Manager.
Started LSB: start and stop ip6tables firewall.
Started LSB: Starts and stops login iSCSI daemon..
Started LSB: Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Starting SYSV: This starts the Linux Auditing System Daemon, which collects security related events in a dedicated audit log. If this daemon is turned off, audit events will be sent to syslog....
Started SYSV: This starts the Linux Auditing System Daemon, which collects security related events in a dedicated audit log. If this daemon is turned off, audit events will be sent to syslog..
Starting LSB: Installs coredump handler which saves segfault data...
Starting LSB: Starts and stops login and scanning of iSCSI devices....
Starting LSB: processor frequency scaling support...
Starting LSB: Start up the OpenSSH server daemon...
Starting LSB: Link Layer Discovery Protocol Agent Daemon...
Starting LSB: Mount and unmount network filesystems....
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: The CUPS scheduler...
Starting LSB: start and stop sendmail...
Starting LSB: Watches system log for oops messages, creates ABRT dump directories for each oops...
Started LSB: Installs coredump handler which saves segfault data.
Started LSB: processor frequency scaling support.
Started LSB: Start up the OpenSSH server daemon.
Started LSB: Watches system log for oops messages, creates ABRT dump directories for each oops.
Started LSB: Link Layer Discovery Protocol Agent Daemon.
Started LSB: Start and stop the MD software RAID monitor.
Started LSB: The CUPS scheduler.
Started LSB: start and stop sendmail.
Started LSB: Starts and stops login and scanning of iSCSI devices..
Started LSB: Mount and unmount network filesystems..
Starting LSB: Asterisk PBX...
Starting LSB: start and stop MySQL server...
Starting Permit User Sessions...
Started Permit User Sessions.
Started LSB: Asterisk PBX.
Started LSB: start and stop MySQL server.
Starting SYSV: Enable monthly update of Smolt...
Started SYSV: Enable monthly update of Smolt.
Starting SYSV: Late init script for live image....
Starting /etc/rc.local Compatibility...
Started SYSV: Late init script for live image..
Starting smb (via systemctl):  ESC[60G[ESC[0;32m  OK  ESC[0;39m]^M
Activating firewall script generated Fri Jun 24 16:22:02 2011 by admin
Running prolog script
# Removing ip address: p33p1 10.10.0.8/24
# Removing ip address: p1p1 10.4.0.1/24
Verifying interfaces: p33p1 p1p1 lo
Rule 0 (NAT)
Rule 1 (NAT)
Rule 0 (p33p1)
Rule 1 (global)
Rule 2 (lo)
Rule 3 (global)
Rule 4 (p33p1)
Rule 5 (global)
Rule 6 (global)
Rule 7 (global)
Rule 8 (p1p1)
Rule 9 (global)
Running epilog script
Starting named (via systemctl):  ESC[60G[ESC[0;32m  OK  ESC[0;39m]^M
Starting vncserver (via systemctl):  ESC[60G[ESC[0;32m  OK  ESC[0;39m]^M
I also display here the output of chkconfig runlevel 5

Code:
root@officesystem log]# chkconfig --list | grep 5:on

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

abrt-ccpp       0:off   1:off   2:off   3:on    4:off   5:on    6:off
abrt-oops       0:off   1:off   2:off   3:on    4:off   5:on    6:off
asterisk        0:off   1:off   2:on    3:on    4:on    5:on    6:off
auditd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
cpuspeed        0:off   1:on    2:on    3:on    4:on    5:on    6:off
cups            0:off   1:off   2:on    3:on    4:on    5:on    6:off
ip6tables       0:off   1:off   2:on    3:on    4:on    5:on    6:off
iscsi           0:off   1:off   2:off   3:on    4:on    5:on    6:off
iscsid          0:off   1:off   2:off   3:on    4:on    5:on    6:off
livesys         0:off   1:off   2:off   3:on    4:on    5:on    6:off
livesys-late    0:off   1:off   2:off   3:on    4:on    5:on    6:off
lldpad          0:off   1:off   2:on    3:on    4:on    5:on    6:off
lvm2-monitor    0:off   1:on    2:on    3:on    4:on    5:on    6:off
mdmonitor       0:off   1:off   2:on    3:on    4:on    5:on    6:off
mysqld          0:off   1:off   2:on    3:on    4:on    5:on    6:off
netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off
portreserve     0:off   1:off   2:on    3:on    4:on    5:on    6:off
sandbox         0:off   1:off   2:off   3:off   4:off   5:on    6:off
sendmail        0:off   1:off   2:on    3:on    4:on    5:on    6:off
smolt           0:off   1:off   2:on    3:on    4:on    5:on    6:off
sshd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
 
Old 04-30-2012, 12:03 AM   #2
blue_print
Member
 
Registered: May 2010
Location: In world
Distribution: RHEL, CentOS, Ubuntu
Posts: 275
Blog Entries: 3

Rep: Reputation: 49
Can you check /var/log/messages file? Do you find any logs before the system got rebooted or halted?
 
Old 04-30-2012, 02:37 AM   #3
packets
Member
 
Registered: Oct 2005
Posts: 282

Original Poster
Rep: Reputation: 30
Nope. All I can see on messages is logs from iptables. Same goes to dmesg.
 
Old 04-30-2012, 03:12 AM   #4
cascade9
Senior Member
 
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 3,718

Rep: Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904
It could be the PSU, but that is just one of many causes of hardware shutdowns. Overheating is more common.
 
Old 04-30-2012, 07:18 AM   #5
packets
Member
 
Registered: Oct 2005
Posts: 282

Original Poster
Rep: Reputation: 30
Ok. I just found out that it is the faulty UPS. The battery is already drain and servers connected to it are being shutdown. Geezzz. I think its time to buy a new UPS.

Thanks to all who gave their inputs. Such a good feeling to have a community willing to help.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Where I can locate Shutdown log for Linux Shutdown (RHL 5.1-2.6.18-53.el5PAE) msmallya Linux - General 2 04-23-2010 01:56 AM
Unable to shutdown/reboot server, no shutdown process running dctw Linux - Server 5 03-31-2010 05:46 AM
User shutdown - 'cp -i -p shutdown /usr/sbin/shutdown2 - why does this not work, can? mitchellray Linux - Desktop 4 03-20-2009 09:31 PM
Please help on how to save services shutdown or shutdown from the terminal. wambuzz Linux - General 2 03-11-2005 07:38 AM
konsole shutdown possible? or key combo = shutdown possible? Laptop2250 Linux - Newbie 3 11-16-2003 10:44 AM


All times are GMT -5. The time now is 08:30 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration