From owner-freebsd-questions Fri Sep 20 4: 2:36 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 549F837B401 for ; Fri, 20 Sep 2002 04:02:35 -0700 (PDT) Received: from brabys.co.za (postoffice.brabys.co.za [192.96.48.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC26643E81 for ; Fri, 20 Sep 2002 04:02:30 -0700 (PDT) (envelope-from nelis@brabys.co.za) Received: from nelis.brabys.co.za (proxy-inner.brabys.co.za [192.96.48.11]) by brabys.co.za (8.12.0/8.12.0) with ESMTP id g8KB1XwS022120 for ; Fri, 20 Sep 2002 13:01:33 +0200 Message-Id: <5.1.0.14.2.20020920124049.0133a830@192.96.48.11> X-Sender: nelis@192.96.48.11 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 20 Sep 2002 13:00:42 +0200 To: freebsd-questions@freebsd.org From: Nelis Lamprecht Subject: problems after restarting with bind and mysqld Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Found to be clean Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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