Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 1071 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[7.400] Slow clock in Astaro VM

Monarch
Hi,

I'm, using ASG running inside VMware Server 2.0 upon Windows Server 2008. Hardware as noted below.

Since I did a fresh install (using the 7.400 ISO image) the clock gets out of sync. That means it looses a few minutes per day. That wasn't the case after my last fresh installation (using the 7.304 image).

What can I do to correct this issue?

Regards,
Bastian


This thread was automatically locked due to age.
Parents
  • 0
    Hi,

    I'm, using ASG running inside VMware Server 2.0 upon Windows Server 2008. Hardware as noted below.

    Since I did a fresh install (using the 7.400 ISO image) the clock gets out of sync. That means it looses a few minutes per day. That wasn't the case after my last fresh installation (using the 7.304 image).

    What can I do to correct this issue?

    Regards,
    Bastian


    How long are you running the 7.4 version for?
    Is ntp enabled and allowed to access the internet?(system logs?)
  • 0 in reply to wingman
    V7.4 has been running for over 10 days (uptime). During this time I now corrected the system clock three times manually, it was at least 10 minutes behind the real time.

    NTP is set to the default (pool.ntp.org). The only log entries I could find are the following (excerpt):

    var/log/system/2009/03/system-2009-03-13.log.gz:2009:03:13-04:00:44 astaro1 ntpd[4680]: Deleting interface #15 ipsec0, 91.20.96.10#123, interface stats: received=2, sent=2, dropped=0, active_time=85200 secs
    /var/log/system/2009/03/system-2009-03-14.log.gz:2009:03:14-04:00:44 astaro1 ntpd[4680]: Listening on interface #17 ipsec0, 91.20.113.170#123 Enabled
    /var/log/system/2009/03/system-2009-03-14.log.gz:2009:03:14-04:00:44 astaro1 ntpd[4680]: Deleting interface #16 ipsec0, 91.20.105.233#123, interface stats: received=3, sent=3, dropped=0, active_time=86400 secs
    /var/log/system.log:2009:03:15-04:00:44 astaro1 ntpd[4680]: Listening on interface #18 ipsec0, 91.20.68.89#123 Enabled
    /var/log/system.log:2009:03:15-04:00:44 astaro1 ntpd[4680]: Deleting interface #17 ipsec0, 91.20.113.170#123, interface stats: received=3, sent=3, dropped=0, active_time=86400 secs 


    Regards,
    Bastian
  • 0 in reply to Monarch
    Hi,
    from my understanding you can't run a vm partition as a time reference due to loss/non use of processor cycles. You have to have a real network element as the time reference then refer the vm guest to it. 

    Ian M
  • 0 in reply to RFCat_vk_01
    Ian, I don't understand.  How does one configure the Astaro to obviate this problem?  Or, is this a VMware setting we need to check?

    Thanks - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0 in reply to RFCat_vk_01
    Ian, I don't understand.  How does one configure the Astaro to obviate this problem?  Or, is this a VMware setting we need to check?

    Thanks - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
Cookie Information Banner