On 2010-07-06 21:40, m...@grounded.net wrote: > On Tue, 6 Jul 2010 23:47:48 +0000, Matthew Kitchin (Public) wrote: >> Can you paste output from crontab -l and the file /etc/ntpd.conf > Sure, nothing in crontab; > > # crontab -l > no crontab for root > > And there is no ntpd.conf in /etc/ > > I have a cron job sitting in /etc/cron.daily/ which I call timeset > > /etc/init.d/ntpd stop > ntpdate 2.pool.ntp.org > /etc/init.d/ntpd start Take that out right away - it is actively harmful.
Use the ntp.conf configuration created for you by the setup script - someone send him a copy - make sure that you have given it ntp servers that work (that includes checking that they are reachable from your network - your firewall may need to be configured). A quick google search will tell you how to check whether or not it is working (and/or others here will help). Make sure that your system is configured to always run ntpd. Running ntpdate can set your clock _back_, which seriously messes up sipXecs - it assumes that time only ever goes forward, which is also true if the the ntp daemon is controlling your clock. > In /etc/sysconfig/clock, I have; > > ZONE="America/Chicago" > UTC=true > > And of course, I set the hardware clock using the system time; > hwclock --systohc > > And finally, have the GUI settings as well. > > What I'm finding interesting since we've been talking about this is how my > hardware clock seems to drift. > I've moved the drives to another server to see what will happen. That won't change anything - nearly all computers have really really bad clocks - running ntpd will fix it, and will very likely fix your problem. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
