HACMP的cluster.log中不断报错

nds521

按照大家给的建议都检查过了。
HA心跳和同步验证都没有问题，现在还是在cluster.log中每隔一小时产生一次这个信息。

nds521

yddll 发表于 2012-07-26 21:51
lslpp -l |grep -i tivoli看看

然后该怎么做，跟tivoli的安装有关吗？

coolcat982

- I asked if /var/adm was filling up...  ->
it's redirecting to envision central server,it's filling up in that
server
-- what exact version of AIX (oslevel -s )?
IV00823  SLP_SRVREG USES 100% CPU OR DUMPS CORE
IV07482  SLP_SRVREG LEAKS MEMORY
IV02032  SLP_SRVREG FILLS SYSLOG WITH DEBUG MESSAGES
IV07657  SLP_SRVREG USES LARGE AMOUNTS OF CPU BUT IS STILL RESPONSIVE
# oslevel -s
6100-06-03-1048
- He didn't know if they use IBM Systems Director...
http://www-03.ibm.com/systems/software/director/
If you are not using IBM Systems Director (which is usually the case)
you can do the following to stop the daemons and eliminate the unwanted
messages. # cp /etc/inittab /etc/inittab.bak
# vi /etc/inittab
Comment out the following two lines with a colon.
:platform_agent:2nce:/usr/bin/startsrc -s platform_agent >/dev/null
2>&1   (doesn't apply in this case)
:cimservices:2nce:/usr/bin/startsrc -s cimsys >/dev/null 2>&1
Save the file.
.
Refresh the inittab file
# telinit q
# stopsrc -s platform_agent
# stopsrc -s cimsys
# ps -ef |grep slp
If you have slp_srvreg process running, kill process id if running.
.
The above steps should prevent slp from logging to syslog.



Action Taken:
-------------
- Nick Gimben contacted me regarding the above messages, which are
related to Service Location Protocol (SLP).

From the snap:
# ps -ef | grep slp_srvreg
     UID      PID     PPID   C    STIME    TTY  TIME CMD
    root  4194436        1   0 13:01:01      -  0:09 ./slp_srvreg -D

# lssrc -a
Subsystem         Group            PID          Status
platform_agent                    3670134      active
cimsys                            3211398      active

- SLP provides a flexible and scalable framework for providing hosts
with access to information about the existence, location, and
configuration of network services.
- The SLP service is primarily used by IBM Systems Director.

- Customer is not using IBM Systems Director, he can go ahead and
disable the SLP service using the following steps:
1) # slp_srvreg -k
If the slp_srvreg server is still running after using "slp_srvreg -k",
kill it manually with a kill -9:
# ps -ef | grep slp_srvreg
# kill -9 <slp_pid>
2) # stopsrc -s cimsys
3) # stopsrc -s platform_agent
4) To prevent the slp_srvreg server from starting when the system is
rebooted, comment out the following two lines in /etc/inittab:
From:
platform_agent:2nce:/usr/bin/startsrc -s platform_agent >/dev/null
2>&1
cimservices:2nce:/usr/bin/startsrc -s cimsys >/dev/null 2>&1
To (use a colon : for the comment sign in the /etc/inittab file):
: platform_agent:2nce:/usr/bin/startsrc -s platform_agent >/dev/null
2>&1
: cimservices:2nce:/usr/bin/startsrc -s cimsys >/dev/null 2>&1

Action Plan: Closing Secondary & Leaving Primary with Nick for Closure.
------------
+WSAS ROBOT ID         -5765G6200  -L103/-------P2S2-13/12/23-12:43--AT

Netcom: Assigned to M Aly
+WSAS ROBOT ID         -5765G6200  -L103/-------P2S2-13/12/23-12:43--AL
+GIMBEN, NICK          -5765G6200  -L16A/-------P2S2-13/12/23-12:47--AT

Customer Rep:   Denis

Action Taken: /var/adm/messages is filling up /var.

Conf NETC,  Mihammed

Had him check if they are using Systems Director,  he says no.

So,

from PSDB:

The error you are receiving is related to Service Location Protocol
(SLP).

From the snap:
# ps -ef | grep slp_srvreg
     UID      PID     PPID   C    STIME    TTY  TIME CMD
    root  4194436        1   0 13:01:01      -  0:09 ./slp_srvreg -D

# lssrc -a
Subsystem         Group            PID          Status
platform_agent                    3670134      active
cimsys                            3211398      active

Please Note:
- SLP provides a flexible and scalable framework for providing hosts
with access to information about the existence, location, and
configuration of network services.
- The SLP service is primarily used by IBM Systems Director.

If you are not using IBM Systems Director, you can go ahead and disable
the SLP service using the following steps:
1) # slp_srvreg -k
If the slp_srvreg server is still running after using "slp_srvreg -k",
kill it manually with a kill -9:
# ps -ef | grep slp_srvreg
# kill -9 <slp_pid>
2) # stopsrc -s cimsys
3) # stopsrc -s platform_agent
4) To prevent the slp_srvreg server from starting when the system is
rebooted, comment out the following two lines in /etc/inittab:
From:
platform_agent:2nce:/usr/bin/startsrc -s platform_agent >/dev/null
2>&1
cimservices:2nce:/usr/bin/startsrc -s cimsys >/dev/null 2>&1
To (use a colon : for the comment sign in the /etc/inittab file):
: platform_agent:2nce:/usr/bin/startsrc -s platform_agent >/dev/null
2>&1
: cimservices:2nce:/usr/bin/startsrc -s cimsys >/dev/null 2>&

He followed those steps,  and the file is no longer growing.

nds521

coolcat982 发表于 2013-12-25 18:28
- I asked if /var/adm was filling up...  ->
it's redirecting to envision central server,it's fillin ...

时隔多年，这个帖子终于可以结了！！！感谢各位朋友热心帮助！！