problems with watchdog on server hardware
Hi to all,
I am running some older Fujitsu Primergy Servers (RX300 S2 and RX100 S3).
All these servers have an activated hardware watchdog (IPMI watchdog) and
the Debian package watchdog is installed. Sometimes these servers just
reboot without any reason. The times of these reboots differ and there is
no prediction when they reboot. For now I found out that a reboot can be
triggered when large files ( 4 GB ) are copied to a server. The server
reboots reliably in the middle of the transfer. When I turn of the watchdog
the transfer finishes successfully and the server does not reboot
spontaneously...
Is someone out there with similar experiences?
Below is one of my watchdog.conf files:
#s/
#s/ping = 127.0.0.1
#interface = eth0
#file = /var/log/messages
#change = 1407
# Uncomment to enable test. Setting one of these values to '0' disables it.
# These values will hopefully never reboot your machine during normal use
# (if your machine is really hung, the loadavg will go much higher than 25)
#max-load-1 = 24
#max-load-5 = 18
#max-load-15 = 12
# Note that this is the number of pages!
# To get the real size, check how large the pagesize is on your machine.
#min-memory = 1
#repair-binary = /usr/sbin/repair
#test-binary =
#test-timeout =
#watchdog-device = /dev/watchdog
watchdog-device = /dev/watchdog
# Defaults compiled into the binary
#temperature-device =
#max-temperature = 120
# Defaults compiled into the binary
#admin = root
admin = alarm
#interval = 10
interval = 10
#logtick = 1
# This greatly decreases the chance that watchdog won't be scheduled before
# your machine is really loaded
realtime = yes
priority = 1
# Check if syslogd is still running by enabling the following line
#pidfile = /var/run/syslogd.pid
#pidfile = /var/run/sshd.pid
Thx for any reply on this,
Michael
Reply to: