Zenoss server not showing device inventory. Errors with zeneventserver

2 posts / 0 new
Last post
Dlewis55
Dlewis55's picture
Offline
Last seen: 4 weeks 1 day ago
Joined: 03/29/2017 - 15:45
Posts: 2
Zenoss server not showing device inventory. Errors with zeneventserver

Zenoss server is not listing the devices and shows this error on web ui. Please advise

Events > Event Console
Type: <class 'zenoss.protocols.services.zep.ZepConnectionError'> 
Value: Could not connect to service. 

Events > Classes
Connection refused. Check zeneventserver status on Daemons

/opt/zenoss/log/zeneventserver.log
2017-03-29T20:49:17.463 [main] INFO  org.zenoss.zep.dao.ConfigDao - Maximum archive days: 1000
2017-03-29T20:49:18.035 [AmqpConnectionManager] INFO  org.zenoss.amqp.AmqpConnectionManager - Attempting to connect to message broker at amqp://zenoss@localhost:5672/zenoss
2017-03-29T20:49:18.060 [AmqpConnectionManager] INFO  org.zenoss.amqp.impl.ConnectionFactoryImpl - No AMQP connection heartbeat
2017-03-29T20:49:18.067 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - No external plug-ins found.
2017-03-29T20:49:18.131 [AmqpConnectionManager] INFO  org.zenoss.amqp.AmqpConnectionManager - Connected to message broker at amqp://zenoss@localhost:5672/zenoss
2017-03-29T20:49:18.800 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Starting plug-in: EventFlappingPlugin
2017-03-29T20:49:18.800 [main] INFO  org.zenoss.zep.impl.EventFlappingPlugin - Event flapping detection plugin loading configuration
2017-03-29T20:49:18.815 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Starting plug-in: TriggerPlugin
2017-03-29T20:49:18.836 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Starting plug-in: EventFanOutPlugin
2017-03-29T20:49:18.837 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Initialized plug-ins
2017-03-29T20:49:18.837 [main] INFO  org.zenoss.zep.impl.Application - Initializing ZEP
2017-03-29T20:49:18.952 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.EventIndexRebuilderImpl - Index rebuilding thread started for: event_summary
2017-03-29T20:49:18.952 [INDEX_REBUILDER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexRebuilderImpl - Index rebuilding thread started for: event_archive
2017-03-29T20:49:18.952 [main] INFO  org.zenoss.zep.impl.Application - Starting event aging at interval: 60000 milliseconds(s), inclusive severity: true
2017-03-29T20:49:18.953 [main] INFO  org.zenoss.zep.impl.Application - Validating that event_summary table is in a good state
2017-03-29T20:49:19.003 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.location (PATH)
2017-03-29T20:49:19.003 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.device_class (PATH)
2017-03-29T20:49:19.003 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.priority (INTEGER)
2017-03-29T20:49:19.004 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.systems (PATH)
2017-03-29T20:49:19.004 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.groups (PATH)
2017-03-29T20:49:19.004 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.production_state (INTEGER)
2017-03-29T20:49:19.004 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.ip_address (IP_ADDRESS)
2017-03-29T20:49:19.007 [INDEXER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexerImpl - Indexing thread started for: event_archive
2017-03-29T20:49:19.008 [INDEXER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.EventIndexerImpl - Indexing thread started for: event_summary
2017-03-29T20:49:19.009 [main] ERROR org.zenoss.zep.impl.Application - There was an error validating the event_summary table: org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DROP TRIGGER IF EXISTS pt_osc_zenoss_zep_event_summary_upd]; SQL state [HY000]; error code [1419]; You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable); nested exception is java.sql.SQLException: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) 

Jcurry
Jcurry's picture
Offline
Last seen: 3 days 7 hours ago
Joined: 01/02/2014 - 13:04
Posts: 407
It is possible that your

It is possible that your events database index is messed up.  It is possible to rebuild these indexes (if slightly scary), so take a system backup / snapshot first.  That said, t has always worked for me.

As the zenoss user, navigate to $ZENHOME/var/zeneventserver/index.

Stop Zenoss with a "zenoss stop".

Under there, there should be 2 directories, summary and archive.  Delete both directories with their contents.

Restart Zenoss - "zenoss start".

You should find those directories recreated.  These are just the indexes, not the events themselves.

 

These instructions are for Zenoss 4 and Zenoss 3.  Don't know if it will still work with Zenoss 5.

Cheers,

Jane

Log in to post comments