strang error starting named

T

tincboy

Verified User
Joined
Aug 14, 2009
Messages
126
My named fails to start and /var/log/messages shows these errors:

Jul 16 06:27:41 named[3014]: starting BIND 9.3.4-P1 -u named
Jul 16 06:27:41 named[3014]: found 2 CPUs, using 2 worker threads
Jul 16 06:27:41 named[3014]: timer.c:695: fatal error:
Jul 16 06:27:41 named[3014]: RUNTIME_CHECK(isc_time_now((&now)) == 0) failed
Jul 16 06:27:41 named[3014]: exiting (due to fatal error in library)

Any help fixing named will be much appreciated.
 
Did you try to google or ask your question in a specialized forum or mailing-lists? That seems to be an error or bug of bind, and has little to do with directadmin, since directadmin does not either compile or make it.
 
zEitEr said:
Did you try to google or ask your question in a specialized forum or mailing-lists? That seems to be an error or bug of bind, and has little to do with directadmin, since directadmin does not either compile or make it.
Click to expand...

Yes, I've tried to google it and there was nothing useful,
Finally I got it fixed,
The issue was because time of my server went back to 1911, I've change it to 2011 and it alright now.

thanks
 
..or the VM just lost track of the time. i've seen this happen a few times. recently, actually. where the sysadmin would set the time to current time using ntpdate, and within 10 minutes had flown forward to jan 2012. apparently it's some kind of bug in older kernels running on top of VM's that occasionally don't count cpu ticks correctly. this not only causes the system to show stupid CPU time used for processes (http://serverfault.com/questions/304655/top-w-ps-showing-wrong-cpu-times), but can also cause the system time to fly forward (or back, in a much worse case scenario, it seems!).
 
You must log in or register to reply here.
Back
Top