Discussion:
Zeneventserver message on going into 'infrastructure' tab
richc
2012-12-27 16:14:28 UTC
Permalink
richc [http://community.zenoss.org/people/richc] created the discussion

"Zeneventserver message on going into 'infrastructure' tab"

To view the discussion, visit: http://community.zenoss.org/message/70705#70705

--------------------------------------------------------------
Hi all

This is a fresh install of 4.2 via the autodeploy script onto centos x64 running on a proxmox vm server (2.2)

when i go into the infrastructure tab I get a connection refused message - check zeneventserver in deamons

So I checked it, the service is stopped according to the display and I canot get it to start

log details below

Many thanks for any help with this

Rich


2012-12-27T16:09:58.325 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.systems (PATH)
2012-12-27T16:09:58.325 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.groups (PATH)
2012-12-27T16:09:58.325 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.production_state (INTEGER)
2012-12-27T16:09:58.325 [INDEX_REBUILDER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.IndexedDetailsConfigurationImpl - Indexed event detail: zenoss.device.ip_address (IP_ADDRESS)
2012-12-27T16:09:58.404 [INDEX_REBUILDER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexRebuilderImpl - Empty index detected.
2012-12-27T16:09:58.406 [INDEXER_EVENT_SUMMARY] INFO  org.zenoss.zep.index.impl.EventIndexerImpl - Indexing thread started for: event_summary
2012-12-27T16:09:58.912 [INDEXER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexerImpl - Indexing thread started for: event_archive
2012-12-27T16:09:58.912 [INDEX_REBUILDER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexRebuilderImpl - Recreating index for table event_archive
2012-12-27T16:09:59.412 [INDEX_REBUILDER_EVENT_ARCHIVE] INFO  org.zenoss.zep.index.impl.EventIndexRebuilderImpl - Finished recreating index for 0 events on table: event_archive
2012-12-27T16:09:59.506 [AmqpConnectionManager] INFO  org.zenoss.amqp.AmqpConnectionManager - Attempting to connect to message broker at amqp://***@localhost:5672/zenoss
2012-12-27T16:10:00.021 [AmqpConnectionManager] INFO  org.zenoss.amqp.AmqpConnectionManager - Connected to message broker at amqp://***@localhost:5672/zenoss
2012-12-27T16:10:00.610 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Starting plug-in: TriggerPlugin
2012-12-27T16:10:00.623 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Starting plug-in: EventFanOutPlugin
2012-12-27T16:10:00.625 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - Initialized plug-ins
2012-12-27T16:10:00.626 [main] INFO  org.zenoss.zep.impl.Application - Initializing ZEP
2012-12-27T16:10:00.799 [main] INFO  org.zenoss.utils.dao.impl.MySqlRangePartitioner - Adding partition p20121227_180000 to table event_time
2012-12-27T16:10:00.817 [main] INFO  org.zenoss.zep.impl.Application - Starting event aging at interval: 60000 milliseconds(s), inclusive severity: false
2012-12-27T16:10:00.818 [main] INFO  org.zenoss.zep.impl.Application - Starting event archiving at interval: 60000 milliseconds(s)
2012-12-27T16:10:00.820 [main] INFO  org.zenoss.zep.impl.Application - Starting database table optimization at interval: 60 minutes(s)
2012-12-27T16:10:01.010 [zenoss.queues.zep.zenevents] INFO  org.zenoss.amqp.AmqpConnectionManager$QueueWorker - Worker started, consuming messages on queue: zenoss.queues.zep.zenevents
2012-12-27T16:10:01.097 [main] INFO  org.zenoss.zep.impl.Application - Completed ZEP initialization
2012-12-27T16:10:01.205 [zenoss.queues.zep.modelchange] INFO  org.zenoss.amqp.AmqpConnectionManager$QueueWorker - Worker started, consuming messages on queue: zenoss.queues.zep.modelchange
2012-12-27T16:10:01.210 [zenoss.queues.zep.heartbeats] INFO  org.zenoss.amqp.AmqpConnectionManager$QueueWorker - Worker started, consuming messages on queue: zenoss.queues.zep.heartbeats
2012-12-27T16:10:01.215 [zenoss.queues.zep.migrated.archive] INFO  org.zenoss.amqp.AmqpConnectionManager$QueueWorker - Worker started, consuming messages on queue: zenoss.queues.zep.migrated.archive
2012-12-27T16:10:01.215 [zenoss.queues.zep.migrated.summary] INFO  org.zenoss.amqp.AmqpConnectionManager$QueueWorker - Worker started, consuming messages on queue: zenoss.queues.zep.migrated.summary
2012-12-27T16:10:12.507 [main] INFO  org.zenoss.zep.dao.ConfigDao - Maximum archive days: 1000
2012-12-27T16:10:14.600 [main] WARN  org.zenoss.utils.impl.ZenPackImpl - No egg-info found for ZenPack in /opt/zenoss/ZenPacks/ZenPacks.zenoss.PySamba-1.0.0-py2.7-linux-x86_64.egg/ZenPacks/zenoss/PySamba/lib.
2012-12-27T16:10:14.610 [main] INFO  org.zenoss.zep.impl.PluginServiceImpl - No external plug-ins found.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70705#70705]

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]
jcurry
2013-01-01 12:50:20 UTC
Permalink
jcurry [http://community.zenoss.org/people/jcurry] created the discussion

"Re: Zeneventserver message on going into 'infrastructure' tab"

To view the discussion, visit: http://community.zenoss.org/message/70758#70758

--------------------------------------------------------------
Hmm,
That looks like a happy zeneventserver.log as far as I can see. It looks like it is connecting successfully to the various RabbitMQ queues.  Don't worry about the last 2 lines about PySamba and no external plugins - that is normal.

You are trying to start the zeneventserver as the zenoss user, not the root user???  You should always work with Zenoss as the zenoss user - only exception is manipulating RabbitMQ queues.

You might check these queues - as root user, try:
rabbitmqctl -p /zenoss list_queues

You should see about 6 queues - but your zeneventserver.log does suggest that these are OK.

What do you have in zenhub.log, event.log, zeneventd.log?

Cheers,
Jane
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70758#70758]

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]
Loading...