similar to: (Centos 5.6) Server Time NTP Facility

Hello, I recently compiled Samba 4.0.6 (as an AD DC) and am running it on Ubuntu 12.04. I followed the instructions on the Samba wiki (https://wiki.samba.org/index.php/Configure_NTP) for how to configure ntp, however the domain clients are rejecting the DCs as being acceptable time sources. Below is my ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 10 server 0.pool.ntp.org iburst

Hi all, I have a problem with ntpd daemon in my CentOS7 vm. When I try to list peers, command fails: [root at c7tst ntpstats]# ntpq ntpq> pe ntpq: read: Connection refused ntpq> My actual ntp.conf: # For more information about this file, see the man pages # ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5). driftfile /var/lib/ntp/drift # Permit time

Hello, I have a question regarding signed NTP support for Samba4 on Ubuntu 12.04. I have followed most of the steps outlined here: https://wiki.samba.org/index.php/Configure_NTP These steps I did differently are: * I did not install from source because the latest Ubuntu package for ntp available on Ubuntu 12.04 includes ntp-signd support already * I did not install Samba4 to /usr/local/samba, so

Recently we have been having a lot of trouble with time synchronisation between our samba DC and the domain clients. We are not sure what started this issue since the Samba domain went live on October 11, 2016 and the issues only began to surface this past January but at some point the time on the clients and the DC diverged enough that we began to get strange network errors. Once we figured out

I just setup CENTOS 4.7 with latest patches on DELL server. I also configured NTP point to out time server. I found /var/log/messages file every 20 to 30 minutes will generate a error message : Mar 15 14:28:15 SER1 ntpd[25037]: sendto(172.29.21.16): Invalid argument Mar 15 14:45:22 SER1 ntpd[25037]: sendto(172.29.21.16): Invalid argument Mar 15 15:02:29 SER1 ntpd[25037]: sendto(172.29.21.16):

Hello Dear Friends, it is CentOS Release 6.2, ntpd is running but do not see bounded to the port udp:123 any guidelines would be very much appreciable. [root at jet mavi]# netstat -ntlp | grep ntpd <nothing in output> [root at jet mavi]# netstat -ntl | grep 123 <nothing in output> But the service is running - [root at jet mavi]# /etc/init.d/ntpd status ntpd (pid 15876) is

Hello everyone, If anyone is interested, I have created a HOWTO on running a Motorola GPS receiver connected to a CentOS 7 box via serial port (com1), with 1PPS over DCD. The trick here is that CentOS 7 uses systemd and setup was a bit different. Anyway, everything works. The result is a highly accurate NTP server, Stratum 1. Here is the documentation.

OK, So what you people say is : 1. Run "ntpdate" during startup only once 2. After that, keep time with ntpd Right ? Regards, spyros ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

Greets! Ok. I'm looking at a client that needs to keep their server time close as reasonably possible (within a minute) of the actual time of day. I've installed the RPM for NTP and I'm looking for tips on what the simplest setup should be, ie: What server(s) should I be using for sync? Should I just run it from a cron every 20 minutes or so? thx. Mike -------------- next part

Running CentOS 3.4, I enabled the ntpd service and noticed that it opens up a hole in the firewall for ntp from 127.127.1.0. I look in the ntpd initscript and see that it's reading in servers from /etc/ntp/step-tickers. However, that file is empty... /etc/ntp/ntpservers contains clock.redhat.com and clock2.redhat.com, but ntpservers isn't used *anywhere*. This looks like a bug, but

Alexander, First off, CentOS7 came with cronyd. Which was very annoying because when I tried to remove it, it had 2 prereqs: anaconda initial-setup Now, I don't know why the setup program kept these 2 around. I think CentOS7 needs a bit growing up. Anyway, I disabled chrony: systemctl disable time-sync systemctl stop time-sync Then I installed ntp. However, when I started it it seems that

I have a need to run a centos server CUT-off from any connected network. So the NTP server that is running on this very small network cannot connect to any other site to do what NTP does. however, I have devices on this small network that I wish to use the centos server as the time source and run ntpd. However - it seems like ntpd server does not like to run this way. There is a LONG delay

The following is from my logwatch email: --------------------- XNTPD Begin ------------------------ XNTPD Killed: 7 Time(s) XNTPD Started: 8 Time(s) Total interfaces 8 (non-local: 4) Total synchronizations 6 (hosts: 1) Errors getaddrinfo: "0.centos.pool.ntp.org" invalid host address, ignored: 2 time(s) getaddrinfo: "1.centos.pool.ntp.org" invalid host

We encountered a problem with respect to KVM virtual host restore and NTP. Specifically, our VM test host was shutdown by an extended power outage and when power returned all of the restored guests were immediately shutdown by ntp because the time differential between the restored systems and that of the ntpd sync servers exceeded the panic threshold. This is not an acceptable situation so in the

Hallo, what is the standard way to sync time under Centos 7. ntp or chrony. Thanks for a short hint. Ralf

I have 30 identical Lenovo desktop systems running CentOS 5.1. On one of those systems the clock is running slow (5+ minutes from yesterday to this morning and another minute since this morning) despite the fact that NTP is running on all of them and they all have the exact same /etc/ntp.conf file (I compared the MD5 sums of that file on all the systems). Here is the output of

Hi, I had the following problem today. Because of a misconfigured network switch one system suddenly didn't have any network. After a reboot (with the network still unavailable) NTPD refused to start. Most likely because the initial ntpdate failed to work. I find this troubling, because when the network was restored, NTPD could have resumed working (like I'd expect from a true

Hi List I have ntp running as a service on a PC, with the expectation that it would keep time in synch to my ntp server. However, while I can manually update the time using "ntpdate -u ...", I find that if I manually force the wrong time, the ntpd service does not automatically re-synch the system time with the ntp server: - Current time: [admin at lol ~]# date Wed Jan 27 10:54:21

This is for centos 7 that has chronyd 2.1.1 I am looking into how to use chronyd as my local ntp server. On my old servers with ntpd I had local access control lines like: restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap But in looking for documentation on chronyd I did not find anything on this at: https://chrony.tuxfamily.org/doc/2.1/manual.html In the actual /etc/chronyd.conf

Hi On 5.3 i have a situation where some boxes have been 3 or 4 seconds out and restarting ntpd has fixed the issue. What i dont understand is why the clocks did not drift to the correct time when the config seems correct in that restarting ntp did correct the time. Is there something 'special' i need to do in order for the drift to work? $ cat /etc/ntp.conf restrict default