A problem with update

83 views
Skip to first unread message

admi...@gmail.com

unread,
Jul 28, 2016, 1:31:11 AM7/28/16
to qubes-users
Hi,
I'm trying to update qubes but there still show that there is no updates (for few moths).
I thought that was true until I tried to download update for xen.

Some commands:
http://pastebin.com/Q7nhfZnX
Linux dom0 4.1.13-9.pvops.qubes.x86_64 #1 SMP Thu Feb 11 15:46:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Can somebody tell me whats going on?

Regards
Adrian

admi...@gmail.com

unread,
Jul 28, 2016, 3:42:31 AM7/28/16
to qubes-users, admi...@gmail.com
Apart from the dom0 update, there is a something nasty in quebes-os debian jessie repository (debian-8, whonix-ws and gw):

W: Failed to fetch http://deb.qubes-os.org/r3.1/vm/dists/jessie/main/binary-amd64/Packages Hash Sum mismatch

Can anyone confirm the issue, or is it only on my computer.

Regards

donoban

unread,
Jul 28, 2016, 3:44:50 AM7/28/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Same problem here.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXmbfuAAoJEBQTENjj7Qily34P/jgHHBl5be2dE/WBeS5j0aV4
2uH5qlW/ZnYdl76yZch7+YVzyDTsoY7MfAlWpDOp2Fr/2ABEl8fRLXf68+n37Y/8
LQCP1MliHsP53Gk7cR5xTzSNtsStBbJISRvn95bZuiEU0D9ifMB2JpjoqGskSwL/
4rBy5TL107V6YRL7b5swOOnh8zSmbUSkeQFVXBuAfOcT84uF1xnJxoE9b/qj7rRn
6rpEmHuxSNTY2p9DJsb1ooUav6rLr/KG3dfOmSshCjROIk4tGeIMyG8YyAfRnd01
DtDcqtlYQT9coYiP3rOj8M0P7a+KPEFPHoHut4gMra1Jrvcxr1D1F58FUPEwU4KW
BfeqDqukL3HQi7OmhjOoY+eRpS3akcVieXAKtgGnYDPsWR+u2fkIEO3AE1lP1o6C
CQ+I634DIvUsvyM14ENJuGOcCQOK0XOLk+BM8AFFhHZoUMwWsSEkZRxU5XI6hgEa
7v9dxsHZIQxAXDwrAL0rOU5JDC1MV0Reu5m2005sdNDTwBUjP1uATKsKynrpR+XT
S1IX3/spE9aMvrYA+3TMAeFfJpGUcUHimXICZUAIF84mlv+Ib72r+X8Kg1fhRIDI
CT6Vcss6kGV4qdNZ9OldHyf7Hevxh63s0NP8B4YJBdPTiUj+PfPSzDzqyXFuD5hd
MAi5DFdcpR4+6mtvPyAK
=/OsC
-----END PGP SIGNATURE-----

Andrew David Wong

unread,
Jul 28, 2016, 4:41:37 AM7/28/16
to admi...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Which template is your sys-firewall based on?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXmcUyAAoJENtN07w5UDAwSH8QAM6+YPcubOYV6rhNN97xqQkT
p8pXhHxH2RD6OdPzlwqImynWgLfcvL+S6GTE8NeYznfDt78lSxDRRBnL7pli3Fcg
UayFUbJBP+uqSu7by1SqIRDCkGWuLv+kIgdpcbmWgypopfH8bwRSW5DIDxyQz4E1
dSMVa/I5l0ovbvGZGtn2TQiIUiN6joT3zmU02SCQusE2vTq208JDF90P7t28on38
0Q4Z7N3Owi53JwXF31VUp1aM8IxdeWQHdZtjzSCTiUbkL9yTWmL8aZedC4nazORg
xAhNngGtTVYbeHVfEaewmDsewyMXSeOxu1X4XvbVLYTOQzpU387BO7lJgVdcZd5R
vzB/z2iwyjyJqE5/QFmyoIRhaSsESw2QrAtf6v/dllz0q1U++ncOVc/yAbiXB+jW
JQ6GS5CJlfBvKuQd2G4mKoITsud3XAgMNXQ70m1CKlJ6QWW0kb9G+ciqVlcn98yt
wRMpVVk46LzyaXLB7ZwRUquOaHE5lnPIbgbf0T9bfISV35X0VweoF5tc8xNUm5+M
StW1E2gp3bbuncCprYXv+CcW49oZXKOkfEckm47ZuD4COhqA9TO8RajJ9GMN0jWo
Qq2DNjSJvQhoz3byBo2i24ZC/Fy6LD56J0hgEwW4OjIv9JsE0KxoXpx0uy0Rk2C2
YJ7xYTor0ogVHPTs1tYS
=hGaC
-----END PGP SIGNATURE-----

admi...@gmail.com

unread,
Jul 28, 2016, 5:06:03 AM7/28/16
to qubes-users, admi...@gmail.com
My sys-firewall and sys-net is based on fedora-23.
sys-firewall's netVM is sys-net and sys-net is connect to the internet (there isn't any problem with internet on VM).

Regards

Marek Marczykowski-Górecki

unread,
Jul 28, 2016, 5:13:35 AM7/28/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Jul 28, 2016 at 09:44:46AM +0200, donoban wrote:
>
> On 28/07/16 09:42, admi...@gmail.com wrote:
> > Apart from the dom0 update, there is a something nasty in quebes-os
> > debian jessie repository (debian-8, whonix-ws and gw):
> >
> > W: Failed to fetch
> > http://deb.qubes-os.org/r3.1/vm/dists/jessie/main/binary-amd64/Package
> s
> > Hash Sum mismatch
> >
> > Can anyone confirm the issue, or is it only on my computer.
> >
> > Regards
> >
>
> Same problem here.

Should be ok now.

- --
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

iQEcBAEBCAAGBQJXmcy5AAoJENuP0xzK19cs/p8IAJTBqcnhq+UIG50v7rXmzEfi
5s9MSAuO7tVpaMkS9r4rxORzxsUipONoQjufmjhdgzhVRAVMMcfH4MUXwINO4CWY
drc4CFBLhkbltgx29CcBtIxiOEvt5MtmKvW8dDmV35o6EsT1QLwQWGNMDAE+zWXK
UicN8HtAhBhw5TUmdvHnuNWiGW2Wi2Kq9QrQIVTqimjE+FdEOUjrubkDeGXpt8/d
48S9fEhLoEtK4anEQkTAmEVx79k/XHWbe3z7Q4RR2Ta+shPaDC/Wd/OZvKcpswDl
jVz3vSdEXWVg6aK3455QfU+kXXtc2vRsutx+LXNH00d2bMWbZUQESp2iCec3798=
=1Sxr
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,
Jul 28, 2016, 5:25:01 AM7/28/16
to admi...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think --debuglevel option is not supported - this is why you've got
that help message instead. Try `qubes-dom0-update --clean` to remove old
metadata first.

- --
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

iQEcBAEBCAAGBQJXmc9nAAoJENuP0xzK19csDp8H/AxRPuOImKt7Oih1iKwf0kJ+
c+qEiY/sguQbqQC8oOXUrulEHZ4aT+9d1sUdAcmUVjQNt7ewo3ksikejfLTQ8uA1
+C7Q63/7sAJUZU+/0x0DCxjC5FMtz+XNwvdAWC8jXU5NNFGjOzw0qkUZUTZhbg0g
injHV5nMVag+Hw4h4I2LOsRhqMVyk2fCeSRQPylB7YB6IfRwHiU/zXcuhq8Eziy/
DqaLztWediTjigsEsMHY+cX06osZdwM8WCxM96lnnQIFA87vSKfPYMV+V3JG9dHs
osVOZYQxopTPy6teulmAOl3yWduJFuXD/mIS8zGlLSUyvFlqH4pGD4APPVBCP9U=
=mxAU
-----END PGP SIGNATURE-----

donoban

unread,
Jul 28, 2016, 5:26:56 AM7/28/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 28/07/16 11:13, Marek Marczykowski-Górecki wrote:
> Should be ok now.
>

Perfect, thanks Marek.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXmc/cAAoJEBQTENjj7Qil27EP/j2j0vZdIin0lw1KRQxQz5CO
h9QXaV0AIenwJts/L5f6LevH71uGZI0LlBclgJXGjq2jNluE5MBOWMCX5y1IUDyV
rylnlCNHhlZeshUzoLYJ94RlQ8uAAXnUaovtVzC1TsO4Lr7NTuv4sTIpY5fIN4ir
WyI+85NnKkfzupQ2HdgrH8yB5CzjMxeGvR7eggFrm36oN9VfGrT4XOAQAXydmKHS
iHpiOH/3gGJPCmtNZizR/k/y+uGVlZapmxQmH67YezjPKyLKlbQLZZOTJII5Hplf
mnqkppcbKXhkFfMf2iJBr5butdUc3PuWptvCJIoIyKKqqvjaNIB9bEYrscwELdVG
5IFupzYkq4T2WH0KyZU8rGQzhgzoo8sP5Ir0IoTO7iktTYYgdXM7a4hiQzDs7/CH
Jj5j/P2CKwebnlbVryhS4MVYJK6HWWwF+NQSV7k+y+XAtpyunXe2XfvtG02r2uPG
pgnfbHStWWIY742JR4FPcrimOB7lcUb38GlpW+BeeeqwA1g6WYuFXCysG5UtLHLc
VtijeHevNG4qiWlRpUoXhHDumzh3M4Nvr4VreGUHq2rD9dfgq04JLqTFKxqXzsXl
ER0ijUar3ilL9EFE4GzdiUF0qvuQ/hgK2rSKKSIyVRlwuJ//jBMYthBQMo7aGWz8
hJbwPFJG62EerSI4bgxF
=+2n5
-----END PGP SIGNATURE-----

admi...@gmail.com

unread,
Jul 28, 2016, 7:22:20 AM7/28/16
to qubes-users, admi...@gmail.com
Ok, maybe, but...
I've got xen-4.6.0-13.fc20.x86_64 (rpm -qa | grep xen) instead of the new version mentioned in *-devel forum:
http://yum.qubes-os.org/r3.1/current/dom0/fc20/rpm/xen-4.6.1-20.fc20.x86_64.rpm

and qubes-dom0-update report always "No new updates available"
I've tried run with "--clean" and it still don't work.

Maybe I executed something by accident which has deleted/overwrote an important file?

Have you any idea? Or what should I check?

admi...@gmail.com

unread,
Jul 28, 2016, 9:03:28 AM7/28/16
to qubes-users, admi...@gmail.com
Okey,
I did step by step (I hope every needed line) in quebes-dom0-update and on sys-firewall.

Finally I runned yum and... some packages are checked and sys-firewall lagged for a while. After all it looks like that:

http://pastebin.com/0SnJZh7M

It seems like qubes-download-dom0-updates.sh doesn't supports yum crash.
But why it is always crashing? Any idea?

Regards

admi...@gmail.com

unread,
Jul 28, 2016, 9:41:57 AM7/28/16
to qubes-users, admi...@gmail.com
[Solved]

Yum crashed because there's no more RAM. Include sys-firewall in memory balancing solved this problem.

However "No updates available" is bit confusing.

Regards

M. Vefa Bicakci

unread,
Jul 28, 2016, 10:56:41 PM7/28/16
to Marek Marczykowski-Górecki, Andrew David Wong, admi...@gmail.com, qubes-users
On 07/28/2016 05:24 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Jul 27, 2016 at 10:31:10PM -0700, admi...@gmail.com wrote:
>> Hi,
>> I'm trying to update qubes but there still show that there is no updates (for few moths).
>> I thought that was true until I tried to download update for xen.
>
>> Some commands:
>> http://pastebin.com/Q7nhfZnX
>> Linux dom0 4.1.13-9.pvops.qubes.x86_64 #1 SMP Thu Feb 11 15:46:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
>> Can somebody tell me whats going on?
>
> I think --debuglevel option is not supported - this is why you've got
> that help message instead. Try `qubes-dom0-update --clean` to remove old
> metadata first.

Hello Marek and Andrew,

On a related note, the script at "/usr/lib/qubes/qubes-download-dom0-updates.sh" may have
a minor bug related to the removal of the cache files when the --clean option is passed
to the qubes-dom0-update script in dom0.

When I run "sudo qubes-dom0-update --clean", as seen below my signature, "rm" outputs an
error mentioning that it cannot remove a directory. Even though "--clean" was used, the
timestamp for the metadata expiration check indicates that dnf is using metadata from
almost 12 minutes ago. This indicates an issue with the clean-up of the dnf/yum cache.

When I "rm -rf" all the offending directory on sys-net using the command listed below,
then "--clean" works as expected as can be seen below, where the metadata expiration
check indicates only a 23 second delta, which is a more plausible value when using "--clean".

All this to say, would it be possible to make the "qubes-download-dom0-updates.sh" script use
"rm -rf" rather than "rm -f" on the paths related to the dnf/yum cache for dom0 updates?

To be specific, I mean replacing the "rm -f" instances with "rm -rf" on the following lines
in /usr/lib/qubes/qubes-download-dom0-updates.sh in the Qubes OS VM templates:

if [ "$CLEAN" = "1" ]; then
$YUM $OPTS clean all
rm -f $DOM0_UPDATES_DIR/packages/*
rm -f $DOM0_UPDATES_DIR/var/cache/yum/*
fi

I believe this may be related to some of the "updates missing" issues that Qubes OS users
have reported after the release of the corrections for Qubes Security Bulletin #24.

Thank you,

Vefa

=== 8< ===

[user@dom0 ~]$ sudo qubes-dom0-update --clean
Using sys-net as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-net'...
30 files removed
rm: cannot remove '/var/lib/qubes/dom0-updates/var/cache/yum/x86_64': Is a directory
Checking for dom0 updates...
Last metadata expiration check: 0:11:54 ago on Thu Jul 28 22:24:19 2016.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
...

[user@dom0 ~]$ qvm-run -aqp sys-net 'rm -rf /var/lib/qubes/dom0-updates/var/cache/yum/x86_64'

[user@dom0 ~]$ sudo qubes-dom0-update --clean
Using sys-net as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-net'...
30 files removed
Checking for dom0 updates...
Last metadata expiration check: 0:00:23 ago on Thu Jul 28 22:39:13 2016.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
...

=== >8 ===

Marek Marczykowski-Górecki

unread,
Jul 29, 2016, 3:31:38 AM7/29/16
to M. Vefa Bicakci, Andrew David Wong, admi...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, this is already fixed in qubes-core-vm 3.2.9:
https://github.com/marmarek/qubes-core-agent-linux/commit/40d5f85b361d6f2ca889f7a9f1230baca826e1bf

- --
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

iQEcBAEBCAAGBQJXmwZVAAoJENuP0xzK19csgF8H/iuY7YLn6aF6e4nDCckzKjUK
b2cKuhJOXt3vYulv5fR2zSQJMQAhdorC7iHXhsBQKvolNxEgqGa0Mt/B+IUixIfT
4A7pZHCR/aO+exXkamzGkvB8ShEnBLGIEKXSXUTri2KMgJzubgjH34VgjUAIgsQa
iFKE1Tj6NTYlIaGPjKoVccnP+3/HSGrsDDmNoNZ3Ru4o8OSP9NCBlCMvOXIDOWr6
VDr8UKfsrU9oEQADa/dOK9TlbqMt8MaeHPrp8sDB4IUD0hQJowyjgazvUxXVixqc
BYMTrhVY5hmg10z86JbEL3T+kjZF3XM6zjwc2exqtablytN2gc1J+WDARVXuu8Q=
=MGXn
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages