mshundal
2012-09-12 13:36:29 UTC
mshundal [http://community.zenoss.org/people/mshundal] created the discussion
"zenoss 4.2.0 - zenwinperf keeps dieing"
To view the discussion, visit: http://community.zenoss.org/message/68532#68532
--------------------------------------------------------------
It just dies randomly and I can't keep it running or more than a few hours. Here a tail log...
2012-09-07 18:07:08,544 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\Disk Write Bytes/sec
2012-09-07 18:07:08,545 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\% Disk Write Time
2012-09-07 18:07:08,545 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\Free Megabytes
2012-09-07 18:07:23,540 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Disk Read Bytes/sec
2012-09-07 18:07:23,541 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\% Disk Read Time
2012-09-07 18:07:23,541 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Disk Write Bytes/sec
2012-09-07 18:07:23,542 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\% Disk Write Time
2012-09-07 18:07:23,542 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Free Megabytes
2012-09-07 18:07:49,485 ERROR zen.CollectorCmdBase: Unable to scan device 192.168.1.30: NT_STATUS_NET_WRITE_FAULT
2012-09-07 18:08:40,497 ERROR zen.CollectorCmdBase: Unable to scan device MOONDB6: NT_STATUS_IO_TIMEOUT
Even tried using a cron script below to revive it but that doesnt seem to work (i used something similar on debian and it worked like a charm however i've had to use this disrto just to be able to use zenoss)
[***@zenoss mhundal]$ uname -a
Linux zenoss.puretracks.com 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[***@zenoss mhundal]$ zenoss status
Daemon: zeneventserver program running; pid=26132
Daemon: zopectl program running; pid=26248
Daemon: zenhub program running; pid=26302
Daemon: zenjobs program running; pid=26381
Daemon: zeneventd program running; pid=26449
Daemon: zenping program running; pid=26489
Daemon: zensyslog program running; pid=26592
Daemon: zenstatus program running; pid=26567
Daemon: zenactiond program running; pid=26607
Daemon: zentrap program running; pid=26691
Daemon: zenmodeler program running; pid=26692
Daemon: zenperfsnmp program running; pid=26724
Daemon: zencommand program running; pid=26755
Daemon: zenprocess program running; pid=26790
Daemon: zenrrdcached program running; pid=26795
Daemon: zenjmx program running; pid=26839
Daemon: zenwin program running; pid=26915
Daemon: zeneventlog program running; pid=26951
Daemon: zenwinperf not running
[***@zenoss mhundal]$ cat ~/scripts/chk-zenwinperf
#!/bin/bash
#
# This script, invoked by crontab, checks for status of ZENWINPERF daemon and restarts if needed
#Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - M S Hundal (Sept. 4, 2012)
#
if [ -z "$ZWPTST1" ]
then
  ZWPTST1="0"
fi
ZWPTST1=`ps ax | grep zenwinperf | grep -v grep | wc -l`
ZWPTST2=$(($ZWPTST1 - 2));
if [ $ZWPTST2 == 1 ]
then
   echo "ZWPTST2 script ran at `date` and all is well" >> /opt/zenoss/log/script.log
else
   /opt/zenoss/bin/zenwinperf start
   echo "Zenwinperf daemon testing script had to intervene at `date`" >> /opt/zenoss//log/script.log
fi
[***@zenoss mhundal]$ crontab -l
*/10 * * * *Â Â Â Â Â Â Â Â Â /home/zenoss/scripts/chk-zenwinperf
[***@zenoss mhundal]$
I know the script runs cuz it appends to the log file in either case however zenwinperf isn't started for some reason. If i run the script manually, it works.
If anyone has seen this before, I'd really apericiate a hint to resolve it.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68532#68532]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"zenoss 4.2.0 - zenwinperf keeps dieing"
To view the discussion, visit: http://community.zenoss.org/message/68532#68532
--------------------------------------------------------------
It just dies randomly and I can't keep it running or more than a few hours. Here a tail log...
2012-09-07 18:07:08,544 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\Disk Write Bytes/sec
2012-09-07 18:07:08,545 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\% Disk Write Time
2012-09-07 18:07:08,545 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.36: \LogicalDisk(\\?\Volume{6cc36847-a83d-11e1-b0f1-806e6f6e6963})\Free Megabytes
2012-09-07 18:07:23,540 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Disk Read Bytes/sec
2012-09-07 18:07:23,541 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\% Disk Read Time
2012-09-07 18:07:23,541 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Disk Write Bytes/sec
2012-09-07 18:07:23,542 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\% Disk Write Time
2012-09-07 18:07:23,542 WARNING zen.winperf.PerfRpc: Bad counter for device 192.168.4.31: \LogicalDisk(\\?\Volume{78347767-1160-11e1-ba7a-806e6f6e6963})\Free Megabytes
2012-09-07 18:07:49,485 ERROR zen.CollectorCmdBase: Unable to scan device 192.168.1.30: NT_STATUS_NET_WRITE_FAULT
2012-09-07 18:08:40,497 ERROR zen.CollectorCmdBase: Unable to scan device MOONDB6: NT_STATUS_IO_TIMEOUT
Even tried using a cron script below to revive it but that doesnt seem to work (i used something similar on debian and it worked like a charm however i've had to use this disrto just to be able to use zenoss)
[***@zenoss mhundal]$ uname -a
Linux zenoss.puretracks.com 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[***@zenoss mhundal]$ zenoss status
Daemon: zeneventserver program running; pid=26132
Daemon: zopectl program running; pid=26248
Daemon: zenhub program running; pid=26302
Daemon: zenjobs program running; pid=26381
Daemon: zeneventd program running; pid=26449
Daemon: zenping program running; pid=26489
Daemon: zensyslog program running; pid=26592
Daemon: zenstatus program running; pid=26567
Daemon: zenactiond program running; pid=26607
Daemon: zentrap program running; pid=26691
Daemon: zenmodeler program running; pid=26692
Daemon: zenperfsnmp program running; pid=26724
Daemon: zencommand program running; pid=26755
Daemon: zenprocess program running; pid=26790
Daemon: zenrrdcached program running; pid=26795
Daemon: zenjmx program running; pid=26839
Daemon: zenwin program running; pid=26915
Daemon: zeneventlog program running; pid=26951
Daemon: zenwinperf not running
[***@zenoss mhundal]$ cat ~/scripts/chk-zenwinperf
#!/bin/bash
#
# This script, invoked by crontab, checks for status of ZENWINPERF daemon and restarts if needed
#Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - M S Hundal (Sept. 4, 2012)
#
if [ -z "$ZWPTST1" ]
then
  ZWPTST1="0"
fi
ZWPTST1=`ps ax | grep zenwinperf | grep -v grep | wc -l`
ZWPTST2=$(($ZWPTST1 - 2));
if [ $ZWPTST2 == 1 ]
then
   echo "ZWPTST2 script ran at `date` and all is well" >> /opt/zenoss/log/script.log
else
   /opt/zenoss/bin/zenwinperf start
   echo "Zenwinperf daemon testing script had to intervene at `date`" >> /opt/zenoss//log/script.log
fi
[***@zenoss mhundal]$ crontab -l
*/10 * * * *Â Â Â Â Â Â Â Â Â /home/zenoss/scripts/chk-zenwinperf
[***@zenoss mhundal]$
I know the script runs cuz it appends to the log file in either case however zenwinperf isn't started for some reason. If i run the script manually, it works.
If anyone has seen this before, I'd really apericiate a hint to resolve it.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68532#68532]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]