I have a Server with Squid, 7.0-RELEASE-p4 FreeBSD, squid-3.0.11, that
has been running fine for the last six months, at least.
It is shutdown every night at 7 PM via cron.
Now suddenly the machine is rebooting instead, and I've made no changes
whatsoever. I'm wondering if this is a symptom of a coming hardware
failure or if I can do something to get the normal behaviour back.
I did have a similar problem when I first put the machine into
production, then it was clear from /var/log/messages that squid did not
have enough time to shutdown and I solved it by changeing the parameter
rcshutdown_timeout="90" i rc.conf.
Here's a piece of /var/log/messages
----------- snip ------------
Jan 1 19:05:00 server01 shutdown: power-down by root:
Jan 1 19:05:33 server01 squid[823]: Squid Parent: child process 826
exited with status 0
Jan 1 19:05:34 server01 named[718]: stopping command channel on
127.0.0.1#953
Jan 1 19:05:34 server01 named[718]: stopping command channel on ::1#953
Jan 1 19:05:34 server01 named[718]: exiting
Jan 1 19:05:36 server01 syslogd: exiting on signal 15
Jan 1 19:07:29 server01 syslogd: kernel boot file is /boot/kernel/kernel
Jan 1 19:07:29 server01 kernel: Copyright (c) 1992-2008 The FreeBSD
Project.
Jan 1 19:07:29 server01 kernel: Copyright (c) 1979, 1980, 1983, 1986,
1988, 1
989, 1991, 1992, 1993, 1994
Jan 1 19:07:29 server01 kernel: The Regents of the University of
California.
All rights reserved.
----------- snip ------------
Thanks
/Leslie
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"