similar to: new errors in /var/log/messages since update to 5.9

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):

Hi, looking at the messages i see errors with ntp everytime i reboot my server: shiva2# tail /var/log/messages Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC 2006 (1) Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0

My server is supposed to be using ntp, with nothing changed from the defaults set up by CentOS5. However, daily I see log entries like Total synchronizations 2 (hosts: 2) **Unmatched Entries** sendto(193.6.222.20) (fd=21): Invalid argument: 1 time(s) sendto(141.89.226.2) (fd=21): Invalid argument: 1 time(s) Does this mean that ntp is failing? I assume so, and if so, how do I change

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled,

On Tue, May 28, 2019 at 11:44:35AM +1000, Jobst Schmalenbach wrote: > On Mon, May 27, 2019 at 06:32:19AM +0200, Ralf Prengel (ralf.prengel at rprengel.de) wrote: > > > > Hallo, > > > > what is the standard way to sync time under Centos 7. > > ntp or chrony. > > YMMV. > > I have used NTP for many, many years so I am familiar with it and also have ALL

I've just installed LibreOffice 4.0.0.3 on my Centos 5.9 system. the previous version (3.4.x) was working fine. But 4.0.0.3 won't start up. When run from a terminal it prints: no suitable windowing system found, exiting. Is this yet another case of apps moving on beyond compatibility with the older components in C5? Or any hints for making it work? Thanks! -- ---- Fred Smith --

I just finished setting this computer up again from scratch since the hard drive died yesterday, and when reinstalling the software that was there before, I discovered that the following packages are not available: beesu caja-beesu caja-extensions-common caja-image-converter caja-open-terminal caja-sendto I'm pretty sure that these came from epel before, but they're now missing? --

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

Dear All, I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address Server 2 : 192.168.13.179 IP Address Floating : 192.168.13.83 IP Address (Assumed by currently active server) I want all snmp packets going out through the active server to be stamped with floating IP So i have added a iptables rules as "iptables -t nat -A POSTROUTING -p udp -s

I have a minimal installation of CentOS, and I wanted to then install X Windows and the GNOME desktop. I then tried the following, which failed on a dependency: $ yum -y groupinstall "X Window System" "GNOME Desktop Environment" --> Running transaction check ---> Package nautilus-sendto.i386 0:0.7-5.fc6 set to be updated --> Processing Dependency:

Hi, I have got problems with the ntp daemon. It is enabled in systemd but is not started on boot. # systemctl status ntpd ? ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) Starting manually works # systemctl start ntpd # systemctl status ntpd ? ntpd.service - Network Time Service

On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > >> Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> >> > On

On 5/23/2015 11:22 PM, Luigi Rosa wrote: > Kirk Bocek wrote on 24/05/2015 04:37: >> So I've built my first CentOS 7 host and am learning all the new ways >> of doing >> things. I setup and enabled ntpd but after a reboot I get: > > In CentOS 7 is bettere to use chrony, here's an howto > > http://linoxide.com/linux-command/chrony-time-sync/ > So

I have a KVM setup. Host is 6.3. I have a bridged client running 5.9 Since upgrading to 5.9 I noticed that ntpd is being restarted every 12 hours. Jan 20 08:00:25 mercury ntpd[16103]: ntpd exiting on signal 15 Jan 20 20:00:26 mercury ntpd[27462]: ntpd exiting on signal 15 Jan 21 08:00:27 mercury ntpd[11343]: ntpd exiting on signal 15 Jan 21 20:00:28 mercury ntpd[25148]: ntpd exiting on signal

hi all! back in Aug several of you assisted me in solving a problem where one of my drives had dropped out of (or been kicked out of) the raid1 array. something vaguely similar appears to have happened just a few mins ago, upon rebooting after a small update. I received four emails like this, one for /dev/md0, one for /dev/md1, one for /dev/md125 and one for /dev/md126: Subject: DegradedArray

A shell script is deployed to synchronize time, the script is invoked hourly by crontab, and its content is as follows: #!/bin/bash service ntpd stop ntpdate 192.168.0.191 #it's a valid ntpd server in LAN service ntpd start chkconfig ntpd on Inspected the Linux log(Centos6.4 /var/log/messages), found the following fragment: Jan 7 14:00:01 host1 ntpd[32101]: ntpd exiting on signal 15 Jan 7

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

hi folks. i'm experimenting with iaxmodem + hylafax using DID to determine where to send the fax to it's final destination. however i have difficulties passing the DID information from iaxmodem to hylafax. in extensions.conf: exten => _XXXX,1,Dial(IAX2/iaxmodem0/${EXTEN}|20|r) exten => _XXXX,n,Dial(IAX2/iaxmodem1/${EXTEN}|20|r) exten => _XXXX,n,Busy exten => _XXXX,n,Hangup

Tengo instalado samba AD en centos 7, pero tengo un inconveniente para sincronizar mis clientes con el servicio NTP, el estado esta en failed, tiene que ver con el socket. Que permisos se le debe de asignar? [root @ adsserver ~] # systemctl status ntpd ● ntpd.service - Servicio de hora de red Cargado: cargado (/usr/lib/systemd/system/ntpd.service; habilitado; proveedor preestablecido:

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