Error Connection error 595: Connection refused after Upgrade from Proxmox 5.3-8 to 5.4-2

O

omempo

New Member
Sep 25, 2023
3
0
1
Please Kindly Help me Solve the Problem, I've been looking through the forum but still can't solve it.

I just mistakenly upgraded Proxmox, I used the wrong repository, it should be 'stretch' but I used 'bookworm', and now my Node is broken, every CT can't be accessed from WEB UI (Error Connection error 595: Connection refused) but I can access and use the Shell from Node.

this is my configuration:

/etc/apt/sources.list
Code: 
deb http://archive.debian.org/debian stretch main contrib

# security updates
deb http://archive.debian.org/debian-security/ stretch/updates main contrib
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

pveversion -v
Code: 
proxmox-ve: 5.4-2 (running kernel: 5.4.203-1-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
pve-kernel-5.4: 6.4-20
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1+deb9u1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.1.0-1
proxmox-widget-toolkit: 2.6-2
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 3.0-22
pve-firmware: 3.3-2
pve-ha-manager: 2.0-9
pve-i18n: 2.3-1
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 4.7.0-3
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

apt-get update
Code: 
Ign:1 http://archive.debian.org/debian stretch InRelease
Hit:2 http://archive.debian.org/debian-security stretch/updates InRelease
Hit:3 http://archive.debian.org/debian stretch Release                                
Hit:5 http://download.proxmox.com/debian/pve stretch InRelease                        
Reading package lists... Done

apt-get dist-upgrade
Code: 
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I've been re install the proxmox-ve and apt install pve-manager.

still the error exist.

systemctl status
Code: 
proxmox3
    State: degraded
     Jobs: 0 queued
   Failed: 5 units
    Since: Tue 2023-09-26 10:58:50 WIB; 1h 8min ago
   CGroup: /
           ├─1593 bpfilter_umh
           ├─init.scope
           │ └─1 /sbin/init
           ├─system.slice
           │ ├─systemd-udevd.service
           │ │ └─383 /lib/systemd/systemd-udevd
           │ ├─cron.service
           │ │ └─1991 /usr/sbin/cron -f
           │ ├─nfs-mountd.service
           │ │ └─1519 /usr/sbin/rpc.mountd --manage-gids
           │ ├─pve-firewall.service
           │ │ └─2059 pve-firewall
           │ ├─spiceproxy.service
           │ │ ├─ 2151 spiceproxy
           │ │ └─18879 spiceproxy worker
           │ ├─pve-ha-crm.service
           │ │ └─2117 pve-ha-crm
           │ ├─systemd-journald.service
           │ │ └─361 /lib/systemd/systemd-journald
           │ ├─ssh.service
           │ │ ├─ 1676 /usr/sbin/sshd -D
           │ │ ├─19273 sshd: root@pts/0
           │ │ ├─19279 /bin/login -f
           │ │ ├─19284 -bash

I found two service can't be restart
systemctl restart pvedaemon
Code: 
Job for pvedaemon.service failed because the control process exited with error code.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.

systemctl status pvedaemon.service
pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2023-09-26 12:09:46 WIB; 52s ago
  Process: 21457 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
      CPU: 382ms

Sep 26 12:09:46 proxmox3 pvedaemon[21457]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Sep 26 12:09:46 proxmox3 pvedaemon[21457]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Sep 26 12:09:46 proxmox3 pvedaemon[21457]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 26 12:09:46 proxmox3 pvedaemon[21457]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 26 12:09:46 proxmox3 pvedaemon[21457]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Sep 26 12:09:46 proxmox3 pvedaemon[21457]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Sep 26 12:09:46 proxmox3 systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
Sep 26 12:09:46 proxmox3 systemd[1]: Failed to start PVE API Daemon.
Sep 26 12:09:46 proxmox3 systemd[1]: pvedaemon.service: Unit entered failed state.
Sep 26 12:09:46 proxmox3 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.

systemctl restart pveproxy
Code: 
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xe" for details.

systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2023-09-26 12:11:31 WIB; 6s ago
  Process: 22427 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
      CPU: 390ms

Sep 26 12:11:31 proxmox3 pveproxy[22427]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Sep 26 12:11:31 proxmox3 pveproxy[22427]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Sep 26 12:11:31 proxmox3 pveproxy[22427]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Sep 26 12:11:31 proxmox3 pveproxy[22427]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Sep 26 12:11:31 proxmox3 pveproxy[22427]: Compilation failed in require at /usr/bin/pveproxy line 11.
Sep 26 12:11:31 proxmox3 pveproxy[22427]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Sep 26 12:11:31 proxmox3 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Sep 26 12:11:31 proxmox3 systemd[1]: Failed to start PVE API Proxy Server.
Sep 26 12:11:31 proxmox3 systemd[1]: pveproxy.service: Unit entered failed state.
Sep 26 12:11:31 proxmox3 systemd[1]: pveproxy.service: Failed with result 'exit-code'.
 
Last edited:
Hello,

Thank you for posting the details!

Please provide us also with the apt history using `cat /var/log/apt/history.log` command.
 
sure,

cat /var/log/apt/history.log

Code: 
Start-Date: 2023-09-26  10:42:29
Commandline: apt install proxmox-ve --reinstall
Install: proxmox-ve:amd64 (5.4-2)
Remove: pve-kernel-helper:amd64 (6.4-20)
End-Date: 2023-09-26  10:42:32

Start-Date: 2023-09-26  10:43:06
Commandline: apt install pve-manager --reinstall
Reinstall: pve-manager:amd64 (5.4-15)
End-Date: 2023-09-26  10:43:12

Start-Date: 2023-09-26  12:01:38
Commandline: apt install proxmox-ve --reinstall
Reinstall: proxmox-ve:amd64 (5.4-2)
End-Date: 2023-09-26  12:01:40

Start-Date: 2023-09-26  12:05:50
Commandline: apt install --reinstall libpve-apiclient-perl pve-manager
Reinstall: pve-manager:amd64 (5.4-15)
End-Date: 2023-09-26  12:05:54
 
Thank you for post the history ofr apt.

Please try to re-install pve-manager and proxmox-ve using the following commands:

Code: 
apt-get install proxmox-ve pve-manager --reinstall
 
apt-get install proxmox-ve pve-manager --reinstall

Code: 
Reading package lists... Done
Building dependency tree     
Reading state information... Done
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 7,738 B/1,978 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 proxmox-ve all 5.4-2 [7,738 B]
Fetched 7,738 B in 1s (4,832 B/s)   
(Reading database ... 54394 files and directories currently installed.)
Preparing to unpack .../proxmox-ve_5.4-2_all.deb ...
Unpacking proxmox-ve (5.4-2) over (5.4-2) ...
Preparing to unpack .../pve-manager_5.4-15_amd64.deb ...
Unpacking pve-manager (5.4-15) over (5.4-15) ...
Setting up pve-manager (5.4-15) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up proxmox-ve (5.4-2) ...


cat /var/log/apt/history.log
Code: 
Start-Date: 2023-09-26  10:42:29
Commandline: apt install proxmox-ve --reinstall
Install: proxmox-ve:amd64 (5.4-2)
Remove: pve-kernel-helper:amd64 (6.4-20)
End-Date: 2023-09-26  10:42:32

Start-Date: 2023-09-26  10:43:06
Commandline: apt install pve-manager --reinstall
Reinstall: pve-manager:amd64 (5.4-15)
End-Date: 2023-09-26  10:43:12

Start-Date: 2023-09-26  12:01:38
Commandline: apt install proxmox-ve --reinstall
Reinstall: proxmox-ve:amd64 (5.4-2)
End-Date: 2023-09-26  12:01:40

Start-Date: 2023-09-26  12:05:50
Commandline: apt install --reinstall libpve-apiclient-perl pve-manager
Reinstall: pve-manager:amd64 (5.4-15)
End-Date: 2023-09-26  12:05:54

Start-Date: 2023-09-27  16:11:43
Commandline: apt-get install proxmox-ve pve-manager --reinstall
Reinstall: pve-manager:amd64 (5.4-15), proxmox-ve:amd64 (5.4-2)
End-Date: 2023-09-27  16:11:53

no change the problem still exists> Error Connection error 595: Connection refused when accessing the CT inside the Node using Web UI.
 
Last edited:
Thank you for the output!

You can login to your Proxmox VE right? if yes - can you please try to restart the pvedaemon and pveproxy services?

If that didn't help please provide us with the full syslog!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back