I had exactly the same thing - zenhub wouldn't start after I rebooted a VM with Zenoss that didn't have clock sync'ed. zenhub.log had entries up until 20:14 that day - the VM clock was about 2 hours fast. When I rebooted zenhub wouldn't come up. No nasty messages in zenhub.log but I could see the old entries timed what was now "in the future". I COULD start zenhub manually with zenhub run -v 10 - it seemed to run fine in the foreground - but I couldn't get it going as a daemon. There were no .zec files anywhere.
Having hacked for at least one of my "missing hours", I took the box down until real time was past "latest zenhub.log time". After that, everything came up fine. I didn't change anything else so I am pretty sure it was a time dependency thing. Don't know what I would have done if it was a production box and it was 2 days behind though?? Any other thoughts??? Cheers, Jane -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=30584#30584 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
