/qubes-issues

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

Network problems from inaccurate time after wake from sleep - R3.1rc3 #1795

Closed
tasket opened this Issue Feb 28, 2016 · 7 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.0 updates
2 participants
@tasket @marmarek
@tasket

tasket commented Feb 28, 2016

User space programs like openvpn and some web sites are experiencing problems because VM date/time is not updated for a very long period after wake from sleep. In the case of openvpn, downstream VMs must wait the entire time (60-120 sec) until a timeout occurs before communication can resume. Normally, a timeout would occur instantly after wake and communication would resume a few seconds later.

This started happening right after I updated to rc3.

I ran some tests and found out that domUs will not get time sync'd for 10 minutes or more after waking from sleep!
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2016

Member

I think this is already fixed here: QubesOS/qubes-core-admin-linux@ee3950a
The update just went into stable repository, so you can simply run qubes-dom0-update.
Member

marmarek commented Feb 28, 2016

I think this is already fixed here: QubesOS/qubes-core-admin-linux@ee3950a
The update just went into stable repository, so you can simply run qubes-dom0-update.

@marmarek marmarek closed this Feb 28, 2016

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Feb 28, 2016

VMs are still not getting timely time syncs after updating and rebooting. This time it took 6 min. after waking from sleep. The VMs are all using a debian 8 template.

tasket commented Feb 28, 2016

VMs are still not getting timely time syncs after updating and rebooting. This time it took 6 min. after waking from sleep. The VMs are all using a debian 8 template.

@marmarek marmarek reopened this Feb 28, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 28, 2016

Member

Do you have proper time in dom0 after resume? Check logs on qubes-suspend service in dom0: sudo journalctl -u qubes-suspend.service, you should see 01qubes-sync-vms-clock script running and listing your VMs - check if and when the affected VMs were listed.
Member

marmarek commented Feb 28, 2016

Do you have proper time in dom0 after resume? Check logs on qubes-suspend service in dom0: sudo journalctl -u qubes-suspend.service, you should see 01qubes-sync-vms-clock script running and listing your VMs - check if and when the affected VMs were listed.
@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Feb 29, 2016

The dom0 time is correct right after waking. When I grep the journalctl output, the last time 01qubes-sync-vms-clock appears is around 13:00 today (several suspend cycles since then). I think this was right around the time I updated dom0.

Here are the log lines from the last time I woke the system:

Feb 28 21:09:25 dom0 systemd[1]: Unit qubes-suspend.service is not needed anymore. Stopping.
Feb 28 21:09:25 dom0 systemd[1]: Stopping Qubes suspend hooks...
Feb 28 21:09:25 dom0 51qubes-suspend-netvm[4062]: method return sender=:1.5 -> dest=:1.104 reply_serial=2
Feb 28 21:09:26 dom0 systemd[1]: Stopped Qubes suspend hooks.

tasket commented Feb 29, 2016

The dom0 time is correct right after waking. When I grep the journalctl output, the last time 01qubes-sync-vms-clock appears is around 13:00 today (several suspend cycles since then). I think this was right around the time I updated dom0.

Here are the log lines from the last time I woke the system:

Feb 28 21:09:25 dom0 systemd[1]: Unit qubes-suspend.service is not needed anymore. Stopping.
Feb 28 21:09:25 dom0 systemd[1]: Stopping Qubes suspend hooks...
Feb 28 21:09:25 dom0 51qubes-suspend-netvm[4062]: method return sender=:1.5 -> dest=:1.104 reply_serial=2
Feb 28 21:09:26 dom0 systemd[1]: Stopped Qubes suspend hooks.

@marmarek marmarek closed this in marmarek/qubes-core-admin-linux@b19ba4d Feb 29, 2016

@marmarek marmarek added bug C: core P: minor labels Mar 6, 2016

@marmarek marmarek added this to the Release 3.0 updates milestone Mar 6, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 7, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.9-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update
Member

marmarek commented Mar 7, 2016

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.9-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek marmarek added the r3.1-dom0-cur-test label Mar 7, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 13, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.9-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update
Member

marmarek commented Mar 13, 2016

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.1.9-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@marmarek marmarek added r3.1-dom0-stable and removed r3.1-dom0-cur-test labels Mar 13, 2016

marmarek added a commit to QubesOS/qubes-core-admin-linux that referenced this issue May 1, 2016

@marmarek
pm-utils: do not leave background tasks - will be killed by systemd 
qvm-sync-clock running in background is killed as soon as
qubes-suspend.service is terminated.
Additionally restore --verbose option, which was the case (implicitly)
in previous qvm-run based code.

Fixes QubesOS/qubes-issues#1795

(cherry picked from commit b19ba4d)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
35a7d5e
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 2, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.20-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update
Member

marmarek commented May 2, 2016

Automated announcement from builder-github

The package qubes-core-dom0-linux-3.0.20-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek marmarek added the r3.0-dom0-testing label May 2, 2016

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