- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NTP not working - coundn't start !
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 06:23 AM
тАО06-08-2009 06:23 AM
anyone pls suggest the solution ?
here are the information...
bank1:/sbin/init.d #ntpq -p
ntpq: read: Can't assign requested address
bank1:/sbin/init.d #/sbin/init.d/xntpd start
bank1:/sbin/init.d #ps -ef | grep ntp
root 9596 9496 0 16:00:06 pts/2 0:00 grep ntp
bank1:/sbin/init.d #ntpdate -d 10.15.144.1
transmit(10.15.144.1)
transmit(10.15.144.1)
transmit(10.15.144.1)
transmit(10.15.144.1)
transmit(10.15.144.1)
server 10.15.144.1, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000
transmit timestamp: cdd7980f.029d7000 Mon, Jun 8 2009 16:00:47.010
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
8 Jun 16:00:48 ntpdate[9600]: no server suitable for synchronization found
bank1:/sbin/init.d #ntpdate 10.15.144.1
8 Jun 16:01:32 ntpdate[9603]: no server suitable for synchronization found
Solved! Go to Solution.
- Tags:
- NTP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 06:27 AM
тАО06-08-2009 06:27 AM
SolutionIf you server's time differs from true time by more than 1000 seconds, NTP will fail to attempt to synchronize. Verify _your_ time with 'date -u'. Remember, NTP uses universal (UTC) time. Your server displays local time according to your TZ setting.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 06:42 AM
тАО06-08-2009 06:42 AM
Re: NTP not working - coundn't start !
the time almost the same, different about 30 seconds...
but the ntp still cannot start...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 06:43 AM
тАО06-08-2009 06:43 AM
Re: NTP not working - coundn't start !
I'd suggest starting from the beginning to fix time (...that sounds so Isaac Asimov..).
Stop xntpd
Confirm and assign internal server(s) to external time source.
Confirm your primary internal time server(s) are now syncing properly to external time source(s).
Once the above looks good....stop/start time on your secondary servers that sync internally to your internal primary time server(s).
...and like Jim said - if they are too far off, you'll have to manually reset the time to something closer. But if your going forward in time - not so bad. Do NOT go backwards in time, as you could have database issues. Co-ordinate for those situations.
Rgrds,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 06:51 AM
тАО06-08-2009 06:51 AM
Re: NTP not working - coundn't start !
ntpq: read: Can't assign requested address
more than likely, the ntp port is occupied by another program, most probably a hung ntp related command.
lsof -i :123
should give you who is holding the port 123 (port that ntp uses) If there is nothing holding this port, I am not sure what to say
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 07:06 AM
тАО06-08-2009 07:06 AM
Re: NTP not working - coundn't start !
NTP will not correct time differences more than a few hours.
The message is clear:
8 Jun 16:01:32 ntpdate[9603]: no server suitable for synchronization found
The server configured is not suitable for Unix ntp.
I know Windows Server 2000 is not appropriate as a time server without patches.
Most firewalls close the ntp port as well.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 09:39 AM
тАО06-08-2009 09:39 AM
Re: NTP not working - coundn't start !
how do we know if the server is not suitable for the ntp server ?
the bank2 hp server run the same environment as bank1, but it working perfectly fine...
any more suggestion ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 09:47 AM
тАО06-08-2009 09:47 AM
Re: NTP not working - coundn't start !
the bank2 hp server run the same environment as bank1, but it working perfectly fine...
any more suggestion ?
check the
grep -i ntp /var/adm/syslog/syslog.log
and check it on both servers, may there will be a difference.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 10:00 AM
тАО06-08-2009 10:00 AM
Re: NTP not working - coundn't start !
there is no ntp log in syslog..... :(....probably has been disable..how do i reactive that ?
also, there's no differences between bank1 and bank2.....both have the same ntp ip address...but the bank2 working fine...
many thanks !!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 10:05 AM
тАО06-08-2009 10:05 AM
Re: NTP not working - coundn't start !
for example on our system :
kmsemng1:/>grep -i ntp /var/adm/syslog/syslog.log
Jun 28 17:24:04 kmsemng1 xntpd[1318]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Jun 28 17:24:04 kmsemng1 xntpd[1318]: precision = 6 usec
Jun 28 17:28:21 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
Jun 28 17:28:21 kmsemng1 xntpd[1318]: time reset (step) 0.658318 s
Jun 28 17:28:21 kmsemng1 xntpd[1318]: synchronisation lost
Jun 28 17:33:41 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
Aug 31 03:38:06 kmsemng1 xntpd[1318]: synchronisation lost
Aug 31 10:06:18 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
Nov 6 18:10:30 kmsemng1 xntpd[1318]: synchronisation lost
Nov 6 18:29:42 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
Jan 1 01:00:01 kmsemng1 xntpd[1318]: leap second occurred, stepped time back 1 second
May 16 21:46:12 kmsemng1 xntpd[1318]: synchronisation lost
May 17 00:29:17 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
May 17 03:50:21 kmsemng1 xntpd[1318]: synchronisation lost
May 18 12:45:36 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
May 18 15:24:00 kmsemng1 xntpd[1318]: synchronisation lost
May 22 13:23:07 kmsemng1 xntpd[1318]: synchronized to 10.36.126.1, stratum=2
that means the ntp client is synchronised, if you don't have this entries in your syslog, them the host is not synchronyzing the time.
mikap