Elog collector alarm

Publication Date:  2012-12-05 Views:  400 Downloads:  0
Issue Description
Customer's server and 2 collectors  was installed on 3 servers.

failure:
one collector service stoped abormally, server side alarm.
The stoped service is as follows:
1.eLog WMIReceiverMgr service abnormally stop.
2.eLog JDBC collector service has stoped abnormally.

After failure collector re-installed, elog WMIReceiverMgr and logcollector problem remained.
Server side alarm disappeared after start collector service manually,  after restart failure collection server, it remain the failure.
Alarm Information
NULL
Handling Process
1、Decompress the attachment 20120425152233885.rar to:C:\eLog\logCollector\etc\conf  replacing the original files

2、Reboot Secoway eLog logCollector server

Root Cause
JDBC and WMI service depend on logCollector service,before JDBC and WMI sevice start,it needs logCollector started.

When reboot the device,logCollector server start slowly,JDBC and WMI service wait for long time, overtime, so it was not up. now it has optimized logCollector the load option when it start,it expedite the start speed.

the reason caused logcollector server slowly start is that this server loaded much drive, it is related with environment of server.
alarm          3      2012-4-24 11:09:01      updsm             CAIJI-1         NULL              lack                 SLP: SLP:RRSubset data wrong  ReSelPath
information  2      2012-4-24 11:09:01      updsm              CAIJI-1          NULL              lack                CFG: FOG Build(PathID:0x60004).

information          2      2012-4-24 11:09:01      mpio              CAIJI-1         NULL          lack                 Added device to \Device\MPIODisk4. DumpData contains the current number of paths.
information          2      2012-4-24 11:09:01      updsm            CAIJI-1         NULL              lack                 DEV: Dev(0x8b9ea930)WWN:6022A11093379156E27CE0007

Suggestions
NULL

END