Date: Fri, 20 Sep 2002 14:48:44 +0200 From: Nelis Lamprecht <nelis@brabys.co.za> To: freebsd-questions@freebsd.org Subject: Re: problems after restarting with bind and mysqld Message-ID: <5.1.0.14.2.20020920144416.01397268@192.96.48.11>
next in thread | raw e-mail | index | archive | help
Never mind the message below as posted previously, I have managed to source the problem to a system date change that I have no idea how it reverted back to July 5 ?? ----------------------------------------------------------------------------------------- Hi List I recently restarted my system ( reloaded rc.conf and startup scripts by going into single user mode and exiting ) and suddenly have run into 2 problems. I am running 4.6 Stable patched with the various security updates. Firstly, Bind 9.2.1 is giving me this error on startup: named[79181]: timer.c:407: unexpected error: named[79181]: isc_time_now() failed: unexpected error named[79181]: timer.c:407: unexpected error: named[79181]: isc_time_now() failed: unexpected error named[79181]: timer.c:407: unexpected error: named[79181]: isc_time_now() failed: unexpected error named[79181]: timer.c:284: unexpected error: named[79181]: isc_time_now() failed: unexpected error named[79181]: loading configuration: unexpected error named[79181]: exiting (due to fatal error) Secondly, Mysql version 3.23.47 is continuously exiting on signal 6. If I try to kill the process it just respawns a new one and if I try to stop it using the scripts in rc.d it does the same. Eventually I had to open up a new terminal and disable the startup scripts and do a shutdown to stop it. Manually starting it has the same results. I have checked the logs and it only shows: /kernel: pid 68869 (mysqld), uid 88: exited on signal 6 /kernel: pid 68874 (mysqld), uid 88: exited on signal 6 /kernel: pid 68879 (mysqld), uid 88: exited on signal 6 /kernel: pid 68884 (mysqld), uid 88: exited on signal 6 /kernel: pid 68889 (mysqld), uid 88: exited on signal 6 Any help/suggestions would be greatly appreciated as this as you can imagine is an urgent issue to be solved. I am busy in the process of back tracing my steps to see if any of the changes to the system may have caused these errors. Many thanks, Nelis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20020920144416.01397268>