  | |  | NTP problems | NTP problems 2004-01-15 - By Christopher McCrory
Back Hello...
On Thu, 2004-01-15 at 05:43, Shaw, Marco wrote:
> This is frustrating...
>
> NTP: I couldn 't get it working with 7.2 with various kernels, and various NTP packages, and now still can 't get it working with 2.1AS...
>
> ipchains allows all eth0 traffic through (trusted interface), yet I cannot get ntp to work.
>
> All I get is this, but absolutely *nothing* in tcpdump:
> # ntpdate -d IP_address_hidden
> 15 Jan 10:05:59 ntpdate[22868]: ntpdate 4.1.2@(protected) Tue Dec 9 11:52:07 EST 2003
> (1)
> 15 Jan 10:06:59 ntpdate[22868]: poll(): nfound = 0, error: Success
> 15 Jan 10:07:59 ntpdate[22868]: poll(): nfound = 0, error: Success
> 15 Jan 10:08:59 ntpdate[22868]: poll(): nfound = 0, error: Success
> 15 Jan 10:09:59 ntpdate[22868]: poll(): nfound = 0, error: Success
> 15 Jan 10:10:59 ntpdate[22868]: poll(): nfound = 0, error: Success
>
> Should ntpdate work if ntp is not configured (ntp.conf set to default).
>
If ntpd is running at all, ntpdate will not work.
I posted this on another list, so I 'll copy-n-paste:
cat /etc/ntp/step-tickers
clock.redhat.com
cat /etc/ntp.conf
restrict default ignore
restrict 127.0.0.1
# your net here
restrict 10.20.0.0 mask 255.255.0.0 notrust nomodify notrap
restrict 66.187.233.4 mask 255.255.255.255 nomodify notrap noquery
server clock.redhat.com
server 127.127.1.0
fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
authenticate no
You can check it with:
/usr/sbin/ntpq
ntpq > peers
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) LOCAL(0) 10 l 54 64 177 0.000 0.000 0.008
*clock.redhat.co .CDMA. 1 u 54 64 177 74.713 -14.724 5.309
ntpq >
Then, being a good netizen) you can point all your other devices to this
one machine.
Config dhcpd.conf to dish this out to local machines:
subnet 10.20.10.0 netmask 255.255.255.0 {
# --- default gateway
option routers 10.20.10.1;
option subnet-mask 255.255.255.0;
option domain-name "example.com ";
option domain-name-servers 10.20.10.2,10.20.30.3;
option time-offset -8; # Pacific Standard Time
option ntp-servers 10.20.10.2;
option netbios-name-servers 10.20.10.9;
> This is on a SMP Dell PE 1650 with a 3Di controller. I was able to get ntp working on the same system, except it did not have the 3Di controller.
>
> How can I troubleshoot? Recompile some NTP packages with '-Wall -ggdb ' and start stepping through lines of NTP code? I 'm at a loss... I tried using strace, yet the dump on a working system appeared relatively the same as a non-working one.
>
> Marco
>
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
>
http://www.redhat.com/mailman/listinfo/taroon-list
--
Christopher McCrory
"The guy that keeps the servers running "
chrismcc@(protected)
http://www.pricegrabber.com
Let 's face it, there 's no Hollow Earth, no robots, and
no 'mute rays. ' And even if there were, waxed paper is
no defense. I tried it. Only tinfoil works.
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
|
|
 |