similar to: Puppet apply hangs on Executing '/etc/init.d/ntp status'

I have a disk image file that was created using dd, makereiserfs dance, operating system files copied in directly with cp -ax (vi a temporary mount, and then dismounted). My domU configuration is as follows: -------------------------------- kernel = "/RAID/data/xen/bootsles10/vmlinuz-xen" ramdisk = "/RAID/data/xen/bootsles10/initrd-xen" memory = 2048 name =

Apologies if this is the wrong mailing list but no list in particular seems appropriate. I was disappointed to discover in the 9.2-RC's that ntpd was still 4.2.4p8. I notice that that same (legacy) ntpd version is in stable/10 and, presumably, likely to end up in the new 10.0 release; so I thought I should speak up in the hope that it is not yet too late for the current ntpd stable release

I have installed samba AD in centos 7, but I have an inconvenience to synchronize my clients with the NTP service, the status is in failed, it has to do with the socket. What permissions should be assigned? [root @ adsserver ~] # systemctl status ntpd ● ntpd.service - Servicio de hora de red Cargado: cargado (/usr/lib/systemd/system/ntpd.service; habilitado; proveedor preestablecido:

On Thu, 18 Oct 2018 15:24:40 +0200 Reindl Harald via samba <samba at lists.samba.org> wrote: > > > Am 18.10.18 um 15:19 schrieb Anderson Hoffmann do Carmo via samba: > > I use a script for backup Samba/AD and before running the backup I > > use the command '/etc/init.d/samba stop' > > After I migrated ubuntu from version 16 to version 18, this command

Hi CentOS users We are running CentOS 4.5 with NTP 4.2.0. # cat /etc/ntp.conf restrict default ignore restrict dns1.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict dns2.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict 127.0.0.1 server dns1.xxx.xxx server dns2.xxx.xxx fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift broadcastdelay 0.008 authenticate no The problem is

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

On Tue, February 7, 2017 13:06, James B. Byrne wrote: > In any case, we have resolved most of these issues. In dealing with > this I ran across > https://wiki.samba.org/index.php/Time_Synchronisation which contains > this instruction: > > Set up the ntpd.conf File on a DC > . . . > ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/ > > Now, on the FreeBSD host I

On Tue, 2017-02-07 at 13:06 -0500, James B. Byrne via samba wrote: > 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

Hai Viktor, I've seen some answers already and all are correct. What i would do different here, when running in a container.. apt-get remove --purge ntpd ;-) The hosts that are running AD DC containers these need all up to use the same time source. And you dont install ntpd, you still have the same time in you AD. NTPD is not obligated to setup AD DC's. Its obligated to have

Hi, I''m trying to run Xen 3.0 with a file-backed VBD on a opteron system. Here''s my Xen config file (xenconf): # -*- mode: python; -*- kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" memory = 1024 name = "Dom2" vif = [ '''' ] disk = [ ''file:/xendisk/vm3disk,sda1,w'' ] root = "/dev/sda1

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

In article <56A88188.6070808 at hogranch.com>, John R Pierce <pierce at hogranch.com> wrote: > On 1/27/2016 12:25 AM, Traiano Welcome wrote: > > I'm tempted to stick an "ntpdate -u ..." in the crontab to force > > time-synch, but I don't see why that's needed if ntpd service should > > already be fulfilling that purpose. > > > ntpd

Hello all, After reboot, one of my servers running CentOS5 no longer keeps its clock synced automatically. ntpd is running and I don't see anything weird being logged. If I kick off ntpd with 'ntpd -q', it will sync the clock. However, if I just rely on ntpd started with 'service ntpd start', syncing does not happen. I previously had: # Undisciplined Local Clock. This

Robert, If your NTP server will be on 7/24, I would uninstall chrony and install ntpd which is still included in CentOS 7. Configure as usual. For the differences between chrony and ntpd reference: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ Essentially, chrony is more for laptops with intermittant network connections, and ntpd is better suited to

- Default NETWORKING=no in /etc/sysconfig/network - Update to yes when configuring network through TUI or firstboot - After configuration in TUI, (re)start ntp daemons rhbz#675870 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 6 ++++++ scripts/network.py | 10 +++++++++- scripts/ovirt-config-networking | 1 + 3 files

Package: logcheck Version: 1.2.43a Severity: minor /etc/logcheck/ignore.d.server/ntp contains: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by [.0-9]+s$ However, this will not match negative corrections such as: System Events =-=-=-=-=-=-= Mar 5 01:44:55 billchase ntpd[6171]: adjusting local clock by -0.190112s Mar 5 01:55:20 billchase ntpd[6171]: adjusting local

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

On 1/27/2016 12:25 AM, Traiano Welcome wrote: > I'm tempted to stick an "ntpdate -u ..." in the crontab to force > time-synch, but I don't see why that's needed if ntpd service should > already be fulfilling that purpose. ntpd won't make drastic changes in the time, if its too far off. its designed to stabilize the clock by making small changes in speeding it

Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor Here's an excerpt from /etc/init.d/xend: *) N=/etc/init.d/xen-utils echo "Usage: $N {start|stop|restart|force-reload}" >&2 exit 1 ;; This will obviously display a wrong path when the script is called with unknown arguments. Regards, -- J?r?my -------------- next part

Hi all, After I recompiled a pv kernel for domU, I reboot the domU, but it hangs at: INIT: Entering runlevel: 2 Starting OpenBSD Secure Shell server: sshdNET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver . Starting NTP server: ntpd. The login prompt never commences. I thought it was the ntpd init script, but then I tested all the init scripts in