Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793 )

[tnt_b...@keemail.me]

well i have already opened this topic in github before long time , but now andrewdavidwong recommended me to send this topic to users section:-

https://github.com/QubesOS/qubes-issues/issues/1745#event-665419288

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I've experienced this too. If I just wait about 10 seconds, then try
to start sys-net again, it always works.

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

iQIcBAEBCgAGBQJXTr67AAoJENtN07w5UDAwAMgQALQdF58VO2/RW520IgCx12jc
Jc506wDrBXlMHU3Qts3N3eQmKeNMjdJrLLP/ZONNC1az1sI0ssrIVjkT5XO8h2/P
b/lY67Qa+9WMQpf8tj0faz6tsnh/tBuUyImEKkpo/389GtAGJAtLrR25cPjDCNXQ
/KTFn6/B4VJxwHFxjJjk2yAxtM4VyO5cTOGtkcrJK07SrC7U9722KDOOhLKLv6Ul
OtaRR0gA7UG6PghvV2ilUOYEshzEFQXoaeaaL3uHcNVuIFW9eb42rYSrStDPF+tg
pox4FXiqG/UZfc9dYZWESYgGItsEwCxHiXZH0zruEaaK8Euea/yNRDHcKh5mwDzs
82O66WmnGvjP2q1YtHlJD1p0TEJma8M0uviLY+sjyi9S6psRBpnX4dAzW5CtKcpw
CsEj+wcQYlXWJ+LmAueDICC2NF2zsi9KtGXFRFHBllMFtTYklUGNYm08MUulzdvE
G6ZCkXkdJ5kv94d8krax3iQalYxH1dhBoXUhVsqXccVCNUHbbaS9S3G/Lf2g9CBf
gCk+dtCMAOexRiK71bZlpSyIQKrYGYGza6vYu6UEUml2r1fRoa8pLI/KmeJicKhd
lKcgcjy75eHJwGvylMnoTZ8h8oLm7fvbe6zJvdjBdTtT3qTKHkFLgN3lUahSFqKp
fe0ZvgThe7OeqrSSRM/+
=hin+
-----END PGP SIGNATURE-----

[tnt_b...@keemail.me]

thats correct it will work , but as u know we should find out the correct fixation to this problem.


1. Jun 2016 10:53 by a...@qubes-os.org:

[raah...@gmail.com]

Happens to me too. It can happen when restarting it too quick I guess because it takes a couple secs for it to fully close the old instance. I guess the faster your computer the less it would happen. For example same thing happens to me with sys-firewall if I start it too quick after the sys-net, basically before the sys-net has internet connection, which will cause an error as well.

To avoid this now, instaed of manually starting the sysnet or proxies, i just load the appvm i want to use. So this way the sys-net and sys-firewall and proxy is automatically started at the proper intervals one after the other avoiding me accidentally starting one of them too quick. But you still have to give it acouple secs after first closing the sys-net .