On Tue, 24 Feb 2004 [EMAIL PROTECTED] wrote:
> Thanks for the replies. I was able to enable my logs and run ntpdate with
> a server but I am still getting the same problems. I also opened port 123
> on udp and tcp but that had no effect, and I really don't understand why
> you need to open a port in order to just query the correct time. Here is
> the feedback i get from the logs:
because you're firewall is doing what you told it ... disallow all ports
that you didnt explicitly allow ... ntp ports are typically turned off
by default
> Feb 24 14:17:19 bilbo ntpd[16556]: ntpd [EMAIL PROTECTED]:4.1.2a-2 Tue Nov 11
> 11:33:28 UTC 2003 (2)
> Feb 24 14:17:19 bilbo ntpd[16556]: signal_no_reset: signal 13 had flags
> 4000000 Feb 24 14:17:19 bilbo ntpd[16556]: precision = 6 usec
> Feb 24 14:17:19 bilbo ntpd[16556]: kernel time discipline status 0040
> Feb 24 14:17:37 bilbo ntpdate[16560]: no server suitable for
> synchronization found
>
> Any more suggestions?
> -ryan
there's lots of debugging commands ... to try out
ntptrace -dv someplace-ntp.server.com
ntpdc -c peers
rest of the debugging
http://linux-consulting.com/NTP/NTP.Commands.txt
and if your clock is out of sync by more than 1000sec ...
it may or may not tell you and wont sync ... but you
can get around that too before ntp'ing
c ya
alvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
