[zenoss-users] 2.2.3 Zenhub Service wont start but will Run

[Jace]

So I have been battling this for a while and I need help.

My Old Environment:
VM Appliance with Zenoss upgraded to 2.2.3

Symptom: Every time I would move the VM between ESX Hosts Zenhub would not start and I would have to revert to a previous snapshot. After trying multiple things and reading I bunch, i decided to do a fresh install becuase of the issue I have read about on the forums with the VM Appliance.

My New Environemmt:
Centos 5 with Zenoss 2.2.3 RPM installed in a VM on ESX 3.5

I did a fresh install and all of the service started.

I restored a backup from the VM version of Zenoss, and fixed all the path issues from /home/zenoss to /opt/zenoss

All of the devices are in Zenoss now, however Zenhub will not start as a service. it runs just fine as Zenoss run -V10. I can model devices and do everything I need to do with it running verses started as a service, except... it appears none of the graphs will update unless zenhub is running as a service. 

So what to try?

--The mysql server is running, I can do a "Select * from events" and see updates being made to the table.

--zenhub run -V10 does not throw any errors that I can see . 

--The only thing that is a little suspect is i see this message in the zenhub debug

"zen.Events:insert into heartbeat set device='zenoss.xxx.com',component='zenmodeler',timeout=90 on duplicate key update lastTime=Null, timeout=90: --> 2"

is the duplicate key a normal message? and the fact that is says lastTime=Null doesnt seems goof. 

It shows this message for each service that it tried to update the heartbeat on.

Any help would be appreciated.

yoy




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23911#23911

-------------------- m2f --------------------