Sponsored Content
Operating Systems AIX xntpd starts after reboot only when HACMP services are started ? Post 302421875 by vilius on Monday 17th of May 2010 01:23:38 AM
Old 05-17-2010
Hi,

I tried to start xntpd when hacmp is down(only host address is active) but results are the same. By the way xntpd starts not after bringing up the resourse group(resource group brings service IP up), but only after hacmp services start(starting hacmp services doesn't activate resource groups automatically in this configuration).
What do you mean by this:
Quote:
Make xntpd use the nodeīs Persistent Address.
How do I make xntpd to use one IP or another ?

V
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Command xntpd

Hi: I,am trying syncronise clock, but i canīt do it In the server client put: /etc/ntp.conf -> server namehost -> resolver /etc/xntpres /etc/tcp -> uncoment lines when say Xntpd /etc/ xntpd In the server as server clock: /etc/ntp.conf -> peers hostname if... (1 Reply)
Discussion started by: AlvaroD
1 Replies

2. IP Networking

Services not started - HELP!!!!

Yesterday, we had an outage and Solaris 8 Sunfirer Server. Now today we can telnet, ftp or rhost in the server. We are getting error message connection refused for each connection. Is there any other way to get into box to see what is going on with the services? Please advise ASAP (4 Replies)
Discussion started by: cassy
4 Replies

3. AIX

services persistant across reboot

Hi, I am nerw to AIX. how can i make certain services to be persistant across reboot,similar to "chkconfig" in linux. Thanks, amit (2 Replies)
Discussion started by: amit4g
2 Replies

4. HP-UX

Services persistant across reboot

Hi All, I need to run a daemon which should start automatically during reboot. which all files i need to alter/modify ? /etc/inittab ? Thanks, Amit (1 Reply)
Discussion started by: amit4g
1 Replies

5. AIX

HACMP does not start db2 after failover (db2nodes not getting modified by hacmp)

hi, when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies

6. AIX

Thoughts on HACMP: Automatic start of cluster services

Hi all, I remember way back in some old environment, having the HA cluster services not being started automatically at startup, ie. no entry in /etc/inittab. I remember reason was (taken a 2 node active/passive cluster), to avoid having a backup node being booted, so that it will not... (4 Replies)
Discussion started by: zaxxon
4 Replies

7. Shell Programming and Scripting

Need to write a shell script that starts one, then kills it, then starts another?

This is on a CentOS box, I have two scripts that need to run in order. I want to write a shell script that calls the first script, lets it run and then terminates it after a certain number of hours (that I specify of course), and then calls the second script (they can't run simultaneously) which... (3 Replies)
Discussion started by: btramer
3 Replies

8. Linux

Application services not starting with server reboot

Hi All, My application uses three different sub-services to make complete application up and running to normal. The entry of all the three services are present in /etc/init.d directory with proper softlink created to application home path where it actually exists. In one rare case one of the... (3 Replies)
Discussion started by: hk_kamozalwar
3 Replies

9. Solaris

Lot of services in non-global zones, in uninitialized after reboot

Hello, This is Solaris-10 server, running with 4 non-global zones. This server was hung today and I had to reboot it forcefully from console. Then root file-system was not clean and I had to run fsck from failsafe mode. After it came back in run-level-3, lot of services are showing in... (3 Replies)
Discussion started by: solaris_1977
3 Replies

10. Shell Programming and Scripting

Inotifywait restart script prevents reboot when started

Hi, maybe someone could help me optimizing this little script. It works so far, but when running, reboot does not work. If kill inotifywait reboot from shell works. I think some optimization is required here. This script starts at the end of the boot process, from an external device and... (3 Replies)
Discussion started by: lowmaster
3 Replies
ntp_manual_setup(7)					 Miscellaneous Information Manual				       ntp_manual_setup(7)

NAME
ntp_manual_setup - Describes how to manually set up the Network Time Protocol (NTP) DESCRIPTION
Setting up the Network Time Protocol (NTP) manually includes selecting your most accurate time source and then configuring the following: Local NTP servers NTP clients You can also choose to set your system time with the rdate command, which is explained in the Setting Network Time with rdate section in this reference page. Setting Up a Local NTP Server What you must do to configure a local NTP server depends on your time source. If your time source is Internet NTP servers, see the Time Source - Internet NTP Servers section in this reference page. If your time source is a local reference clock, see the Time Source - Local Reference Clock section in this reference page. Time Source - Internet NTP Servers Use the following procedure to set up your local NTP servers if your time source is Internet NTP servers: Select three Internet primary or secondary servers for each local NTP server. Selecting a different set of Internet servers for each local server is recommended. Secondary servers are usually as reliable and accurate as primary servers. See the Network Administration manual for information on obtaining a list of Internet servers. Decide which options to the xntpd daemon you want to run. You can chose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will log only the initialization message and error messages to syslog. Edit the /etc/ntp.conf file. You must add a peer entry to the /etc/ntp.conf file for each Internet server. Each Internet server must either have an entry in the local /etc/hosts file or the hosts file distributed by BIND or NIS. The following /etc/ntp.conf file is for a local NTP server that is synchronizing its time with the fictitious Internet time servers host1, host2, and host3. The version 1 after host3 indicates that host3 is running the ntpd daemon instead of the xntpd daemon. (Servers running Tru64 UNIX run the xntpd daemon.) The line driftfile /etc/ntp.drift indicates the location of the drift file on this system. # # XNTPD Configuration File (template for NTP V3) # # # Specify a filename for the driftfile created by xntpd. # /etc/ntp.drift is the default. # driftfile /etc/ntp.drift # # # # # Specify several NTP servers and/or peers (See the xntpd # documentation for recommendations on selecting servers and peers). # NOTE: Be sure to specify the version number of the server/peer: # # peer host1 version 2 # xntpd V2 # server host2 version 1 # ntpd V1 # server host3 version 3 # xntpd V3 # # For further information on configu- ration options, see the xntpd # documentation. If you have a local accurate clock (radio clock, # etcetera), you will need to spec- ify further configuration options. # #Server and peer configuration peer host1 version 3 peer host2 version 3 peer host3 version 1 Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following series of commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host1 # /usr/sbin/rcmgr set XNTP_SERV2 host2 # /usr/sbin/rcmgr set XNTP_SERV3 host3 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host1, host2, and host3 with the names of the Internet pri- mary or secondary servers that you selected in step 1. Replace options with the options you selected in step 2. You must enclose the options in quotation marks (" "). Start the xntpd daemon with the following command: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command with the -p option: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Time Source - Local Reference Clock Use the following procedure to set up your local NTP servers if your time source is a local reference clock: Choose one of your local NTP servers to be the local reference clock. The other two local NTP servers can be set up as NTP clients that use the local reference clock and each other as peers. For example, if host4, host5, and host6 are the local NTP servers and host4 is the local reference clock, then you should set them up as follows: Set up host5 as an NTP client that specifies host4 and host6 as its local NTP servers Set up host6 as an NTP client that specifies host4 and host5 as its local NTP servers Complete steps 3 through 6 only if you are setting up the local reference clock. Decide which options to the xntpd daemon you want to run. You can choose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will log only the initialization message and error messages to syslog. Edit the /etc/ntp.conf file and add the following entry: # peer 127.127.1.1 This entry allows the local reference clock to run at stratum 3. For more information about local refer- ence clocks, see the ntp.conf(4) reference page. Note that when using a local reference clock, you should never use stratum 1, since the clock may provide very inaccurate time. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following series of commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host4 # /usr/sbin/rcmgr set XNTP_SERV2 host5 # /usr/sbin/rcmgr set XNTP_SERV3 host6 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host4, host5, and host6 with the names of the hosts that you selected to be servers in step 1. Replace options with the options you selected in step 2. You must enclose the options in quota- tion marks (" "). Start the xntpd daemon with the following command: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Setting Up NTP Clients Use the following procedure to set up an NTP client: Decide which options to the xntpd daemon you want to run. You can choose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will only log the initialization message and error messages to syslog. For each client, add a server entry to the /etc/ntp.conf file for each local NTP server. The following /etc/ntp.conf file is for an NTP client that is synchronizing its time with the local NTP servers host4, host5, and host6. The line driftfile /etc/ntp.drift indicates the location of the drift file on this system. # # XNTPD Configuration File (template for NTP V3) # # # Specify a filename for the driftfile created by xntpd. # /etc/ntp.drift is the default. # driftfile /etc/ntp.drift . . . server host4 version 3 server host5 version 3 server host6 version 3 Remember that each local NTP server that you specify must have an entry in either the client's /etc/hosts file or in a BIND or NIS hosts database that is searched by your system. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host4 # /usr/sbin/rcmgr set XNTP_SERV2 host5 # /usr/sbin/rcmgr set XNTP_SERV3 host6 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host4, host5, and host6 with the names of three local NTP servers for your network. Replace options with the options you selected in step 1. You must enclose the options in quotation marks (" "). Enter the following command to start the xntpd daemon: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command with the -p option: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Setting Network Time with rdate For your system to use the rdate command to set its time to the average network time when it starts, you must add an entry for rdate to the /etc/rc.config file. If your network uses the Network Time Protocol (NTP) time service you might still want to put the rdate entry in the /etc/rc.config file; if NTP hosts are unreachable, the system's time will still be set. If NTP hosts are reachable, the ntpdate command, which runs after the rdate command, will set the time to NTP time before starting the xntpd daemon. You must use the rcmgr command to edit the /etc/rc.config file. Enter the following command to add an entry for the rdate command to the /etc/rc.config file: # /usr/sbin/rcmgr set RDATE_CONF YES RELATED INFORMATION
Commands: ntp(1), timedsetup(8), xntpdc(8).. Daemons: timed(8), xntpd(8). Routines: ctime(3). Files: ntp.conf(4). Introduction: ntp_intro(7). Network Administration delim off ntp_manual_setup(7)
All times are GMT -4. The time now is 04:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy