[Zenoss-dev] Issues with 2.1.70

Eric Newton ecn at zenoss.com
Mon Jan 14 06:56:45 EST 2008 

Zenping, zensyslog and zentrap all use zensocket to get a privileged
socket.  Since all three of these are breaking for you, I imagine that
zensocket has the wrong permissions.  As root, execute the following:

	# chmod 04750 $ZENHOME/bin/zensocket
	# chown root:zenoss $ZENHOME/bin/zensocket

How did you install 2.1.70?  RPM?  Which platform are you on (perhaps
zensocket is not packaged properly).

Thanks!

-Eric


jsauve wrote:
> Since installing 2.1.70:
> 
> 1) Zenping, Zensyslog and Zentrap daemons keep stopping.
> 
> In the Zenping log, I'm seeing this:
> 
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'RJCPWINSBS' network '192.168.0.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'JFA-MF3' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'JFA-MF2' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'VIRUSWALL2' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'JFA-FAXSERVER' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'JFA-AD' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'IPS-SERVER' network '192.168.70.0/24' not in topology
> 2008-01-12 10:11:59 WARNING zen.ZenStatus: device 'FMS_BORDER' network '192.168.75.0/24' not in topology
> 2008-01-12 10:12:37 INFO zen.ZenPing: Finished pinging 33 jobs in 0.04 seconds
> 2008-01-12 10:13:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:14:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:15:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:16:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:17:37 INFO zen.ZenPing: Finished pinging 33 jobs in 0.04 seconds
> 2008-01-12 10:18:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:19:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:20:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:21:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:22:37 INFO zen.ZenPing: Finished pinging 33 jobs in 0.04 seconds
> 2008-01-12 10:23:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:24:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:25:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:26:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:27:37 INFO zen.ZenPing: Finished pinging 33 jobs in 0.04 seconds
> 2008-01-12 10:28:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:29:38 INFO zen.ZenPing: Finished pinging 33 jobs in 1.54 seconds
> 2008-01-12 10:30:05 INFO zen.ZenPing: delete pidfile /usr/local/zenoss/var/zenping.py.pid
> 2008-01-12 10:30:05 INFO zen.ZenPing: Daemon ZenPing shutting down
> 2008-01-12 10:30:05 INFO zen.ZenPing: stopping...
> 2008-01-12 10:30:06 INFO zen.ZenPing: stopped
> 2008-01-12 11:05:17 ERROR watchdog: Timeout: getting initial connection from process
> 2008-01-12 11:05:18 ERROR watchdog: Restarting zenping
> 
> Don't quite understand this "not in topology" error; everything seems to be there.
> 
> In Zensyslog, I get this over and over and over:
> 
> 2008-01-12 21:34:10 INFO zen.ZenSyslog: started
> 2008-01-12 21:36:08 ERROR watchdog: Timeout: getting initial connection from process
> 2008-01-12 21:38:15 ERROR watchdog: Restarting zensyslog
> 2008-01-12 21:38:17 INFO zen.ZenSyslog: started
> 2008-01-12 21:40:15 ERROR watchdog: Timeout: getting initial connection from process
> 2008-01-12 21:46:08 ERROR watchdog: Restarting zensyslog
> 2008-01-12 21:46:10 INFO zen.ZenSyslog: started
> 2008-01-12 21:48:08 ERROR watchdog: Timeout: getting initial connection from process
> 2008-01-12 21:50:15 ERROR watchdog: Restarting zensyslog
> 2008-01-12 21:50:17 INFO zen.ZenSyslog: started
> 
> 
> Same thing - repeatedly - for Zentrap.
> 
> 2) Can't add messages to events
> 
> When going into the details of an event, we like to use the third tab - Log - to add notes and messages to events. This no longer works for any kind of event; we always get this:
> 
> Site error
> 
> An error was encountered while publishing this resource. The requested resource does not exist.
> Please click here to return to the Zenoss dashboard
> Request Information
> 
> 
> 3) With 2.1.2 we had set the zWinEventlogMinSeverity to 3 for Windows servers. That way, we were no longer getting Informational logs. With 2.1.70, this seems to have stopped; we now get severity 2 events.
> 
> 
> 4) Getting a lot of /Status/RRD messages from "localhost". The message currently looks like this:
> 
> RRD files not updated: Devices/KAILO/hw/harddisks/8985/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/EVALUATEUR/os/interfaces/Broadcom NetXtreme Gigabit Ethernet Driver/ifOperStatus_ifOperStatus.rrd Devices/newton.adaris.ca/os/interfaces/vmnic0/ifOutErrors_ifOutErrors.rrd Devices/newton.adaris.ca/os/filesystems/vmfs_volumes_VMFILES/Disk_VDF_usedBlocks.rrd Devices/AdarisPIX.adaris.ca/os/interfaces/PIX Firewall _inside_ interface/ifInUcastPackets_ifInUcastPackets.rrd Devices/NPI915596/os/interfaces/HP ETHERNET MULTI-ENVIRONMENT,ROM M.22.01,JETDIRECT,JD89,EEPROM M.24.06/ifInUcastPackets_ifInUcastPackets.rrd Devices/HDSNOD/hw/harddisks/10518/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/newton.adaris.ca/os/filesystems/var_log/Disk_VDF_availBlocks.rrd Devices/AdarisPIX.adaris.ca/os/interfaces/PIX Firewall _outside_ interface/ifOutOctets_ifOutOctets.rrd Devices/NPI2ADA7C/os/interfaces/HP ETHERNET MULTI-ENVIRONMENT,ROM J.07.15,JETDIRECT EX,JD35,
EE
>  PROM J.08.49/ifOperStatus_ifOperStatus.rrd Devices/ts.adaris.ca/sysUpTime_sysUpTime.rrd Devices/newton.adaris.ca/os/interfaces/vmnic1/ifOutErrors_ifOutErrors.rrd Devices/NetGearSwitch/os/interfaces/GS724T  Gigabit Ethernet Interface_2/ifOutErrors_ifOutErrors.rrd Devices/EVALUATEUR/os/interfaces/Broadcom NetXtreme Gigabit Ethernet Driver/ifInErrors_ifInErrors.rrd Devices/ts.adaris.ca/os/interfaces/MS TCP Loopback interface/ifOutOctets_ifOutOctets.rrd Devices/ts.adaris.ca/hw/harddisks/30354/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/ts.adaris.ca/hw/harddisks/28315/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/HDSNOD/hw/harddisks/12997/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/newton.adaris.ca/sysUpTime_sysUpTime.rrd Devices/CERYX/hw/harddisks/51544/lDiskDiskReadBytesPerSec_lDiskDiskReadBytesPerSec.rrd Devices/JFA-ZEN/os/interfaces/HP NC10xx_NC67xx_NC77xx Gigabit Server Adapter/ifOutErrors_ifOutErrors.rrd Devices/HD
SN
>  OD/hw/harddisks/12388/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/CRM/hw/harddisks/117768/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/AdarisPIX.adaris.ca/os/interfaces/PIX Firewall _inside_ interface/ifOutUcastPackets_ifOutUcastPackets.rrd Devices/newton.adaris.ca/os/interfaces/vmnic0/ifInOctets_ifInOctets.rrd Devices/newton.adaris.ca/memBuffer_memBuffer.rrd Devices/HDSNOD/hw/harddisks/12729/lDiskDiskWriteBytesPerSec_lDiskDiskWriteBytesPerSec.rrd Devices/LJ3800D/os/interfaces/HP ETHERNET MULTI-ENVIRONMENT,ROM none,JETDIRECT,JD128,EEPROM V.28.61_2/ifOutOctets_ifOutOctets.rrd Devices/ts.adaris.ca/hw/harddisks/13503/lDiskDiskReadBytesPerSec_lDiskDiskReadBytesPerSec.rrd Devices/ACE/hw/harddisks/D/lDiskDiskReadBytesPerSec_lDiskDiskReadBytesPerSec.rrd Devices/AdarisPIX.adaris.ca/os/interfaces/PIX Firewall _inside_ interface/ifInErrors_ifInErrors.rrd Devices/HDSNOD/hw/harddisks/12388/lDiskDiskReadBytesPerSec_lDiskDiskReadBytesPerSec.rrd Dev
ic
>  es/newton.adaris.ca/os/interfaces/vmnic1/ifOutOctets_ifOutOctets.rrd Devices/newton.adaris.ca/os/interfaces/lo/ifInOctets_ifInOctets.rrd Devices/ts.adaris.ca/hw/harddisks/28315/lDiskDiskReadBytesPerSec_lDiskDiskReadBytesPerSec.rrd Devices/ts.adaris.ca/os/interfaces/Broadcom NetXtreme Gigabit Ethernet _2/ifOutErrors_ifOutErrors.rrd Devices/newton.adaris.ca/os/interfaces/vswif0/ifOutUcastPackets_ifOutUcastPackets.rrd Devices/PARETO/os/interfaces/MS TCP Loopback interface/ifOperStatus_ifOperStatus.rrd Devices/NetGearSwitch/os/interfaces/GS724T  Gigabit Ethernet Interface_2/ifOutOctets_ifOutOctets.rrd Devices/ACE/os/interfaces/HP NC373i Multifunction Gigabit Server Adapter/ifOperStatus_ifOperStatus.rrd Devices/LJ3800D/os/interfaces/HP ETHERNET MULTI-ENVIRONMENT,ROM none,JETDIRECT,JD128,EEPROM V.28.61/ifOutOctets_ifOutOctets.rrd Devices/newton.adaris.ca/os/filesystems/var_log/Disk_VDF_totalBlocks.rrd Devices/ts.adaris.ca/memoryAvailableKBytes_memoryAvailableKBytes.rrd Devices/P
AR
>  ETO/os/interfaces/MS TCP Loopback interface/ifOutUcastPackets_ifOutUcastPackets.rrd Devices/newton.adaris.ca/os/filesystems/dev_shm/Disk_VD
> 
> 
> Is my RRD database simply screwed up? If so, is there a way to fix it?
> 
> 
> 
> 
> -------------------- m2f --------------------
> 
> Read this topic online here:
> http://community.zenoss.com/forums/viewtopic.php?p=15265#15265
> 
> -------------------- m2f --------------------
> 
> 
> 
> _______________________________________________
> zenoss-dev mailing list
> zenoss-dev at zenoss.org
> http://lists.zenoss.org/mailman/listinfo/zenoss-dev
>

More information about the zenoss-dev mailing list