Skip to content
This repository has been archived by the owner on Feb 2, 2022. It is now read-only.

ntpd not started in cspvm by default #35

Closed
rommelfs opened this issue Jun 26, 2019 · 8 comments
Closed

ntpd not started in cspvm by default #35

rommelfs opened this issue Jun 26, 2019 · 8 comments
Labels
bug Something isn't working

Comments

@rommelfs
Copy link

Time will drift easily on VM installation

@thanosa75
Copy link
Contributor

Alpine uses chrony (https://chrony.tuxfamily.org) for the NTP service. Please confirm that you do not see this process running, by doing:

ps -ef |grep chronyd

Thanks

@rommelfs
Copy link
Author

I confirm I see this process.

I also confirm a time drift of 9 days.

I was able to fix it by starting /etc/init.d/ntpd

@thanosa75
Copy link
Contributor

thanosa75 commented Jun 26, 2019 via email

@thanosa75
Copy link
Contributor

To further troubleshoot your VM with chrony you could use (I assume ntpd will be stopped and chronyd restarted):

chronyc activity

we get:

4 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address

chronyc sourcestats

Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
router-vzb.servme.network   7   4   34m     -0.011      0.039   -221us  9172ns
ntp-ext.cosng.net           7   5  103m     +0.115      0.238   +751us   225us
ntp1.kolatelecom.ru        20  13  141m     +1.708      0.322  +9682us   870us
mail.fangfufu.co.uk         6   3   43m     -0.006      0.221   -191us    59us

@thanosa75
Copy link
Contributor

Hello @rommelfs any news?

@rommelfs
Copy link
Author

What news do you expect? chronyc is running, ntpd is running, still time drifts.
I will only be worried about this once this instance is registered at the central node (which hasn't happened within the last two weeks). So this is for your information if you like to dig into it. If not, fine for me.

@thanosa75
Copy link
Contributor

Hello @rommelfs

Please do the following:
a) stop ntpd and reboot the instance.
b) execute the following: cronyc sourcestats, chronyc activity and provide us with the output.

Thanks

@thanosa75 thanosa75 added the bug Something isn't working label Jun 27, 2019
@thanosa75
Copy link
Contributor

Closed as no response received

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants