[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
tracing mysterious rebooting on centos 5
- To: silug-discuss@silug.org
- Subject: tracing mysterious rebooting on centos 5
- From: Brandon Joseph Adams <emidln@gmail.com>
- Date: Thu, 29 Oct 2009 01:29:23 -0500
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:mime-version:content-type:content-transfer-encoding :message-id; bh=6b92BLYHkiSIH9ryUO5Fj10xQwbDSih9uYa3ftrj6qc=; b=Nd9V9zfoLFC0KMqubf98F35HjQ7BQQBwc2YphLgmekf7WqM6AYKW2QyJa9106ItrSG s7egj8KbbaK9ImGknJQhPqkwdHi7FGTdvM0p1IUmqdmx4GrL9kozNfg22MV4aGO0rZz8 rakeF08nN8MF2xqmPTqz6ZCSawSpG/JnEyqi4=
- DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:message-id; b=GOVwh7sOtXHKSqOoOIKpxnsb0rUQal2H6tvO8Y2FOkaodnzk/ODSOuhHcbLCPxf7nm YOajVfyILHB/oI6ertpNniZSXi7ScrYLAn1S+ABhvmfM9iN5X5Vjj4Y+jO+C8HPp0aiZ VTzQe842Zk5UR4fNDBe7TGKjeTUp2J9+GyQBQ=
- Organization: Southern Illinois Linux Users Group
- Reply-To: silug-discuss@silug.org
- Sender: silug-discuss-owner@silug.org
- User-Agent: KMail/1.12.2 (Linux/2.6.31-14-generic; KDE/4.3.2; i686; ; )
Hi
So I'm back doing linux stuff after a few years and I ran into a rather
signficant hangup. The system I'm working on is a CentOS 5.4 machine
keeps rebooting at semi-random intervals whenever the iptables rules
change. I'm not currently sure if this is a fault in my iptables rules, a
hardware problem, or the result of a rogue legacy script finding something
amiss and rebooting. The solution I came up with is as follows (with auditd
enabled):
auditctl -a entry,always -S reboot
My only concern is that there might be another way to reboot the system
that isn't using reboot(2). init 6 seems to use reboot(2) and the userspace
reboot command seems to use it as well. Is there another way (outside of
magic sysrq) that the system might be rebooting via software?
Also, is there a better (maybe more obvious) way to be checking for this.
The logs in /var/log aren't very helpful and last & friends just tell me that
a reboot happened, not what caused it.
Thanks,
--
Brandon Joseph Adams
Email: emidln@gmail.com
Tel: +1 217-953-0257
GPG Key: 1024D/2F2EFCCF
Fingerprint = 2AEE AA3F B5C9 409D 2EE6 E38B CA06 8CDF 2F2E FCCF
This is a digitally signed message part.