[ISSUE] My system clock is four minutes behind. How do I fix it?

[ISSUE] My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

New issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.19_1 x86_64 GenuineIntel uptodate hold rFF

### Package(s) Affected

openntpd

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

When i login to my machine, it should report the correct time.log in

### Actual behaviour

It's 4 minutes behind. For example, if right now it is 14:20, my machine will show 14:16. I should manually restart openntpd service to fix this problem.

I'm using openntpd as "Network Time Protocol" implementation, but even switching to chrony has the same issue.

### Steps to reproduce

Just install openntpd and enable it's service.its

Re: My system clock is four minutes behind. How do I fix it?

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 247 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228359604

Comment:
Did you try to manually update it via https://wiki.archlinux.org/title/OpenNTPD#Error_adjusting_time ?

Re: My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228368301

Comment:
Why should i update it manually every time I restart my computer?

No, it's not working:

```
↳ sudo ntpd -d
Password:
ntpd: ntpd already running
```

As I said before, I can fix the issue by restarting the `openntpd` service, but I don't want to do that. It should work without manual intervention!

Re: My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228368301

Comment:
Why should I update it manually every time I restart my computer?

No, it's not working:

```
↳ sudo ntpd -d
Password:
ntpd: ntpd already running
```

As I said before, I can fix the issue by restarting the `openntpd` service, but I don't want to do that. It should work without manual intervention!

Re: My system clock is four minutes behind. How do I fix it?

[Anachron]

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228377328

Comment:
So anything in the system log showing whats wrong with it? Or does it even believe it's uptodate?

Also would be good to disable the service and run it manually and increase verbosity until its figured out.

Re: My system clock is four minutes behind. How do I fix it?

[sgn]

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228599273

Comment:
IIUC, `ntpd` tries to avoid drastically drift in time, I don't really know about `openntpd` but for chrony I think there're slew mode and step mode. Sometime your local clock's frequency isn't stable, too.

Re: My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228690523

Comment:
I figured out how to solve it without manual intervention. It's not an ideal solution, but... it's working for me.

Just add this line to the end of `visudo`:
`linarcx ALL=(ALL) NOPASSWD: /usr/bin/sv`

And put this line to .xinitrc:
`sudo sv restart openntpd`

Re: [ISSUE] [CLOSED] My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Closed issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.19_1 x86_64 GenuineIntel uptodate hold rFF

### Package(s) Affected

openntpd

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

When i login to my machine, it should report the correct time.log in

### Actual behaviour

It's 4 minutes behind. For example, if right now it is 14:20, my machine will show 14:16. I should manually restart openntpd service to fix this problem.

I'm using openntpd as "Network Time Protocol" implementation, but even switching to chrony has the same issue.

### Steps to reproduce

Just install openntpd and enable it's service.its

Re: My system clock is four minutes behind. How do I fix it?

[LinArcX]

[-- Attachment #1: Type: text/plain, Size: 510 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228690523

Comment:
I figured out how to solve it without manual intervention. It's not an ideal solution, but... it's working for me.

Just add this line to the end of `visudo`:
`linarcx ALL=(ALL) NOPASSWD: /usr/bin/sv`

And put this line to .xinitrc:
`sudo sv restart openntpd`

Edit: but if anyone knows what's wrong with openntpd, and has better ideas, please let me know.

Re: My system clock is four minutes behind. How do I fix it?

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228728228

Comment:
That `NOPASSWD` rule basically gives you root right:

```
$ cat ~/sv/dwm/check
#!/bin/sh
id >&2
exit 0
$ sudo sv check ~/sv/dwm/
uid=0(root) gid=0(root) groups=0(root)
ok: run: /home/duncan/sv/dwm/: (pid 7389) 1133558s
```

If restarting openntpd later works, then there is probably an issue with the inital run, check the logs.

Re: My system clock is four minutes behind. How do I fix it?

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/38918#issuecomment-1228728228

Comment:
That `NOPASSWD` rule basically gives you root right:

```
$ cat ~/sv/dwm/check
#!/bin/sh
id >&2
exit 0
$ sudo sv check ~/sv/dwm/
uid=0(root) gid=0(root) groups=0(root)
ok: run: /home/duncan/sv/dwm/: (pid 7389) 1133558s
```

If restarting openntpd later works, then there is probably an issue with the inital run too far out of sync or constraints failing, check the logs.