Oct 27, 2012 3:56 PM
Zenhub won't start after a reboot
-
Like (0)
I have the same problem as seen in another thread.
Fresh install of Zenoss 4.2 virtual appliance. When I try to add the first device manually, I get: error: errno 104 connection reset by peer.
As per the other thread, service zenoss status shows that zenhub is not running.
The only changes I made were to networking to change it from DHCP to a static IP address and add DNS servers. I amended these two files:
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/resolv.conf
Please advise on how to fix. Did I follow the correct procedure to change the networking? (I'm a Windows guy normally).
If I can't get this fixed in the next few days I'll have to go back to the previous version of Zenoss.
Problem fixed.
This time I set up a DHCP server and allowed Zenoss to get a DHCP address. Now zenhub starts and I can add devices.
Obviously I did something wrong when I manually changed the networking to use a static IP.
Please can someone advise on the correct process for setting a static IP. It's not ideal for Zenoss to use a DHCP address, even though I've given it a reservation.
Spoke too soon. I've just restarted the Zenoss appliance (from the vSphere Client using the Guest/Shutdown command). When I restarted the appliance, the zenhub daemon won't start again.
So it seem the problem is NOT changing the IP address. The problem is simply shutting down Zenoss!
Problem fixed (for real this time!).
Answer found in this post: message/68815#68815
I added the entries to /root/.bashrc, logged off then on again as root, then ran $ZENHOME/bin/zenoss_upgrade_pre.
I then ran service zenoss stop, followed by service zenoss start. Now zenhub actually stays up. Hooray!
Big thanks to Shane Scott for the original fix.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||