Linux system hangs giving ntp errors

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Linux system hangs giving ntp errors
# 1  
Old 01-21-2011
Linux system hangs giving ntp errors

Hi folks,
I am facing issue of my system (host1) getting hanged after throwing following ntpd messages. I am not able to ssh to the server there after. only option is to restart the host:
Dec 29 02:58:51 host1 ntpd[991]: time reset -0.207907 s
Dec 29 02:58:51 host1 ntpd[991]: synchronisation lost
Dec 29 04:20:20 host1 ntpd[991]: time reset 1.018233 s
Dec 29 04:20:20 host1 ntpd[991]: synchronisation lost
Dec 29 04:35:44 host1 ntpd[991]: time reset -0.468052 s
Dec 29 04:35:44 host1 ntpd[991]: synchronisation lost
Dec 29 08:27:47 host1 ntpd[991]: time reset 0.249744 s
Dec 29 08:27:47 host1 ntpd[991]: synchronisation lost
Dec 29 11:42:50 host1 syslogd 1.4.1: restart.
Dec 29 11:42:50 host1 syslog: syslogd startup succeeded

I checked the time of my client(host1) which is getting hanged and the ntp server and found that both are having same time.
ntpq -p output gives following:
[root@host1 log]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*server1.example.c server02.exampl 4 u 976 1024 377 0.701 10.092 0.886

[root@host1 log]# ntpstat
synchronised to NTP server (172.15.16.167) at stratum 5
time correct to within 99 ms
polling server every 1024 s

Please advice. Thanks in advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Solaris script using awk giving errors - please advise

I'm using solaris 10 Scenario as follows I have a logfile with 2 columns: column 1 = source directory + filename column 2 = destination directory + filename Using cron, my script polls for new files and adds them to the logfile ($ELOG) as described above. Using sed, the distination... (2 Replies)
Discussion started by: davidra
2 Replies

2. Red Hat

system freezes / hangs

Hi, We're using - openldap-2.3.43-12.el5_6.5 nss_ldap-253-25.el5 on RHEL-5.5 Intermittently the entire system hangs, no message is present in any of the log files, login to the system fails, ssh fails, ping fails, the only way to recover is to hard-boot the system. We consulted... (3 Replies)
Discussion started by: TheRock
3 Replies

3. Solaris

Solaris 10 system hangs

Solaris 10 (Sun V210) System hangs every couple of months. Have to go into ALOM to reset. I did a consolehistory report and seen this in it. Failed to exec inetd_start method of instance svc:/network/bootps/udp:default: I/O error WARNING: /pci@1c,600000/scsi@2 (glm0): Resetting... (3 Replies)
Discussion started by: Joeentech
3 Replies

4. Linux

How often does Linux NTP server update its time with the external NTP server?

All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies

5. UNIX for Dummies Questions & Answers

machine hangs for some time after giving password.

Hi I m trying to take a console of linux machine using putty. Whenever i connect to the machine and give password details to log into the machine it hangs for some time and then it allow the login. I m totally clueless why it is happening suddenly . ---------- Post updated at 01:14 AM... (1 Reply)
Discussion started by: pinga123
1 Replies

6. Solaris

System hangs (freezes) on system bell/beep

I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600. Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays. I have mitigated this by turning the system bell off in gnome-terminal, which I use... (3 Replies)
Discussion started by: DeadBadger
3 Replies

7. BSD

dmesg giving errors

When running dmesg, the output is a long list of the following: ACPI Error: No object attached to node 0xffffff00016622e0 20090521 exresnte-211 ACPI Error (uteval-0329): Method execution failed (Node 0xffffff00016622e0), AE_AML_NO_OPERAND As a workaround I resort to sysctl, which gives... (0 Replies)
Discussion started by: figaro
0 Replies

8. Solaris

System hangs

Hi, today when i started the OS Sun Solaris 10 it hangs on initialization. Following was shown in the end of the screen Initializing system Please wait.... * Please help? (3 Replies)
Discussion started by: malikshahid85
3 Replies

9. UNIX for Advanced & Expert Users

NTP errors

im getting errors on all of my NTP clients. Oct 27 14:44:15 cms2 ntpd: synchronisation lost Oct 27 15:08:25 cms2 ntpd: time reset 0.688591 s Oct 27 15:08:25 cms2 ntpd: synchronisation lost Oct 27 15:28:45 cms2 ntpd: time reset 0.462257 s i checked several things: ntpq> rv status=0644... (3 Replies)
Discussion started by: modcan
3 Replies

10. Programming

gcc Compiler Switches: giving Illogical Errors

Hi, Has anyone used gcc compiler and know alot about it? I am compiling a file with: gcc -o xyz xyz.c abc.o -lsocket -lnsl it compiles pretty fine. But whe I use switches gcc -o -Wall -pedantic -ansi xyz xyz.c abc.o -lsocket -lnsl it starts giving illogical, rather I should say stupid... (1 Reply)
Discussion started by: Ahsan
1 Replies
Login or Register to Ask a Question
ntp(1)							      General Commands Manual							    ntp(1)

NAME
ntp - query a clock running a Network Time Protocol daemon, either ntpd or xntpd SYNOPSIS
/usr/bin/ntp [-v] [-s] [-f] host1 | IPaddress1 ... OPTIONS
Specifies verbose output. The output shows the full contents of the received NTP packets, plus the calculated offset and delay. Sets local clock to remote time. This only happens if the offset between the local and remote time is less than 1000 seconds. The local clock is not reset if the remote host is unsynchronized. If you specify more than one host name on the command line, ntp queries each host in order, waiting for each host to answer or time- out before querying the next host. The local clock is set to the time of the first remote host that responds. Forces setting local clock regardless of offset. The -f option must be used with -s option. The local clock is not reset if the remote host is unsyn- chronized. DESCRIPTION
The ntp command may be retired in a future release; use the ntpdate(8) command instead. The ntp command is used to determine the offset between the local clock and a remote clock. It can also be used to set the local host's time to a remote host's time. The ntp command sends an NTP packet to the NTP daemon running on each of the remote hosts specified on the command line. The remote hosts must be running either the ntpd daemon or xntpd daemon. When the NTP daemon on the remote host receives the NTP packet, it fills in the fields (as specified in RFC 1129), and sends the packet back. The ntp command then formats and prints the results on the standard output. Note You can specify hosts by either host name or Internet address. The hosts that you specify must either exist in the /etc/hosts file, or in the master hosts database, if the database is being served to your system by BIND or Network Information Service (NIS). The default output shows the roundtrip delay of the NTP packet in seconds, the estimated offset between the local time and remote time in seconds, and the date in ctime format. See the ctime(3) reference page for more information. The -s and -f options can be used to reset the time of the local clock. RESTRICTIONS
Using the -s and -f options require that you be logged on as superuser. ERRORS
The following error messages can be returned by NTP: May indicate that the NTP daemon is not running on the remote host. The NTP command cannot resolve the specified host name in the /etc/hosts file. Check that the host exists in the /etc/hosts file, or that it exists in the master hosts database, if the database is being served to your system by BIND or NIS. EXAMPLES
In the following examples, some output text lines may be broken. The line end are marked with the backslash symbol () and the following line is indented. Such text may appear as a single line on your terminal. The following is the default output to an ntp query about a remote host with an internet address of 555.5.55.5: # /usr/bin/ntp 555.5.55.5 555.5.55.5: delay:1.845207 offset:-0.358460 Mon Aug 20 08:05:44 1991 The following is the verbose output to an ntp query about the same remote host: # /usr/bin/ntp -v 555.5.55.5 Packet from: [555.5.55.5] Leap 0, version 1, mode Server, poll 6, precision -10 stratum 1 (WWVB) Synch Distance is 0000.1999 0.099991 Synch Dispersion is 0000.0000 0.000000 Reference Timestamp is a7bea6c3.88b40000 Tue Aug 20 14:06:43 1991 Originate Timestamp is a7bea6d7.d7e6e652 Tue Aug 20 14:07:03 1991 Receive Timestamp is a7bea6d7.cf1a0000 Tue Aug 20 14:07:03 1991 Transmit Timestamp is a7bea6d8.0ccc0000 Tue Aug 20 14:07:04 1991 Input Timestamp is a7bea6d8.1a77e5ea Tue Aug 20 14:07:04 1991 555.5.55.5: delay:0.019028 offset:-0.043890 Tue Aug 20 14:07:04 1991 The fields are interpreted as follows: The address of the remote host from which this NTP packet was received. The leap second indicator. Non-zero if there is to be a leap second inserted in the NTP timescale. The bits are set before 23:59 on the day of insertion and reset after 00:00 on the following day. The NTP protocol version. The NTP mode can be Server, Client, Symmetric Pas- sive, Symmetric Active, or Broadcast. See RFC 1129 for more information on NTP modes. The desired poll rate of the peer in seconds as a power of 2. For example, if poll is equal to 6, that means that the poll rate is one message exchanged every 2**6 seconds. The precision of the remote host's clock in seconds as a power of 2. For example, if precision is equal to -10, that means that the pre- cision is 2**-10. The NTP daemon sets this automatically. The stratum of the clock in the NTP hierarchy, along with the source of the clock. The source is either the name of a reference standard (such as WWVB or GOES), or the Internet address of the clock that this clock references. The values reported are used internally by the NTP daemon. The values reported are used internally by the NTP daemon. The next five timestamps are given as NTP fixed-point values, in both hexadecimal and ctime. The timestamps are set either by this NTP process, or by the remote host you are querying. These timestamps are used by the local host to calculate delay and offset for this query. This specifies the last time the remote host clock was adjusted. (remote time) This specifies when the NTP request was transmitted by the local host to the remote host. (local time) This specifies when the NTP request was received at the remote host. (remote time) This specifies when the NTP response was transmitted by the remote host. (remote time) This specifies when the NTP response was received by the local host. (local time) This field summarizes the results of the query, giving the host name or inter- net address of the responding clock specified in the command line, the round-trip delay in seconds, and the offset between the two clocks in seconds (assuming symmetric round-trip times). SEE ALSO
ctime(3), ntp.conf(4), ntpdate(8), xntpd(8), xntpdc(8), ntpq(8) Internet time synchronization: The Network Time Protocol (RFC 1129) Network Administration ntp(1)