Running "Red Hat Linux release 9".I want to setup ntpd service to synchronize with our internal ntp server./etc/ntp.conf:
Code:
# Prohibit general access to this service.
restrict default ignore
[code]....
I'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly
This is the ntp.conf file:
Code:
[root@CentOS5 ~]# cat /etc/ntp.conf
logfile /var/log/ntp.log
driftfile /var/lib/ntp/drift
server 0.centos.pool.ntp.org
This is the output of command:
Code:
[root@CentOS5 ~]# ntpd -dqg
ntpd 4.2.2p1@1.1570-o Sat Dec 19 00:58:16 UTC 2009 (1)
addto_syslog: precision = 1.000 usec
create_sockets(123)
addto_syslog: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 .....
clock_filter: n 6 off 42905.489022 del 0.390840 dsp 0.000132 jit 4.733917, age 12
16 addto_syslog: no reply; clock not set
Also attached is the trace file, from the trace file, everything seems ok, timestamps is sent and received:
I'm trying to sync my clock. I think I would like to do this by the "ntpd" daemon running. I think it should start up on boot, but it doesn't.
I have the following in my /var/log/syslog:
Jul 18 23:44:14 neo ntpd[1780]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:45:13 UTC 2010 (1)
Jul 18 23:44:14 neo ntpd[1781]: proto: precision = 0.634 usec
Jul 18 23:44:14 neo ntpd[1781]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
Jul 18 23:44:14 neo ntpdate[1194]: step time server 72.26.125.125 offset -0.505108 sec
Other posts say if ntpd and ntpdate run too close together, they cause one to think the other is locking a resource. It works to type "ntpdate pool.ntp.org" to manually update the clock. My Debian version is squeeze (6.0.2)
It works to start the ntpd daemon manually:
... sudo /etc/init.d/ntp start
... Starting NTP server: ntpd.
I'm having a problem with the time on one of my servers jumping forward into the future. We run serveral CentOS 5.4 servers running Xen, some up to date and some a little older. The one in question is running 2.6.18-164.el5xen, with xen-libs-3.0.3-94.el5_4.2 and xen-3.0.3-94.el5_4.2. On this server are several Xen virtual machines, also running CentOS 5.4 with kernel 2.6.18-164.el5xen. One in particular has problems with the clock keeping proper time.
We use NTP (ntpd) to sync time to a central server in the company. Our NTP set-up works fine, and we have problems on only a couple of servers out of many. The problem I see is that one one particular Xen virtual machine, the clock will suddenly jump forward into the future, usually by several minutes but once by more than an hour. This has obvious implications for software running on the machine. Software such as Oracle grid control agent will restart itself under the (incorrect) assumption that it has been hung for several minutes with no activity. Oracle database will cope gracefully, but applications that refer to the clock will be confused.
We detect these time jumps because we have Nagios checking the clock on each host against the centralised time server (Nagios's check_ntp plugin). Nagios will suddenly report a clock offset that is miles into the future. Following the time jump, ntpd on the host in question will re-sync the time. Ntpd keeps the time steady, ticking just a few milliseconds per second until real time catches up with the server. i.e. Nagios will report the time as being 10 minutes ahead, then a minute later the host will be 9 minutes ahead, and then a further minute later the host will be 8 minutes ahead of real time. The clock on the host stays running very slow until it eventually is correct.
[Code]...
NTPD on Fedora 14.
View 2 Replies View RelatedI am facing issue in ntp, it is getting killed frequently. see below error; # /etc/init.d/ntpd status ntpd dead but pid file exists After starting service it is works fine but again after sometimes it get in dead postition.
View 5 Replies View Related[root@espeed log]# /etc/init.d/ntpd start
Starting ntpd: ntpd: error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
[root@espeed log]# ldd /usr/sbin/ntpd
linux-gate.so.1 => (0x00786000)
libm.so.6 => /lib/libm.so.6 (0x0059d000)
[code]....
Before my windows clock was at local time + 2h. Now my Win clock is ok but my F11 clock is at local time +2h. What happened?!
View 9 Replies View RelatedTry as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
View 6 Replies View RelatedWhen I travel, I would like to tell my laptop that I, as a user, am in a different time zone that what the OS may think is local. And I would like the clock on my desktop (default Gnome bar date/time display) to show the local time.
Instead, I currently have to use sudo and change the system time... (click on the clock, choose time settings, set system time -- there are no other choices given). The applet thing allows me to add other locations, but they only show up if I click on the icon, as extra times below the main one.
Am I missing something? Using the wrong app?
I was wondering what smartphones do people have and what applications are they using with them.
Is there a calendar/address book application which synchronizes with the phones?
I've used a Palm Pilot with J-Pilot before. Would it work with an iPhone or Blackberry or Nokia N900?
I was wondering if any of you knows any feed reader for gnome that is compatible enough with Google Reader that it synchronizes with it ? I am currently trying Liferea. Does it sync with Greader ?
View 2 Replies View RelatedI'm using a very simple conky script to diplay the date and time on my desktop. I've noticed that he conky clock is a few seconds early compared to the time displayed in the right hand side of the top panel (Natty). I guess both displays are based on the same "internal" time, so I'm left wondering how this could happen, and how to sync back the clocks.
It seems that Conky is in sync with the system date, while the panel clock is 2 seconds late (on my system). Checked with while true; do date; sleep 0.1; done
Just curious as to if it is possible to have the clock in the center of the task bar centered clock in Ubuntu 11.04?
View 1 Replies View RelatedDoes anyone know of an interface to a quartz clock that can be used for a TOD clock?? I want to interface it to an Arduino board. Can be GPIO or USB.
View 1 Replies View RelatedI had cloned a centos 5.6 installation from virtualbox virtual machine to physical box. Everything work fine. However, the time showing in os using date command differs from bios time by roughly 4 hours. I am running ntp services which sync the time with another centos server on the network. It appears that some services are using virtual clock and some use physical clock. How do I get rid of virtual clock and only use physical clock?
View 1 Replies View RelatedI had Windows XP working. I then put in a new hard disk and installed Redhat 5 on it. rom then i could only boot into Redhat. Further, everyting is very slow. Anothe rproblem is that Redhat does not see my netwrok so I cannot get onto the Internet. I need to have the choice of booting into XP or Redhat.
View 2 Replies View RelatedI am rebuilding / updating my internal server. It is strange to me that 11.0 will not install on this ASUS M3A78 MB but 11.2 will go through. I am setting up the ntp server and run into new things, ntpdate is not used anymore so you have this long string : sntp -P no -r pool.ntp.org which does the same thing or a couple of other calls that may work. It seems that pool.ntp.org will not work however so I switched to another time server.
pool.ntp.org does work on 11.0 however, it still uses ntpdate atm.
I can use ntpdate to my server from other clients and get the time but I can't use Yast to set it up, it hangs (or maybe it will eventually time out) when you test the server in the gui tool. rcntp ntptimeset comes back with no server reached on the ntp server machine so I am not confident that it will auto update itself, which I think is an issue, the server will not respond to client queries after a day or two.
I have a Windows 2003 server that runs a Win32 time server which synchronizes with off site time sources. I have a CentOS 5.4 server which I just configured and installed NTP on. For some reason, I keep getting time discrepancies even after the server is (apparently) synching with my local NTP server on the Windows box.
Hwclock is set to UTC true/etc/localtime is properly symlinked to appropriate /usr/share/zoneinfo fileNTPD is setup as a service which loads on startupNTP.conf is configured to only retrieve from my local Windows 2003 time serverntpq -p seems to verify that the system is indeed synching up properlyThe problem is, whenever I run the 'date' command it is displaying my system time in (presumably) UTC. That is, even though my the CentOS box appears to be synching up to the local time, it's not translating it into my proper time zone. Consequently, the date is always at -6 hours from the actual local time. It was my understanding that the hwclock is fine to remain at UTC as ntpd should be synching with my local Windows 2003 time server periodically and updating it, and the system time should be getting translated to my localtime.
what I do, after rebooting the box the hwclock and system clock display the improper time.Maybe I just have a fundamental misunderstanding of how this is supposed to operate.Update: I'm not sure why, but after I commented out the other servers and added a fudge declaration for my internal server and rebooted, everything is working as it should and the time is correct.I'm still not really sure if it was adding the "fudge <hostname> stratum 2" declaration that corrected things, or commenting out the additional hosts, so I'll leave this open if anyone cares to comment or contribute.
i'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly.this is the ntp.conf file:
[root@CentOS5 ~]# cat /etc/ntp.conf
logfile /var/log/ntp.log
driftfile /var/lib/ntp/drift
server 0.centos.pool.ntp.org
this is the output of command:
[root@CentOS5 ~]# ntpd -dqg
ntpd 4.2.2p1@1.1570-o Sat Dec 19 00:58:16 UTC 2009 (1)[code]....
Also attached is the trace file, from the trace file, everything seems ok, timestamps is sent and received:
I can compile and run ntpd 4.2.6p2, but after a while the reach indicator falls back from 377 to 0 and then the ntpd is in an unsynced state for a while. So far I haven't seen any indication why we have this.
View 1 Replies View RelatedI cant mount a directory on red hat 5 from red hat 4 using fstab.I keep getting permission denied.I mount directories on the same red hat 5 sys from other red hat 5 and 2 old HPUX systems using fstab.When I try to telnet to it i get "no route to host."
View 3 Replies View RelatedI am trying to synchronize the time of my VM server with ntpd. I have the following configuration. And in the /etc/ntp.conf, I have the following line:
restrict default ignore
restrict 127.0.0.1.
server time1.server
server time2.server
Whenever I have this line, the erver is not able to synchronize its time... So far as I understood, this line prevents other servers using this machine as a time server. And the second line says to allow localhost to use as time server. But why do I need to use its own time server when I have specified to use time1.server and time2.server ? ( firewall for tcp and udp ports 123 is open)
However, when I replace the first line of the configuration with the following line, it works. restrict default kod nomodify notrap noquery But with this, i am allowing other servers to use this server a ntp (which I wouldn't like to). Why this machine tries to use ntp server of its own (to snyc time) and why it is not working though i have the entry "restrict 127.0.0.1" ??
I use Arch, but no info about it in official wiki.
View 2 Replies View RelatedI have a problem with a server with os Linux RedHat Enterprise AS 4.7:
when the server boots both ntpd and rpc.statd fail to start.
looking into /var/log/messages I found:
and
For ntp, when the server completed the boot process, altough it seems ntpd started, no external server is used for syncronization. The rpc.statd does not start at all and it doesn't appear if I issue a rpcinfo -p
The strange thing is that at this point if I manually start or restart /etc/init.d/ntpd and /etc/init.d/nfslock both services start with no errors. Another strange thing is the timestamp for messages into /var/log/messages. How could it be possible to have a line with a certain timestamp and the following with a timestamp 30 seconds before?
The kernel version in use is 2.6.9-55.0.12.ELsmp #1 SMP x86_64
I'd like to get the 13.0 "synchronized to <time server>, stratum <stratum>" messages back on 13.1.
- On 13.0, running ntpd 4.2.4p8, reassuring messages appeared in /var/log/messages like "synchronized to 211.233.84.186, stratum 2".
- On 13.1, running ntpd 4.2.6p1, there are no messages in /var/log/messages to confirm that time is being synchronised.
rc.ntpd on both starts ntpd with the same options. /etc/ntp.conf is identical on both, a "get it working and then make it secure" version:
Code:
cat /etc/ntp.conf | grep -E -v '^$|^#' cat /etc/ntp.conf | grep -E -v '^$|^#'
server in.pool.ntp.org
server asia.pool.ntp.org
server 127.127.1.0
fudge 127.127.1.0 stratum 10
driftfile /etc/ntp/drift
According to Linux Home Networking, synchronization can be checked using ntpq -p. This shows synchronization is working. I would prefer to see that confirmation in /var/log/messages without having to run a command manually to check it. How to get the old messages back?
I am having a situation with an NTPD server.
Code:
remote refid st t when poll reach delay offset jitter
plesk2.datacent .INIT. 16 u - 64 0 0.000 0.000 0.000
91.198.87.118.b .INIT. 16 u - 64 0 0.000 0.000 0.000
core.fr.zeroloo .INIT. 16 u - 64 0 0.000 0.000 0.000
178-26-105-100- .INIT. 16 u - 64 0 0.000 0.000 0.000
and it remains so no matter how long I wait...
Hoping to get better results with ntpdate, I stopped NTPS and tried :
Code:
# ntpdate ntp.skynet.be
29 Mar 09:12:26 ntpdate[4715]: no server suitable for synchronization found
# ntpdate -ud ntp.skynet.be
29 Mar 09:14:02 ntpdate[4814]: ntpdate 4.2.4p4@1.1520-o Sun Nov 22 16:14:35 UTC 2009 (1)
transmit(195.13.23.5)
receive(195.13.23.5) .....
I am running Debian Lenny 64b, and every packages are totally updated. I have 25 identical servers. And there is just one giving me this problem. From what I see, it is not a connection/FW issue since ntpdate get replies from the ntp server (ntp.skynet.be is my isp's stratum 2 ntp server).
I have recently installed Slackware 13 (64bit) (Kernel 2.6.29.6) on an Acer Veriton M series with AMD Athlon cpu. I have started ntpd server and from it's log file it seems to be synchronising to each of the three stratum 2 servers specified in the ntp.conf file.
25 Mar 18:27:02 ntpd[4542]: time reset +2.163491 s
25 Mar 18:33:08 ntpd[4542]: synchronized to 130.88.200.4, stratum 2
25 Mar 18:37:25 ntpd[4542]: synchronized to 130.88.200.6, stratum 2
25 Mar 18:42:59 ntpd[4542]: time reset +2.282097 s
25 Mar 18:49:21 ntpd[4542]: synchronized to 130.88.200.6, stratum 2
25 Mar 18:50:17 ntpd[4542]: synchronized to 130.159.196.118, stratum 2
25 Mar 18:55:57 ntpd[4542]: synchronized to 130.88.200.6, stratum 2
25 Mar 18:58:57 ntpd[4542]: time reset +2.147508 s
If I invoke ntpdate from another linux machine, that ntpdate reports that the stratum of the ntpd server is too high and won't use it.
transmit(192.168.175.8)
receive(192.168.175.8)
transmit(192.168.175.8)
receive(192.168.175.8)
transmit(192.168.175.8)
192.168.175.8: Server dropped: strata too high
server 192.168.175.8, port 123
stratum 16, precision -20, leap 11, trust 000
refid [192.168.175.8], delay 0.02577, dispersion 0.00000
transmitted 4, in filter 4
reference time: cf562778.a310c705 Thu, Mar 25 2010 18:18:32.636
originate timestamp: cf562cdd.048cbee3 Thu, Mar 25 2010 18:41:33.017
transmit timestamp: cf562cd0.56618ce2 Thu, Mar 25 2010 18:41:20.337
filter delay: 0.02579 0.02577 0.02579 0.02579
0.00000 0.00000 0.00000 0.00000
filter offset: 12.68024 12.68024 12.68024 12.68024
0.000000 0.000000 0.000000 0.000000
delay 0.02577, dispersion 0.00000
offset 12.680248
25 Mar 18:41:20 ntpdate[9683]: no server suitable for synchronization found
I have run ntpd on another platform with Slackware 12 (32bit) and never had any problems.
I have a server running VMWare Server on it with 4 virtual machines running. I am trying to use NTPD to keep the time correct on all of the virtual machines. On my physical server, I have installed ntpd and this is it's config file:
Quote:# ntpd.conf
tinker panic 0
restrict 127.0.0.1
restrict default kod nomodify notrap
server 0.vmware.pool.ntp.org
server 1.vmware.pool.ntp.org
server 2.vmware.pool.ntp.org
[Code]...
ntpd startup fails during boot.Does startup just fine manually from command line once it's booted though. Any suggestions what I might adjust?
View 2 Replies View Related