failed to connect to the server

A

artichaut

New Member
Oct 29, 2022
12
0
1
Im getting these error on ct & vm, on chrome & safari & edge
Screenshot 2023-06-04 at 15.29.20.pngScreenshot 2023-06-04 at 15.29.36.pngCT: failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1

VM: TASK ERROR: connection timed out
 
anyone ? please
Code: 
root@pve2:~# pveversion -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
proxmox-ve: 7.4-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.7.0
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-2
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1
root@pve2:~#
 
Code: 
root@pve2:~# apt update
Hit:1 http://ftp.be.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Get:3 http://ftp.be.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease         
Fetched 44.1 kB in 1s (33.5 kB/s)     
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
6 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Skipping acquire of configured file 'pve-no-subscriptiondeb/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'pve-no-subscriptiondeb' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'pve-no-subscriptiondeb/i18n/Translation-en' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'pve-no-subscriptiondeb' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'http://download.proxmox.com/debian/pve/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'http://download.proxmox.com/debian/pve' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'http://download.proxmox.com/debian/pve/i18n/Translation-en' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'http://download.proxmox.com/debian/pve' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'bullseye/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'bullseye' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'bullseye/i18n/Translation-en' as repository 'http://download.proxmox.com/debian/pve bullseye InRelease' doesn't have the component 'bullseye' (component misspelt in sources.list?)
root@pve2:~#
 
leesteken said:
Such issues are common with two-node clusters. How many nodes does your cluster have and/or does it have a QDevice?
Click to expand...

1 cluster and 2 nodes-(2 device)... i dont have qdevice

1 node is masternode and setup cluster on that..

I haven't experimented with Qdevide, I don't need to. mostly one server works for me. I turn on other as needed when I'm experimenting. if I knew it wouldn't work, I would never have connected them. as far as I can see, it's a little harder to separate them now. and i need both turned on to use shell from web
 
drvenipatuljak said:
1 cluster and 2 nodes-(2 device)... i dont have qdevice

1 node is masternode and setup cluster on that..
Click to expand...
Proxmox does not have a "masternode" and all nodes are equal: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_pvecm
drvenipatuljak said:
I haven't experimented with Qdevide, I don't need to. mostly one server works for me. I turn on other as needed when I'm experimenting. if I knew it wouldn't work, I would never have connected them. as far as I can see, it's a little harder to separate them now. and i need both turned on to use shell from web
Click to expand...
That's asking for trouble because each one never has more than half the total number of votes: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_quorum
Lots of threads about problems with two-node clusters on this forum. Either add a QDevice ( https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_external_vote_support ) or live with the issues. Best of luck.
 
  • Like
Reactions: drvenipatuljak
I have the same problem, I can no longer access the shell on my first node and the second node is already formatted ... it looks as if the systems on node 1 can no longer be started. Damn, can I still save something ... at least restore the data somehow?
Before removing node 2, I used “pvecm delnode pve2” to remove the node from the cluster. Still the problem.
 
You must log in or register to reply here.
Top Bottom