Does anyone know what needs to be done to make SLES 11 SP3 act as a time server ?
I see the ntp client packages and I have them installed and configured, but I want to make other servers come to this server to get their time. Then have this server sync with the us.pool.ntp.org time server pools.
Yes but there is no ntp server daemon, just a client. So the server isn’t listening for ntp requests in order to respond. It will only time sync with an external source.
I’m going to try a compile the ntp-server from ntp.org and see if that will work. I’m surprised that SUSE doesn’t have a ntp-server daemon.
Like Malcolm already answered, the only “ntp client package” is the yast extension - the “ntp daemon” package contains the code to run both as server and as a client (the NTP daemon is both).
[QUOTE=cisaksen;22634]Yes but there is no ntp server daemon, just a client. So the server isn’t listening for ntp requests in order to respond. It will only time sync with an external source.
I’m going to try a compile the ntp-server from ntp.org and see if that will work. I’m surprised that SUSE doesn’t have a ntp-server daemon.[/QUOTE]
since the ntp daemon is just that - an NTP server, the one from ntp.org, I’d like to know how you conclude “the server isn’t listening for ntp requests”, maybe there’s some setup problem?
since the ntp daemon is just that - an NTP server, the one from ntp.org, I’d like to know how you conclude “the server isn’t listening for ntp requests”, maybe there’s some setup problem?
With regards,
Jens[/QUOTE]
Hi
Correct, all you need to do is configure ntp.conf to allow connections from the local network, sync to an external time source, open the firewall port etc.
It’s not listening on port 123. And from what I’ve read so far, it looks like it is an ntp server but it does so using the rpc service. I’ve tried the test button on to another suse system that have ntp setup to listen to another time server and they respond to the test successfully but if you go the system it is not listening on port 123. Also the system that responded to the test successfully also does not appear on the local ntp server search.
Hi
So if you check via the system running the ntp daemon, maybe if post your current ntp.conf (maybe change your ip addresses to xxx) may help? Port open in the firewall? You have restarted the ntp service?
*nde04.hh.nde.ag 195.50.171.101 3 u 1 16 377 0.132 -0.002 0.003
+nde32.hh.nde.ag 217.144.138.234 3 u 1 16 377 0.089 76.670 0.106
LOCAL(0) .LOCL. 10 l 47 64 377 0.000 0.000 0.001
Checking for network time protocol daemon (NTPD): running
nde101:~ # rpm -qi ntp
Name : ntp Relocations: (not relocatable)
Version : 4.2.4p8 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Release : 1.22.1 Build Date: Wed May 8 23:55:38 2013
Install Date: Thu May 8 14:59:06 2014 Build Host: gubaidulina
Group : Productivity/Networking/Other Source RPM: ntp-4.2.4p8-1.22.1.src.rpm
Size : 1635382 License: BSD 3-Clause
Signature : RSA/8, Wed May 8 23:55:45 2013, Key ID e3a5c360307e3d54
Packager : http://bugs.opensuse.org
URL : http://www.ntp.org/
Summary : Network Time Protocol daemon (version 4)
Description :
The Network Time Protocol (NTP) is used to synchronize the time of a
computer client or server to another server or reference time source,
such as a radio, satellite receiver, or modem.[/CODE]
And this even is one of our peer machines, a “client”, so to say. But our central NTP servers don’t look different and I may point any client at this server at any time, without problems…