I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE. rcntp status Checking for network time protocol daemon (NTPD): running when I run ntpdate from an of the unix boxes I get this back ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found /etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org ## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer ## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized ## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap driftfile /var/lib/ntp/drift/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 29/07/06 15:00, Elijah Savage wrote:
I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE.
rcntp status Checking for network time protocol daemon (NTPD): running
when I run ntpdate from an of the unix boxes I get this back
ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found
/etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org
## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer
## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap
^^^ Does it work without the authentication requirement? If not, then ensure the ntp port is open on the internal interface. If it does work, then have another look at your client config files (ie. do they include the autokey option in the server definition, etc?)
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Jul 29, 2006, at 5:18 PM, Darryl Gregorash wrote:
On 29/07/06 15:00, Elijah Savage wrote:
I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE.
rcntp status Checking for network time protocol daemon (NTPD): running
when I run ntpdate from an of the unix boxes I get this back
ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found
/etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org
## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer
## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap
^^^ Does it work without the authentication requirement? If not, then ensure the ntp port is open on the internal interface. If it does work, then have another look at your client config files (ie. do they include the autokey option in the server definition, etc?)
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
I took the restrictions out and rcntp restart Shutting down network time protocol daemon (NTPD) done Try to get initial date and time via NTP from 0.north- america.pool.ntdoneg 1.north-america.pool.ntp.org Starting network time protocol daemon (NTPD) done Then tried a client and no go. And the firewall is not running on the suse box and the two machines I am testing with both sit off of a cisco 3550 swtich right next to each other on the same network 192.168.11.10 and 192.168.11.12 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 29/07/06 15:26, Elijah Savage wrote:
On Jul 29, 2006, at 5:18 PM, Darryl Gregorash wrote:
On 29/07/06 15:00, Elijah Savage wrote:
I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE.
rcntp status Checking for network time protocol daemon (NTPD): running
when I run ntpdate from an of the unix boxes I get this back
ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found
/etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org
## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer
## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap
^^^ Does it work without the authentication requirement? If not, then ensure the ntp port is open on the internal interface. If it does work, then have another look at your client config files (ie. do they include the autokey option in the server definition, etc?)
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
I took the restrictions out and
rcntp restart Shutting down network time protocol daemon (NTPD) done Try to get initial date and time via NTP from 0.north- america.pool.ntdoneg 1.north-america.pool.ntp.org Starting network time protocol daemon (NTPD) done
Then tried a client and no go.
And the firewall is not running on the suse box and the two machines I am testing with both sit off of a cisco 3550 swtich right next to each other on the same network 192.168.11.10 and 192.168.11.12
On a client system, what are the outputs of the "pe" and "as" commands in ntpq? Also, have you verified that the server is receiving ntp packets from the clients? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
From: "Darryl Gregorash" <raven@accesscomm.ca>
On a client system, what are the outputs of the "pe" and "as" commands in ntpq? Also, have you verified that the server is receiving ntp packets from the clients?
And he should note that ntp can take ten minutes or so to synchronize and allow itself to be used as a reference. That is why the ntpq reports are so important. {^_-} Joanne -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Jul 29, 2006, at 7:01 PM, Darryl Gregorash wrote:
On 29/07/06 15:26, Elijah Savage wrote:
On Jul 29, 2006, at 5:18 PM, Darryl Gregorash wrote:
On 29/07/06 15:00, Elijah Savage wrote:
I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE.
rcntp status Checking for network time protocol daemon (NTPD): running
when I run ntpdate from an of the unix boxes I get this back
ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found
/etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org
## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer
## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap
^^^ Does it work without the authentication requirement? If not, then ensure the ntp port is open on the internal interface. If it does work, then have another look at your client config files (ie. do they include the autokey option in the server definition, etc?)
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
I took the restrictions out and
rcntp restart Shutting down network time protocol daemon (NTPD) done Try to get initial date and time via NTP from 0.north- america.pool.ntdoneg 1.north-america.pool.ntp.org Starting network time protocol daemon (NTPD) done
Then tried a client and no go.
And the firewall is not running on the suse box and the two machines I am testing with both sit off of a cisco 3550 swtich right next to each other on the same network 192.168.11.10 and 192.168.11.12
On a client system, what are the outputs of the "pe" and "as" commands in ntpq? Also, have you verified that the server is receiving ntp packets from the clients?
I have done this many of times with FreeBSD then I run into this weirdness. I reinstalled from yast via cmdline and then rebooted the machine for good measure and other machines can sync off of it now. Thank you to everyone that replied I do appreciate it. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Darryl Gregorash -
Elijah Savage -
jdow