- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NTP problem
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
Forums
Discussions
Discussions
Discussions
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
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
01-24-2006 04:23 AM
01-24-2006 04:23 AM
NTP problem
server timehost1.devenv1.bt.co.uk prefer
server timehost2.devenv1.bt.co.uk
driftfile /var/ntp/ntp.drift
and the relevant lines in netdaemons are:
export NTPDATE_SERVER=
XNTPD=1
export XNTPD_ARGS=
After starting xntpd, ntpq -p shows:
remote refid st t when poll reach delay offset disp
==============================================================================
hwdusi04e2 10.240.52.101 3 u 59 64 17 0.27 -0.794 1879.20
However, after a reboot I find that the server names have been changed to 0.0.0.0 like so:
server 0.0.0.0 prefer
server 0.0.0.0
driftfile /var/ntp/ntp.drift
and the following line in the netdaemons file has also been changed:
export NTPDATE_SERVER="0.0.0.0"
ntpq -p now gives:
remote refid st t when poll reach delay offset disp
==============================================================================
0.0.0.0 0.0.0.0 16 - - 64 0 0.00 0.000 16000.0
I two other similar systems which are both behaving normally andI'm struggling to find any differences between this one and those. What's going on?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 04:58 AM
01-24-2006 04:58 AM
Re: NTP problem
You need to find out what is doing that - check for a newconfig file:
/usr/newconfig/etc/rc.config.d/netdaemons
Does that have
export NTPDATE_SERVER="0.0.0.0"
The rest of your stuff is fine...
Also check /sbin/init.d/xntpd
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 05:02 AM
01-24-2006 05:02 AM
Re: NTP problem
See if yuo have PHCO_33171 installed. This would appear to the be source of your problem.
http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHCO_33171&context=hpux:800:11:23
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 12:51 PM
01-24-2006 12:51 PM
Re: NTP problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 01:58 PM
01-24-2006 01:58 PM
Re: NTP problem
1. Edit the /etc/rc.config.d/netdaemons file to configure the xntpd daemon to startup every time the system boots. Set the XNTPD variable to equal 1
export NTPDATE_SERVER= Timer server IP
export XNTPD=1
export XNTPD_ARGS=
For NTP servers, do not set the NTPDATE_SERVER variable (leave it blank). This variable is for NTP clients.
2. Edit the /etc/TIMEZONE file and specify the correct time zone for the system. Set the TZ variable to equal the time zone for the system. See the /usr/lib/tztab file for a list of all the available time zones.
TZ=CST6CDT
export TZ
3. Edit the /etc/ntp.conf file and define the NTP server (as described earlier in this module). Below is an example for defining an NTP server to use its local clock:
server 127.127.1.1
fudge 127.127.1.1 stratum 10
4. Start the xntpd daemon manually by executing the following command:
sbin/init.d/xntpd start
5. Wait. It could take up to 6 minutes for the xntpd daemon to start.
6. Verify the NTP server configuration (and its association with peer NTP servers) by executing the following command:
ntpq -p
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 02:19 PM
01-24-2006 02:19 PM
Re: NTP problem
At server: U only need to set: the XNTPD variable to equal 1 (/etc/rc.config.d/netdaemon). Others parameter should keep it be blank.
At client: U must set all below parameter:
export NTPDATE_SERVER='NTP server1 NTP server2'
export XNTPD=1
export XNTPD_ARGS=
and /etc/ntp.conf:
broadcastclient yes
server NTP server
driftfile /etc/ntp.drift
Pls review your confs again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 02:28 PM
01-24-2006 02:28 PM
Re: NTP problem
Please find the attached procedure to follow for install /verify your NTP Installation.
Regards,
Shameer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 10:19 PM
01-24-2006 10:19 PM
Re: NTP problem
DHCP was for some reason enabled for the primary network interface in the netconf file, even though we don't use DHCP. Having turned it off, the NTP client now behaves perfectly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2006 04:20 AM
01-25-2006 04:20 AM