/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

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

Closed
TNTBOMBOM opened this Issue Feb 12, 2016 · 5 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.1 updates
3 participants
@TNTBOMBOM @andrewdavidwong @marmarek
@TNTBOMBOM

TNTBOMBOM commented Feb 12, 2016

qubes 3.1 , sys-net fedora-23

message/notification pupped up while i wanted to start new appVM (just clicked on the start button then the message appeared)

Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793
). Terminate it manually and retry. If that isn't QubesDB process, remove the pidfile: /var/run/qubes/qubesdb.sys-net.pid

image (firstly the message appeared in the notification section down right corner , then i shutdowned firewall then sysnet):-

firewallprob
@TNTBOMBOM

This comment has been minimized.

Show comment
Hide comment
@TNTBOMBOM

TNTBOMBOM Feb 23, 2016

happened again with different PID number:-

Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1800
). Terminate it manually and retry. If that isn't QubesDB process, remove the pidfile: /var/run/qubes/qubesdb.sys-net.pid

TNTBOMBOM commented Feb 23, 2016

happened again with different PID number:-

Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1800
). Terminate it manually and retry. If that isn't QubesDB process, remove the pidfile: /var/run/qubes/qubesdb.sys-net.pid

@andrewdavidwong andrewdavidwong added the question label Apr 6, 2016

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 19, 2016

Member

This question is too localized for qubes-issues. Please consider posting this to the qubes-users mailing list instead. (You can read more about our mailing lists here.)

qubes-users is intended for these sorts of questions and receives much more traffic, which means that your question is more likely to receive a response there.
Member

andrewdavidwong commented May 19, 2016

This question is too localized for qubes-issues. Please consider posting this to the qubes-users mailing list instead. (You can read more about our mailing lists here.)

qubes-users is intended for these sorts of questions and receives much more traffic, which means that your question is more likely to receive a response there.

@andrewdavidwong andrewdavidwong closed this May 19, 2016

@marmarek marmarek added bug C: core P: minor and removed question labels Jun 4, 2016

@marmarek marmarek added this to the Release 3.1 updates milestone Jun 4, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jun 4, 2016

Member

The message was to explain "rare problem", but apparently it isn't such rare and deserve a proper fix.
Member

marmarek commented Jun 4, 2016

The message was to explain "rare problem", but apparently it isn't such rare and deserve a proper fix.

@marmarek marmarek reopened this Jun 4, 2016

@marmarek marmarek closed this in marmarek/old-qubes-core-admin@2265fd3 Jun 7, 2016

@marmarek marmarek referenced this issue Jun 20, 2016

Closed

Wifi networking NetVM crashes with poor UX #1595

marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Jun 25, 2016

@marmarek
core: start qubesdb as normal user, even when VM is started by root 
On VM start, old qubesdb-daemon is terminated (if still running). In
practice it happen only at VM startart (shutdown and quickly start
again). But in that case, if the VM was started by root, such operation
would fail.
So when VM is started by root, make sure that qubesdb-daemon will be
running as normal user (the first user in group 'qubes' - there should
be only one).

Fixes QubesOS/qubes-issues#1745

(cherry picked from commit 2265fd3)
(adjusted for missing qrexec counterpart with 'grp' import)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
e3996c2
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jun 25, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-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 Jun 25, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-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 Jun 25, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 25, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-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 Jul 25, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-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 Jul 25, 2016

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Sep 8, 2016

@marmarek
qubes/vm: start VM daemons as normal user 
This is migration of core2 commits:

commit d0ba43f
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Mon Jun 6 02:21:08 2016 +0200

    core: start guid as normal user even when VM started by root

    Another attempt to avoid permissions-related problems...

    QubesOS/qubes-issues#1768

commit 89d002a
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Mon Jun 6 02:19:51 2016 +0200

    core: use runuser instead of sudo for switching root->user

    There are problems with using sudo in early system startup
    (systemd-logind not running yet, pam_systemd timeouts). Since we don't
    need full session here, runuser is good enough (even better: faster).

commit 2265fd3
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Sat Jun 4 17:42:24 2016 +0200

    core: start qubesdb as normal user, even when VM is started by root

    On VM start, old qubesdb-daemon is terminated (if still running). In
    practice it happen only at VM startart (shutdown and quickly start
    again). But in that case, if the VM was started by root, such operation
    would fail.
    So when VM is started by root, make sure that qubesdb-daemon will be
    running as normal user (the first user in group 'qubes' - there should
    be only one).

    Fixes QubesOS/qubes-issues#1745
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
c534b68

@qubenix qubenix referenced this issue Oct 8, 2016

Closed

ERROR: Failed to kill old QubesDB instance #2369

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