Here's the memory load of the 3.2.1 box.

root@blahblan-zenoss1:~# free m

             total       used       free     shared    buffers     cached

Mem:       1019512     940764      78748          0       1924      30032

-/+ buffers/cache:     908808     110704

Swap:      1044476    1010912      33564

Regarding the 4.2 box.

I just loaded up a rabbitmq-env.conf file here and added my variables:

/etc/rabbitmq

[root@blah-zenoss2 rabbitmq]# more rabbitmq-env.conf

#example rabbitmq-env.conf file entries

#Rename the node

NODENAME=blah-zenoss2.fqdn.com

#Config file location and new filename bunnies.config

CONFIG_FILE=/etc/rabbitmq/rabbitmq-env.conf

I then rebooted the box, but am seeing the same error and zenhub won't start.

Here's the output you requestd.  I replaced our fqdn with blah

[root@blahblah-zenoss2 ~]# /usr/sbin/rabbitmqctl list_queues -p /zenoss

Listing queues ...

Error: unable to connect to node 'blah-zenoss2.fqdn.com@blah-zenoss2': nodedown

DIAGNOSTICS

===========

nodes in question: ['blah-zenoss2.fqdn.com@blah-zenoss2']

hosts, their running nodes and ports:

- blah-zenoss2: [{rabbitmqctl5414,51346}]

current node details:

- node name: 'rabbitmqctl5414@blah-zenoss2'

- home dir: /var/lib/rabbitmq

- cookie hash: Gzyq/2JMhTgLWXJQrb+UxA==

I did add the hostname and IP in /etc/hosts.  Thank you.

Hi all,

I got rabbitmq to run on the 4.2 box by messing with some hostname settings in /etc/hosts and /etc/sysconfig/network and the rabbitmq-env.conf file referenced above, but I'm still not able to run zenhub.  I get the same error in the zenhub logs.

2012-08-30 12:23:25,919 INFO zen.HubService.RenderConfig: Starting graph retrieval listener on port 8090

2012-08-30 12:23:28,957 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer

2012-08-30 12:23:31,976 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer

2012-08-30 12:23:31,977 ERROR zen.ZenHub: Unable to send an event

Traceback (most recent call last):

  File "/opt/zenoss/Products/ZenHub/zenhub.py", line 576, in sendEvent

    self.zem.sendEvent(Event(**kw))

  File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 60, in sendEvent

    event = self._publishEvent(event)

  File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 82, in _publishEvent

    publisher.publish(event)

  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 283, in publish

    self._publish("$RawZenEvents", routing_key, event, mandatory=mandatory, immediate=immediate)

  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 302, in _publish

    mandatory, immediate)

  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 376, in publish

    headers=headers, declareExchange=declareExchange)

  File "/opt/zenoss/lib/python/zenoss/protocols/amqp.py", line 138, in publish

    raise Exception("Could not publish message. Connection may be down")

Exception: Could not publish message. Connection may be down

2012-08-30 12:23:39,092 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer

2012-08-30 12:23:42,096 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer

Here is the rabbitmq output to show that it is in fact running.

[root@zenoss2 ~]# /usr/sbin/rabbitmqctl list_queues -p /zenoss

Listing queues ...

...done.

[root@zenoss2 ~]#

[root@zenoss2 ~]#

[root@zenoss2 ~]# rabbitmqctl -n zenoss2  status

Status of node zenoss2@zenoss2 ...

[{pid,3462},

{running_applications,[{rabbit,"RabbitMQ","2.8.4"},

                        {os_mon,"CPO  CXC 138 46","2.1.8"},

                        {sasl,"SASL  CXC 138 11","2.1.5.4"},

                        {mnesia,"MNESIA  CXC 138 12","4.4.7"},

                        {stdlib,"ERTS  CXC 138 10","1.15.5"},

                        {kernel,"ERTS  CXC 138 10","2.12.5"}]},

{os,{unix,linux}},

{erlang_version,"Erlang (BEAM) emulator version 5.6.5 [source] [64-bit] [async-threads:30] [hipe] [kernel-poll:true]\n"},

{memory,[{total,24980344},

          {processes,10049144},

          {processes_used,10038448},

          {system,14931200},

          {atom,1069665},

          {atom_used,1053972},

          {binary,137952},

          {code,11791567},

          {ets,745336}]},

{vm_memory_high_watermark,0.39999999990517116},

{vm_memory_limit,843625267},

{disk_free_limit,1000000000},

{disk_free,5531357184},

{file_descriptors,[{total_limit,924},

                    {total_used,6},

                    {sockets_limit,829},

                    {sockets_used,4}]},

{processes,[{limit,1048576},{used,127}]},

{run_queue,0},

{uptime,220}]

...done.

Appreciate all the assistance.

Dave

Hi Shane and dpetzel,

First off, my apologies for dropping off the radar.  I was traveling for a work conference/summit last week and was out of touch entirely after the holiday weekend.  Second, a sincere thank you for your input and assistance.  I'm digging out today, and wanted to update you both on the latest.

Regarding my 3.2.1 build, it _appears_ it was a memory issue.  I asked the admin's of our ESX environment if I could up the RAM of the virtual box to 4 gigs, up from 1 gig.  Once that was done and the box was rebooted, zenhub has been running ever since.  It's been up for 11 days now.  Not that I'm out of the water, but I haven't had it up for more than 3 days for the last 4 months or so.  Feels like progress and the functionality I've been used to for the last 4 years.

Second, regarding the 4.2 build, I ended up starting again with a new virtual machine and will utilize the snapshot feature as I build/make changes to the box.  I had already deleted the box before your posts dpetzel, so I'm sorry not to provide feedback on your helpful input.  Very much appreciated and best regards.

Dave