We have had problems where the aselogger stops logging on either
cluster member. We have serveral 2 member ase's on our site and have
had this problem across 3 releases of OS and 3 respective releases of
TruCluster Software i.e V1.41-1.6. We have suspected CA's
UNICENTER/TNG of restarting syslog and causing this problem. The idea
is that aselogger loses it's 'handshake' with syslogd and hence the
problem. I have talked to support about this and all I have been told
now is that the only way to restart aselogger(You cannot HUP it) is to
do an asemember restart. This would cause an outage because the
services would have to failover to the other member. Has anyone else
seen this issue? Any ideas, thoughts will be greatly
appreciated........
Tks & Rgds,
Alay Shah
Allegiance Healthcare Corp.
1400 Waukegan Rd.
MPDS-72
McGaw Park, IL 60085
Ph - 847-578-2584
Fax - 847-578-5586
Email - shahal_at_allegiance.net
Received on Wed Jul 26 2000 - 14:48:54 NZST