Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello
I'm trying to find out why my server is powering off by itself. I would like to know where the problem is. It seems to be a cron job because it goes down every day same hour. This is the log I have from the hour it happens
Jun 14 16:03:59 salome syslogd 1.4.1: restart.
How can I avoid this?
Thanks
Check your crontab using crontab -l .
Check your /etc/cron.daily directory also, if there is any script which restart the server.
And provide detailed logs from /var/log/messages for troubleshooting.
Hi, thanks for your help
I ran crontab -l from root in I got no crontab for root
also I have another user but there's no cron script to restart the server. do you know how to see enviroment logs? also I saw in my snmp server that the server is not going down at same time. snmp server logs has 30min to 1 hour of difference.
in /var/log/messages, the logs before shutdown and after power on
Jun 14 16:07:13 salome kernel: Bluetooth: HCI socket layer initialized
Jun 14 16:07:13 salome kernel: Bluetooth: L2CAP ver 2.8
Jun 14 16:07:14 salome kernel: Bluetooth: L2CAP socket layer initialized
Jun 14 16:07:14 salome kernel: Bluetooth: RFCOMM socket layer initialized
Jun 14 16:07:14 salome kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 14 16:07:14 salome kernel: Bluetooth: RFCOMM ver 1.8
Jun 14 16:07:14 salome kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Jun 15 16:04:06 salome syslogd 1.4.1: restart.
Jun 15 16:04:07 salome kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jun 15 16:04:07 salome kernel: Linux version 2.6.18-8.el5 (mockbuild@builder4.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Thu Mar 15 19:57:35 EDT 2007
Jun 15 16:04:07 salome kernel: BIOS-provided physical RAM map:
Jun 15 16:04:07 salome kernel: BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
Have you checked scripts in /etc/cron.daily ?
Also cross check again crontab files of all users in /var/spool/cron/.
Run a script at 16:00 which grabs output of ps -efc or ps aux into a file every minute. Check the file after server restart to find out if there is any process/script which is causing server restart.
Time difference between your server and SNMP logs may be due to different time settings on both servers. Run date command on both servers at the same time and check difference between them. If this is the cause, setup NTP for synchronized timings.
Have you checked scripts in /etc/cron.daily ?
Also cross check again crontab files of all users in /var/spool/cron/.
Run a script at 16:00 which grabs output of ps -efc or ps aux into a file every minute. Check the file after server restart to find out if there is any process/script which is causing server restart.
Time difference between your server and SNMP logs may be due to different time settings on both servers. Run date command on both servers at the same time and check difference between them. If this is the cause, setup NTP for synchronized timings.
Update us your findings.
thanks for your help, I started to read, and I find there is an option on BIOS where it is a power management setting. I disable an option called ACPI, and the problem is gone. The problem was that ACPI recognice when a device as monitor, keyboard, etc is not connected then it forces the system to make a power safe and shutdown
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.