Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
HACMP cluster log
- Thread starter jkc924
- Start date
Hi,
The cluster.log file usually keeps track of your HACMP cluster activity : start/stop, event triggered, topology/resources modification ...
If you're doing a lot of modifications, cluster tests, or events are often triggered, then this file may grow.
I don't know if HACMP recreates the file if deleted, what you can do is delete the file and "touch" another one with the same attributes.
Bye .
regards.
The cluster.log file usually keeps track of your HACMP cluster activity : start/stop, event triggered, topology/resources modification ...
If you're doing a lot of modifications, cluster tests, or events are often triggered, then this file may grow.
I don't know if HACMP recreates the file if deleted, what you can do is delete the file and "touch" another one with the same attributes.
Bye .
regards.
hi,
If rthis file is 'big' , you should firstl check it for any recent errors and if it is a problem fix it .
You can tidy the file , there are several options
1. you can mv cluster.log cluster.log.1
touch cluster.log ( create an empty one )
and zip cluster.log.1
2. you can trim the file and keep so much data .
3. in /etc/syslog.conf , you will see an entry for HACMP log info local0.info ( this logs information to your log file , messages can be discarded , but you may need them for trouble shooting)
HTH
If rthis file is 'big' , you should firstl check it for any recent errors and if it is a problem fix it .
You can tidy the file , there are several options
1. you can mv cluster.log cluster.log.1
touch cluster.log ( create an empty one )
and zip cluster.log.1
2. you can trim the file and keep so much data .
3. in /etc/syslog.conf , you will see an entry for HACMP log info local0.info ( this logs information to your log file , messages can be discarded , but you may need them for trouble shooting)
HTH
You can use /usr/es/sbin/cluster/utilities/clcycle which is a HACMP utility. Normally it is started via crontab and without parameters (it only cycles hacmp.out). But one can use it with option cluster.log and it will cycle cluster.log to cluster.log.1 and cluster.log.1 to cluster.log.2 and so on.
That's what it do:
LOGFILE=$1
mv $LOGFILE.6 $LOGFILE.7 2> /dev/null
mv $LOGFILE.5 $LOGFILE.6 2> /dev/null
mv $LOGFILE.4 $LOGFILE.5 2> /dev/null
mv $LOGFILE.3 $LOGFILE.4 2> /dev/null
mv $LOGFILE.2 $LOGFILE.3 2> /dev/null
mv $LOGFILE.1 $LOGFILE.2 2> /dev/null
mv $LOGFILE $LOGFILE.1 2> /dev/null
touch $LOGFILE 2> /dev/null
HTH
Axel
That's what it do:
LOGFILE=$1
mv $LOGFILE.6 $LOGFILE.7 2> /dev/null
mv $LOGFILE.5 $LOGFILE.6 2> /dev/null
mv $LOGFILE.4 $LOGFILE.5 2> /dev/null
mv $LOGFILE.3 $LOGFILE.4 2> /dev/null
mv $LOGFILE.2 $LOGFILE.3 2> /dev/null
mv $LOGFILE.1 $LOGFILE.2 2> /dev/null
mv $LOGFILE $LOGFILE.1 2> /dev/null
touch $LOGFILE 2> /dev/null
HTH
Axel
- Status