debian 10 VM: "Unable to init server: Could not connect: Connection refused."

38 views
Skip to first unread message

qubes...@riseup.net

unread,
Feb 20, 2021, 9:27:40 AM2/20/21
to qubes...@googlegroups.com
Hi,

Since today I'm unable to start any GUI application (testing with gnome-terminal and xterm) within a debian 10 based AppVM:

In Qubes Manager the VM shows the green state icon.

To collect logs I connected via 'xl console':

sudo xl console debian-10:

journalctl -f

<try to start gnome-terminal>

Log output:

qrexec-agent[599]: executed user:QUBESRPC qubes.VMShell dom0 pid 24766
qrexec-agent[24766]: pam_unix(qrexec:session): session opened for user user by (uid=0)
systemd[1]: Started Session c17 of user user.
qubes.VMShell-dom0[24775]: .[0;1;39m.[0;1;31m.[0;1;39mUnable to init server: Could not connect: Connection refused.[0m
qrexec-agent[24766]: pam_unix(qrexec:session): session closed for user user
qrexec-agent[599]: send exit code 1
qrexec-agent[599]: pid 24766 exited with 1
qrexec-agent[599]: eintr
systemd[1]: session-c17.scope: Succeeded.

The last updates according to /var/log/apt/history.log within that VM:

Start-Date: 2021-02-01
Commandline: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade
Install: linux-headers-4.19.0-14-amd64:amd64 (4.19.171-2, automatic), linux-headers-4.19.0-14-common:amd64 (4.19.171-2, automatic), linux-image-4.19.0-14-amd64:amd64 (4.19.171-2, automatic)
Upgrade: linux-libc-dev:amd64 (4.19.160-2, 4.19.171-2), linux-compiler-gcc-8-x86:amd64 (4.19.160-2, 4.19.171-2), linux-image-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), linux-headers-amd64:amd64 (4.19+105+deb10u8, 4.19+105+deb10u9), lightning:amd64 (1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), thunderbird:amd64 (1:78.6.0-1~deb10u1, 1:78.7.0-1~deb10u1), linux-kbuild-4.19:amd64 (4.19.160-2, 4.19.171-2)



Any help to further debug or solve this issue is greatly appreciated.

qubes...@riseup.net

unread,
Feb 20, 2021, 9:53:16 AM2/20/21
to qubes...@googlegroups.com
solved: the disk of the template was full
Reply all
Reply to author
Forward
0 new messages