New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fedora 28 VMs not updating time #3983

Open
dmoerner opened this Issue Jun 12, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@dmoerner

Fedora 28 templates and Qubes 4.0.

qvm-sync-clock is updating dom0 to the wrong time because sys-net has the wrong time because systemd-timesyncd isn't starting with error status=238/STATE_DIRECTORY.

Fedora issue: https://bugzilla.redhat.com/show_bug.cgi?id=1559286.
Upstream report: systemd/systemd#7659

Manually changing /var/lib/private to 700, as mentioned in the above reports, fixed the problem for me. However, upstream commit systemd/systemd@ebe6ff6 which is merged in systemd in Fedora 28, which was supposed to fix this problem, seems not to have fixed it. Perhaps it needed to be combined with changing the permission on /var/lib/private in the Fedora package.

@micah

This comment has been minimized.

Show comment
Hide comment
@micah

micah Jul 3, 2018

This happens to me on every boot.

In order to fix it, I need to launch a terminal in sys-net and chmod 0700 /var/lib/private; systemctl start systemd-timesyncd.service and then go to dom0 and do sudo qvm-sync-clock in order for things to be right.

micah commented Jul 3, 2018

This happens to me on every boot.

In order to fix it, I need to launch a terminal in sys-net and chmod 0700 /var/lib/private; systemctl start systemd-timesyncd.service and then go to dom0 and do sudo qvm-sync-clock in order for things to be right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment