Backups fail after upgrade to RC3.1

121 views
Skip to first unread message

Gaijin

unread,
Jan 30, 2016, 3:14:38 AM1/30/16
to Qubes Users
I tried the experimental upgrade from Qubes 3.0 to 3.1 rc2.[1] The
upgrade seems to have been successful but there are a few issues.

Biggest problem is that I cannot backup. When I try to do a full backup
it gets up to about 64% and then I get a dialog, "ERROR: Failed to
perform backup: error in addproc" I have tried backing up several times
with the same error.

Next, if I shutdown the sys-net VM I cannot restart it. I need to do a
full system reboot. Often it takes 2 or 3 reboots to get the system
running again. I can boot all the way to the GUI, but then the screen
freezes and I cannot do anything. I have to manually power off and try
again.

[1] https://www.qubes-os.org/doc/upgrade-to-r3.1/

Alex

unread,
Jan 30, 2016, 4:13:08 AM1/30/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/30/2016 09:14 AM, Gaijin wrote:
> I tried the experimental upgrade from Qubes 3.0 to 3.1 rc2.[1] The
> upgrade seems to have been successful but there are a few issues.
>
> Biggest problem is that I cannot backup. When I try to do a full
> backup it gets up to about 64% and then I get a dialog, "ERROR:
> Failed to perform backup: error in addproc" I have tried backing up
> several times with the same error.
>
The issue happened to me too, the problem may be related (in my case
it was) to invalid symlinks in some VM directory under /var/lib/qubes.

In my case the wrong symlinks were for some .desktop files and for the
icon.png in the root folder of the VM
(/var/lib/qubes/appvms/[vmname]/icon.png). Fixing the links solved the
backup interruption.

- --
Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWrH6bAAoJENNOJZnNP8uD+qcQAJCE6R1RmlhhzmVK3odY7FW7
N3Ev4zwPCv582dYzddcMxbnEtopFIKQM/YiR+pRcZBlGydVAA9cT5k1D2BTKqqJ9
1FgOHR/6KCnqx5nuWZrk5D5LgQ+lMP8DNB/Zc1WCaurCzwLEsL0TVTPgNGOVw4+h
oPp97iPePHwu+G93Xi/6pxUL6Me0KQlipmwcaZ7cv1/j6L4esW5cF9+FuNMBUsFW
d/1tO4GGUtUf1qqRCMjq7OdxNTT0nYSVZLTyqwinuK0YVwZkJjdfj81kif1qoMiy
Oq9UaItpizDC8ncIylwPwFHTGEf9UuZZPjUP9Oh4Y330JN35eDJTZePyJaUDG8Lo
daLlG6uvz3GMX6Xt+Q77roUWynlbrejYKBjeQ67bQvj0arHaeI+RKlJiD2A/3Cmn
GZvRr719pVgY+KQ6Sk829UkmYf7cqE2XZgzbhbwc6KsgylBOOTGHwrKf4iiF5zLJ
VfK2W6UKCleooBVbx6ysvi3J6vyXXMQqaOJz8XvFk4M26F/J1bBfhgNPPgMAtM2V
sr2DAhFfKSafWTZnCCfcFaBoAA/DfIzVOQFkFCTdXvwP6nZ7G9M6Kxr+cmxoZd6z
7q2d1A/xIpXyH3QY0fS+yAWuIM/8aZBkAt6Yq/Vc2PgydQa7pWYOeuM93dcPnz1y
byBqR0mYDlm/0TVi8hk4
=nTq0
-----END PGP SIGNATURE-----

Chris Laprise

unread,
Jan 30, 2016, 11:28:41 AM1/30/16
to Gaijin, Qubes Users
I did the same upgrade, but am not having these issues. There was a
problem with vms not starting during system boot, but that has hopefully
gone away.

Chris

Gaijin

unread,
Jan 30, 2016, 9:36:28 PM1/30/16
to Qubes Users
I looked up the broken symlinks in dom0:
find ./ -type l -exec file {} \; |grep broken
There were a bunch in there from old VMs that I had deleted, but none
for the /var/lib/qubes/appvms/[vmname]/icon.png that you mentioned.
Fixing those seems to have fixed the backup problems. I can now do a
full backup. Thanks.

I still can't start the sys-net VM if I shut it down. I get, "Error
starting VM sys-net: cannot execute qr-exec daemon!

Marek Marczykowski-Górecki

unread,
Jan 31, 2016, 5:53:45 PM1/31/16
to Gaijin, Qubes Users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Jan 31, 2016 at 02:36:26AM +0000, Gaijin wrote:
> On 2016-01-30 09:13, Alex wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA256
> >
> >On 01/30/2016 09:14 AM, Gaijin wrote:
> >>I tried the experimental upgrade from Qubes 3.0 to 3.1 rc2.[1] The
> >>upgrade seems to have been successful but there are a few issues.
> >>
> >>Biggest problem is that I cannot backup. When I try to do a full
> >>backup it gets up to about 64% and then I get a dialog, "ERROR:
> >>Failed to perform backup: error in addproc" I have tried backing up
> >>several times with the same error.
> >>
> >The issue happened to me too, the problem may be related (in my case
> >it was) to invalid symlinks in some VM directory under /var/lib/qubes.
> >
> >In my case the wrong symlinks were for some .desktop files and for the
> >icon.png in the root folder of the VM
> >(/var/lib/qubes/appvms/[vmname]/icon.png). Fixing the links solved the
> >backup interruption.
> >
>
> I looked up the broken symlinks in dom0:
> find ./ -type l -exec file {} \; |grep broken
> There were a bunch in there from old VMs that I had deleted, but none for
> the /var/lib/qubes/appvms/[vmname]/icon.png that you mentioned. Fixing those
> seems to have fixed the backup problems. I can now do a full backup. Thanks.
>
> I still can't start the sys-net VM if I shut it down. I get, "Error starting
> VM sys-net: cannot execute qr-exec daemon!

Take a look here:
https://github.com/QubesOS/qubes-issues/issues/1449

In the last comment there is some workaround for it.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWrpBwAAoJENuP0xzK19csvOwH/3ZhGJ63BC2UEdeJBWX/aQkC
XcpNvSfvNKjIjW9voALwp6A8+ULznEtEIiUVVClLpkRfJTm+N8M/oVR2DwQO/Fhe
+V62YW6QJgU9p52hkuJ2Z8It47AHE/mfGjjRrbDwuO3UjFexyqCKyDOnTCr4uBW6
nEBy1Zu/bZGaAtqZdCEzmw0ZI2P+UuhB5Y4xa7d0I0sDwI/mZ7NagbVGm/wCxqd1
9ALIWeLZzsfHZR+cbuNSdmzpvTDXnFL4t0IRlFgpTPrIMNyz0bgXgz0iJOXSaezK
08Tyf3zuS8d65BE4VQ693m4orR7ggqjiCMnRWQbpeTfHsI4oDexddvIc0JJXbrg=
=yOaG
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages