EVA Management Server logs

[BB21]

Hi,
We have 2 EVA8000s and two 2 EVA4000s managed by a dedicated Command View server. We run CA between the 8000s. We are running tight on space on the C drive on the managment server and need to clean-up files every two weeks. We noticed we have 10 log files that are 102,401 KB each. They are storage.trace.1, storage.trace.2 and .3 and .4, evapdcs-trace-081010-1.log, .1009-1.log, 1010-2.log, 1008-2.log and 1009-2.log.

Can someone explain whether these are default logs? Are they expected to grow as much and as quickly as ours and can they be cleaned up (deleted)? Is it possible that EVAPERF is running from a past collection and impacting the log growth?

Thanks for any help you can provide.

[IBaltay]

Hi,
evapdcs keeps running after the evaperf was finished. It will continue to run till the next reboot or manual stop of the service
But if there are no further evaperf requests,
the Data collector service performs a discovery every 10 minutes which gets logged within the evapdcs-event-yymmdd-#.log file only. During that time nothing will be logged within the evapdcs-trace-yymmdd-#.log file.

Resume
yes it is most probably the relict of the evaperf data collection...

[BB21]

Hi,
The server was rebooted several times and there is no EVAPERF process running (if that is what it starts with). The HP EVA Performance Data Collector shows not started under services (Manual).

Our evapdcs-trace-yymmdd-#.log files have modified dates all in the last three days. Is this the overflow from the evapdcs-event logs? Is the 10 minute discovery logging too many errors and filling up? Are these logs circular (re-written) or does a new one get created when the previous one is filled?

Thanks

[IBaltay]

Then it the data collector service is not running and this is only a residuum of the previous evaperf activity

[BB21]

These are the types of entries filling the logs:

10/10/08 21:38:24 - 5045012, evamet, 8436, 49892, 2, evamet, 149, Device now has 2 pathts
10/10/08 21:38:24 - 5045012, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUH86F
10/10/08 21:38:24 - 5045013, evamet, 8436, 49892, 2, evamet, 149, Device now has 3 pathts
10/10/08 21:38:24 - 5045014, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUJ86J
10/10/08 21:38:24 - 5045014, evamet, 8436, 49892, 2, evamet, 149, Device now has 4 pathts
10/10/08 21:38:24 - 5045015, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: P8BC8F3AAS9002
10/10/08 21:38:24 - 5045016, evamet, 8436, 49892, 2, evamet, 149, Device now has 2 pathts
10/10/08 21:38:24 - 5045017, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUH86F
10/10/08 21:38:24 - 5045018, evamet, 8436, 49892, 2, evamet, 149, Device now has 4 pathts
10/10/08 21:38:24 - 5045018, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUH85K
10/10/08 21:38:24 - 5045019, evamet, 8436, 49892, 2, evamet, 149, Device now has 3 pathts
10/10/08 21:38:24 - 5045020, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUH85K
10/10/08 21:38:24 - 5045021, evamet, 8436, 49892, 2, evamet, 149, Device now has 4 pathts
10/10/08 21:38:24 - 5045022, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUFB7L
10/10/08 21:38:24 - 5045022, evamet, 8436, 49892, 2, evamet, 149, Device now has 3 pathts
10/10/08 21:38:24 - 5045023, evamet, 8436, 49892, 2, evamet, 148, Attempt to add an existing controller - serial: PB5A7D4AAUFB7L
10/10/08 21:38:24 - 5045024, evamet, 8436, 49892, 2, evamet, 149, Device now has 4 pathts
10/10/08 21:38:24 - 5045025, m_100, 8436, 49892, 2, 4000, 1560, fillPageCache
10/10/08 21:38:24 - 5045026, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x1F
10/10/08 21:38:24 - 5045030, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x1F
10/10/08 21:38:24 - 5045035, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x25
10/10/08 21:38:24 - 5045040, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x25
10/10/08 21:38:24 - 5045045, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x29
10/10/08 21:38:24 - 5045050, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x29
10/10/08 21:38:24 - 5045054, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x27
10/10/08 21:38:24 - 5045061, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x27
10/10/08 21:38:24 - 5045067, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x2B
10/10/08 21:38:24 - 5045074, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x2B
10/10/08 21:38:24 - 5045081, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x1D
10/10/08 21:38:24 - 5045087, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x1D
10/10/08 21:38:24 - 5045093, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x21
10/10/08 21:38:24 - 5045098, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x21
10/10/08 21:38:24 - 5045103, fsscsi, 8436, 49892, 2, scsilun, 267, ScsiLun::logSense page 0x23
10/10/08 21:38:24 - 5045108, fsscsi, 8436, 49892, 2, scsilun, 26

[IBaltay]

what is the name of the listed file pls?

[BB21]

evapdcs-trace-081010-2.log

[IBaltay]

could it be that any application (e.g. MRTG, or CACTI or any other graphical perf application is requesting the evaperf collection continuosly pls?

[BB21]

I'm not sure, is there a way I can find out?

[IBaltay]

check if any of your CommandView EVA host applications is triggering the evaperf continuosly, can be the Windows Perfmon, CACTI, Nagios, MRTG or any other perf (SNMP) solutions, ...

[BB21]

I just scanned for those processes (assuming they have similiar names) and there are none. Is there a way I can be certain? Services that are running: HPCC for SAN Environments is running , HP Availaibilty Collector is running, and HP Insight Storage and Server agents also running, HP SMI-S CimServer running.

[IBaltay]

then it seem not be any visible process triggering the evaperf so maybe the quickest way is to send the evapdcs-trace-081010-1.log to the local HP for the analysis (because its growth is suspicious). You can also experiment with your files after the copy to the safe place and then you can see if and when they will appear again