Quantcast
Channel: Zenoss Community : Popular Discussions - zenoss-windows
Viewing all articles
Browse latest Browse all 155

zenwinperf routinely stops and needs to be restarted

$
0
0

I have a new Zenoss Core 4 installation, and I've noticed that the zenwinperf daemon is routinely stopping and needs to be restarted.

 

The logs seem pretty standard and then include a few things like:

 

2012-09-05 10:32:33,300 INFO zen.maintenance: Performing periodic maintenance
2012-09-05 10:32:33,301 INFO zen.zenwinperf: Counter eventCount, value 9692
2012-09-05 10:32:33,303 INFO zen.zenwinperf: 72 devices processed (8475 datapoints)
2012-09-05 10:32:33,305 INFO zen.collector.scheduler: Tasks: 73 Successful_Runs: 177 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0
2012-09-05 10:34:04,145 ERROR zen.CollectorCmdBase: Unable to scan device somemachine.domain.com: NT_STATUS_HOST_UNREACHABLE 2012-09-05 10:36:57,475 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Bytes Received/sec
2012-09-05 10:36:57,475 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Bytes Sent/sec
2012-09-05 10:36:57,476 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Packets Received Errors
2012-09-05 10:36:57,476 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Packets Received/sec
2012-09-05 10:36:57,477 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Packets Outbound Errors
2012-09-05 10:36:57,477 WARNING zen.winperf.PerfRpc: Bad counter for device x.x.x.x: \Network Interface(BASP Virtual Adapter)\Packets Sent/sec
2012-09-05 10:37:33,322 INFO zen.maintenance: Performing periodic maintenance
2012-09-05 10:37:33,322 INFO zen.zenwinperf: Counter eventCount, value 9701
2012-09-05 10:37:33,323 INFO zen.zenwinperf: 72 devices processed (9021 datapoints)
2012-09-05 10:37:33,325 INFO zen.collector.scheduler: Tasks: 73 Successful_Runs: 208 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0
2012-09-05 10:37:57,078 ERROR zen.CollectorCmdBase: Unable to scan device othermachine.domain.com: NT_STATUS_RESOURCE_NAME_NOT_FOUND


 

 

The daemon stopped shortly after the last message shown above.

 

Any ideas as to why this would be shutting down or how to keep it running?

 

Thanks,

Troy.


Viewing all articles
Browse latest Browse all 155

Trending Articles