From: Adam Weremczuk <adamw@matrixscience.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] stuck container
Date: Wed, 18 Aug 2021 12:10:41 +0100 [thread overview]
Message-ID: <39b5815a-c591-8c08-21ce-fb441dff8bb3@matrixscience.com> (raw)
Hi all,
Host PVE version: 6.2-6, Debian 10.4
Dual host set up using zfs and replication.
Container: Debian 10.10
The container responds to ping and telnet to SSH port but I can't ssh to
it, access via PVE console or stop/start it seeing all sorts of errors:
command 'lxc-stop -n 100 --timeout 5' failed: got timeout
TASK ERROR: received interrupt
command 'lxc-stop -n 100 --timeout 5' failed: got timeout
TASK ERROR: got unexpected control message:
trying to acquire lock...
TASK ERROR: can't lock file '/run/lock/lxc/pve-config-100.lock' - got
timeout
malformed authentication string
TASK ERROR: command '/usr/bin/termproxy 5901 --path /vms/101 --perm
VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole101 -r winch
-z lxc-console -n 101 -e -1' failed: exit code 255
From the shell I tried deleting /run/lock/lxc/pve-config-100.lock,
killing all processes referring to container 100 and starting it but no joy:
pct reboot 100 --timeout 5
trying to acquire lock...
can't lock file '/run/lock/lxc/pve-config-100.lock' - got timeout
pct stop 100 --skiplock 1
trying to acquire lock...
can't lock file '/run/lock/lxc/pve-config-100.lock' - got timeout
pct shutdown 100 --forceStop 1 --timeout 5
trying to acquire lock...
can't lock file '/run/lock/lxc/pve-config-100.lock' - got timeout
pct stop 100 --skiplock 1
[stalls here]
All the other containers appear to be running fine.
Any ideas?
Thanks,
Adam
reply other threads:[~2021-08-18 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39b5815a-c591-8c08-21ce-fb441dff8bb3@matrixscience.com \
--to=adamw@matrixscience.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.