On Sun, Mar 20, 2005 at 06:38:49PM +0100, Michael Meskes wrote:
> Sorry, I don't understand your bug report.
ok.
explanations follow

> On Sat, Mar 19, 2005 at 07:24:20PM +0100, Artur Górniak wrote:
> >I am getting errors 101 and 2 resulting in system reboot when trying to
> 101 is "network unreachable", 2 means "no such file". Neither one should
> be a possible return value for a memory check for instance.
I had lines:
file                   = /var/log/syslog
ping                   = 192.168.0.1
interface              = eth0
interface              = eth1
min-memory             = 1
pidfile                        = /var/run/syslogd.pid

I had 101/2 errors in mails from watchdog so lines with eth and file
are forcing restart of the system (was trying few setups).

the problem is:
ping and eth1 is my local network working all the time on static
settings.  eth0 is getting address from dhcp but I was trying
configuration with eth0 line commented.
After first restart watchdog was rebooting my computer just after
start of the deamon.

> > seems that watchdog is restarting system if any event occurs
> > in 10 sec interval.
> Do you mean it gets an event every 10 seconds? Or do you mean it just gets 
> any event?

in my setup watchdog is checking all resources every 10sec (default
time).  but the problem is that it is rebooting computer if there is
a single problem with pid/file/ping and so on.

> > The problem is: upgrading system with watchdog running (restart of
> > deamons could/will trigger watchdog)
> This seems to imply that restarting a server process triggers watchdog
> and thus reboots the system. Is this the case?

this is also the case.

for now I can only say that it should not restart computer in a case of
single failure (upgrade of deamons) and that it should be started later
in boot process.

I do not know why it was rebooting my computer with file/interface
or ping configured.

my mainboard is dual pentium II but I do not think that it should be
a problem.

I started up watchdog on the other P IV 3.0 GHz machine and it was
working without a problem for at least few hours. I will see tomorrow if
it is forcing restart on that machine as it has similar configuration
to my server with pidfile/ping/interface/file line uncommented and
configured.

Artur Górniak



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to