<DISCLAIMER>"Ladies and gentlemen: the story you are about to hear is true.
Only the names have been changed to protect the innocent."</DISCLAIMER>
I am getting and error when i run the following command:
Code:
zenmodeler run -v10 -d YYYY.YYYYY.YYYYY.YYY
The out is:
Code:
DEBUG:zen.ZenModeler:Run in foreground, starting immediately.
DEBUG:zen.ZenModeler:in debug mode starting apply in main thread.
INFO:zen.ZenModeler:starting collector loop
INFO:zen.ZenModeler:collecting for device YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.ifconfig on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.swap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.memory on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.memory on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.cpu on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.process on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.ifconfig on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_rn on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.netstat_an on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_an on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.process on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.cmd.df on YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.cmd.uname for YYYY.YYYYY.YYYYY.YYY
INFO:zen.ZenModeler:no cmd plugins found for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.CiscoHSRP on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.IpServiceMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.InformantHardDiskMap for
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeMap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.CiscoMap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:using zenoss.snmp.DeviceMap on YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:using zenoss.snmp.InterfaceMap on YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:using zenoss.snmp.NewDeviceMap on YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.HPDeviceMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.PowerwareDeviceMap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.APCDeviceMap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.UCDHardDiskMap for
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeDiskMap on
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellCPUMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRFileSystemMap for
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.CpuMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.HPCPUMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellPCIMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellDeviceMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.RouteMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRSWInstalledMap for
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.NewRouteMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRSWRunMap for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:skipping zenoss.snmp.InterfaceAliasMap for
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.DbConnectionPool:Creating a new connection; Pool size: 0
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
INFO:zen.ZenModeler:snmp collection device YYYY.YYYYY.YYYYY.YYY
INFO:zen.ZenModeler:plugins: zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap,
zenoss.snmp.NewDeviceMap
DEBUG:zen.SnmpClient:timeout=1193848728.2, tries=2
DEBUG:zen.SnmpClient:Testing SNMP configuration
DEBUG:zen.ZenModeler:skipping zenoss.portscan.IpServiceMap for
YYYY.YYYYY.YYYYY.YYY
INFO:zen.ZenModeler:no portscan plugins found for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.SnmpClient:running <zenoss.snmp.DeviceMap.DeviceMap instance at
0x8afc32c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.DeviceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.InterfaceMap.InterfaceMap instance at
0x8ae2b8c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.InterfaceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.NewDeviceMap.NewDeviceMap instance at
0x86a75cc>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.NewDeviceMap
INFO:zen.SnmpClient:snmp client finished collection for YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ZenModeler:client for YYYY.YYYYY.YYYYY.YYY finished collecting
DEBUG:zen.ApplyDataMap:processing data for device YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ApplyDataMap:processing plugin zenoss.snmp.DeviceMap on device
YYYY.YYYYY.YYYYY.YYY
INFO:zen.ApplyDataMap:processing zenoss.snmp.DeviceMap for device
YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.ApplyDataMap:set attribute 'snmpSysName' to 'YYYY.YYYYY.YYYYY.YYY' on
object 'YYYY.YYYYY.YYYYY.YYY'
DEBUG:zen.Events:Found device=YYYY.YYYYY.YYYYY.YYY
DEBUG:zen.Events:EventClassInst=Set
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.Events:insert into history set
Location='',prodState=1000,firstTime=1193848549.746,severity=2,component='',summary='set
attribute \'snmpSysName\' to \'YYYY.YYYYY.YYYYY.YYY\' on object
\'YYYY.YYYYY.YYYYY.YYY\'',dedupid='YYYY.YYYYY.YYYYY.YYY||/Change/Set||2|set
attribute \\\'snmpSysName\\\' to \\\'YYYY.YYYYY.YYYYY.YYY\\\' on object
\\\'YYYY.YYYYY.YYYYY.YYY\\\'',eventKey='',DeviceGroups='|',DeviceClass='/Discovered',device='YYYY.YYYYY.YYYYY.YYY',eventClass='/Change/Set',lastTime=1193848549.746,ipAddress='66.178.128.133',message='set
attribute \'snmpSysName\' to \'YYYY.YYYYY.YYYYY.YYY\' on object
\'YYYY.YYYYY.YYYYY.YYY\'',Systems='|',deletedTime=null,evid='42b2a72e35f9e965ffffcdf'
ERROR:zen.Events:(1114, "The table 'history' is full")
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 31, in execute
result = cursor.execute(statement)
File "opt/zenoss/lib/python/MySQLdb/cursors.py", line 137, in execute
File "opt/zenoss/lib/python/MySQLdb/connections.py", line 33, in
defaulterrorhandler
OperationalError: (1114, "The table 'history' is full")
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
ERROR:zen.Events:(1114, "The table 'history' is full")
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 98, in sendEvent
evid = self.doSendEvent(event)
File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 132, in
doSendEvent
rescount = execute(curs, stmt)
File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 36, in execute
raise ex
OperationalError: (1114, "The table 'history' is full")
ERROR:zen.ApplyDataMap:plugin zenoss.snmp.DeviceMap device YYYY.YYYYY.YYYYY.YYY
Traceback (most recent call last):
File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 100, in
processClient
changed = self._applyDataMap(device, datamap)
File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 143, in
_applyDataMap
changed = self._updateObject(tobj, datamap)
File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 263, in
_updateObject
"set attribute '%s' "
File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 45, in
logChange
self.logEvent(device, compname, eventClass, msg, Event.Info)
File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 74, in
logEvent
self.datacollector.dmd.ZenEventManager.sendEvent(eventDict)
File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 103, in
sendEvent
raise ZenBackendFailure(str(e))
ZenBackendFailure: (1114, "The table 'history' is full")
INFO:zen.ZenModeler:scan time: 1.65 seconds
INFO:zen.ZenModeler:stopping...
This seems bad to me. Anyone have any suggestions?
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=12565#12565
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
