Sponsored Content
Operating Systems Solaris ntp client configuration error Post 302712333 by nikhil kasar on Tuesday 9th of October 2012 05:14:04 AM
Old 10-09-2012
ntp client configuration error

hi all
ntp client side configuration file is done but in
Code:
 # ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
 ntpserver    .INIT.          16 u    -   64    0     0.00    0.000 15937.5
*LOCAL(0)        .LOCL.           5 l   63   64    3     0.00    0.000 3937.74

in given command output ntp is point to the local machine it is not sync with the ntpserver.

Last edited by DukeNuke2; 10-10-2012 at 06:02 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ntp configuration

Hi all, I'm sure this question was asked before but I couldn't find what I was looking for in the 2 threads I found on here. Here's my question/problem: I have an isolated (no connection to outside world at all) Unix network. I want to have time sync between my other non-PC based system... (0 Replies)
Discussion started by: mariobernier
0 Replies

2. Windows & DOS: Issues & Discussions

ntp client windows xp

All, I have a Windows XP client which I need to get time synchronized from a Linux ntp server. What are the commands to perform the setup and configuration? Thanks, Mike (1 Reply)
Discussion started by: bubba112557
1 Replies

3. Solaris

ntp server and ntp client

All, How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server. Any... (1 Reply)
Discussion started by: bubba112557
1 Replies

4. Red Hat

NTP Configuration on RHEL 5.4

Hi, I'm trying to configure NTP client, however it failes to sync correctly. Even after I manually set the time, once it connects with the NTP server, it pushes the time ahead by 4 hours. We have set an AIX host as NTP server. It works fine for other AIX hosts, however fails on RHEL 5.4 ... (4 Replies)
Discussion started by: max_min
4 Replies

5. Solaris

ntp server configuration

hi Please give me the configuration steps for NTP server. How do i sync other servers with this NTP server thanks to all (1 Reply)
Discussion started by: sijocg
1 Replies

6. Solaris

NTP client offset

How to add offset to NTP client so that, for eg., clock is -20 seconds? (2 Replies)
Discussion started by: orange47
2 Replies

7. UNIX for Dummies Questions & Answers

NTP configuration issue..

hello Guys, I have an NTP problem on my SUN N240 server. External NTP server is being used for this box and when i run 'ntpq -p' i get connection refused message; ntpq -p ntpq: read: Connection refused Here this is the ntp.conf file: cat /etc/ntp.conf # BEGIN NTP SERVERS server... (6 Replies)
Discussion started by: dyavuzy1
6 Replies

8. Red Hat

NTP Configuration file

Hi, Could you please explain about "restrict" parameters in /etc/ntp.conf in ntp client and ntp Servers. Example: restrict 127.0.0.1 restrict -6 ::1 restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap Regards, Mastan (1 Reply)
Discussion started by: mastansaheb
1 Replies

9. Red Hat

Yum client configuration error

Dear concern, I want to configure a yum client node. Yum configuration file (/etc/yum.repos.d/) is given below: # cat server.repo name=rhel6 baseurl=ftp://192.168.225.3/pub/Packages/ enabled=1 gpgcheck=0 We got following error message while executing yum list command. # yum clean... (1 Reply)
Discussion started by: makauser
1 Replies

10. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
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)
All times are GMT -4. The time now is 04:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy