This brings up some ideas I think others are having (vish I think mentioned it last night). Would it be better to base when a service is up or down by something not time based? Something maybe connection based, or possibly something not using absolute times (so that NTP sync doesn't matter). Possibly this is getting worked on already, but can't remember, haha. From: JuanFra Rodriguez Cardoso <juanfra.rodriguez.cardoso at gmail.com<mailto:juanfra.rodriguez.cardoso at gmail.com>> Date: Friday, November 30, 2012 2:49 AM To: Skible OpenStack <skible.openstack at gmail.com<mailto:skible.openstack at gmail.com>>, Openstack <openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>> Subject: Re: [Openstack] nova-manage service list weirdo ! Ok. No problem! Be careful with time synchronization. It's one of most common problem in distributed environments. I guess your scenario is like below: - Controller Node (Synchronizing from external NTP servers and at the same time it acts as NTP server to compute nodes) - Compute Nodes (Synchronizing from controller node) Regards, JuanFra. 2012/11/30 Skible OpenStack <skible.openstack at gmail.com<mailto:skible.openstack at gmail.com>> Hi Juan, its related to my ntp server, it was not configured properly. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121130/488ca168/attachment.html>