I don't have web access

C

cabling

Active Member
Jun 19, 2018
25
0
41
52
Hello, I have a problem with a cluster node.
I installed a new node, and add it to the cluster, I didn't have any problem, it integrated well.

Yesterday I went to access the node via the web and observed that the cluster marked it without access. I tried to access the node directly using its ip address (https://172.26.2.235:8006) and I don't have access either.

I get this result

This website cannot be reachedThe page 172.26.2.235 has refused the connection.
Try to:

check connection
Check proxy and firewall
ERR_CONNECTION_REFUSED

By console if I have access.

I have an annual subscription.

Can anybody help me?

Greetings and thanks
 
Hi,
any errors in the journal? journalctl -r -b gives you a paged view of the journal since boot in reverse. What's the status of systemctl status pveproxy.service pvestatd.service?
 
thanks for answering, this is the result

journalctl -r -b
-- Logs begin at Mon 2023-07-31 10:23:50 CEST, end at Mon 2023-07-31 11:45:12 CE
Jul 31 11:45:12 PROXMOX9 systemd[1]: Started User Manager for UID 0.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Startup finished in 26ms.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Default.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Basic System.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Paths.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Sockets.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent (
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent a
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Timers.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent a
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent (
Jul 31 11:45:12 PROXMOX9 systemd[5716]: pam_unix(systemd-user:session): session
Jul 31 11:45:12 PROXMOX9 systemd[1]: Started Session 10 of user root.
Jul 31 11:45:12 PROXMOX9 systemd-logind[1350]: New session 10 of user root.
Jul 31 11:45:12 PROXMOX9 systemd[1]: Starting User Manager for UID 0...
Jul 31 11:45:12 PROXMOX9 systemd[1]: pvenetcommit.service: Cannot add dependency
Jul 31 11:45:12 PROXMOX9 systemd[1]: Created slice User Slice of root.
Jul 31 11:45:12 PROXMOX9 sshd[5692]: pam_unix(sshd:session): session opened for
Jul 31 11:45:12 PROXMOX9 sshd[5692]: Accepted password for root from 192.168.222
Jul 31 11:45:10 PROXMOX9 kernel: hid-generic 0003:03F0:094A.0052: input,hidraw2:
Jul 31 11:45:10 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/
Jul 31 11:45:10 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
lines 1-23...skipping...
-- Logs begin at Mon 2023-07-31 10:23:50 CEST, end at Mon 2023-07-31 11:45:12 CEST. --
Jul 31 11:45:12 PROXMOX9 systemd[1]: Started User Manager for UID 0.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Startup finished in 26ms.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Default.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Basic System.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Paths.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Sockets.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent (access for web browsers).
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Reached target Timers.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 31 11:45:12 PROXMOX9 systemd[5716]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 31 11:45:12 PROXMOX9 systemd[5716]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Jul 31 11:45:12 PROXMOX9 systemd[1]: Started Session 10 of user root.
Jul 31 11:45:12 PROXMOX9 systemd-logind[1350]: New session 10 of user root.
Jul 31 11:45:12 PROXMOX9 systemd[1]: Starting User Manager for UID 0...
Jul 31 11:45:12 PROXMOX9 systemd[1]: pvenetcommit.service: Cannot add dependency job, ignoring: Unit pvenetcommit.service is masked.
Jul 31 11:45:12 PROXMOX9 systemd[1]: Created slice User Slice of root.
Jul 31 11:45:12 PROXMOX9 sshd[5692]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jul 31 11:45:12 PROXMOX9 sshd[5692]: Accepted password for root from 192.168.222.6 port 65115 ssh2
Jul 31 11:45:10 PROXMOX9 kernel: hid-generic 0003:03F0:094A.0052: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:45:10 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.0052 /input/input83
Jul 31 11:45:10 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:45:10 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical Mouse
Jul 31 11:45:10 PROXMOX9 kernel: usb 4-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 11:45:10 PROXMOX9 kernel: usb 4-12: New USB device found, idVendor=03f0, idProduct=094a
Jul 31 11:45:09 PROXMOX9 kernel: usb 4-12: new low-speed USB device number 84 using xhci_hcd
Jul 31 11:45:08 PROXMOX9 kernel: usb 4-12: USB disconnect, device number 83
Jul 31 11:45:04 PROXMOX9 sshd[5692]: Failed password for root from 192.168.222.6 port 65115 ssh2
Jul 31 11:45:02 PROXMOX9 sshd[5692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.222.6 user=root
Jul 31 11:44:08 PROXMOX9 kernel: hid-generic 0003:03F0:094A.0051: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:44:08 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.0051 /input/input82
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical
Jul 31 11:44:08 PROXMOX9 kernel: hid-generic 0003:03F0:094A.0051: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:44:08 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.0051/input/input82
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical Mouse
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: New USB device found, idVendor=03f0, idProduct=094a
Jul 31 11:44:08 PROXMOX9 kernel: usb 4-12: new low-speed USB device number 83 using xhci_hcd
Jul 31 11:44:06 PROXMOX9 kernel: usb 4-12: USB disconnect, device number 82
Jul 31 11:43:06 PROXMOX9 kernel: hid-generic 0003:03F0:094A.0050: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:43:06 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.0050/input/input81
Jul 31 11:43:06 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:43:06 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical Mouse
Jul 31 11:43:06 PROXMOX9 kernel: usb 4-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 11:43:06 PROXMOX9 kernel: usb 4-12: New USB device found, idVendor=03f0, idProduct=094a
Jul 31 11:43:06 PROXMOX9 kernel: usb 4-12: new low-speed USB device number 82 using xhci_hcd
Jul 31 11:43:04 PROXMOX9 kernel: usb 4-12: USB disconnect, device number 81
Jul 31 11:42:04 PROXMOX9 kernel: hid-generic 0003:03F0:094A.004F: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:42:04 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.004F/input/input80
Jul 31 11:42:04 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:42:04 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical Mouse
Jul 31 11:42:04 PROXMOX9 kernel: usb 4-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 11:42:04 PROXMOX9 kernel: usb 4-12: New USB device found, idVendor=03f0, idProduct=094a
Jul 31 11:42:04 PROXMOX9 kernel: usb 4-12: new low-speed USB device number 81 using xhci_hcd
Jul 31 11:42:03 PROXMOX9 kernel: usb 4-12: USB disconnect, device number 80
Jul 31 11:41:03 PROXMOX9 kernel: hid-generic 0003:03F0:094A.004E: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:14.0-12/input0
Jul 31 11:41:03 PROXMOX9 kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb4/4-12/4-12:1.0/0003:03F0:094A.004E/input/input79
Jul 31 11:41:03 PROXMOX9 kernel: usb 4-12: Manufacturer: PixArt
Jul 31 11:41:03 PROXMOX9 kernel: usb 4-12: Product: HP USB Optical Mouse
Jul 31 11:41:03 PROXMOX9 kernel: usb 4-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 31 11:41:03 PROXMOX9 kernel: usb 4-12: New USB device found, idVendor=03f0, idProduct=094a
Jul 31 11:41:02 PROXMOX9 kernel: usb 4-12: new low-speed USB device number 80 using xhci_hcd
Jul 31 11:41:01 PROXMOX9 kernel: usb 4-12: USB disconnect, device number 79
lines 1-62


root@PROXMOX9:~# systemctl status pveproxy.service pvestatd.service
● pveproxy.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)

● pvestatd.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)


thank you, regards
 
Your services are masked, this should not have happened on its own. Did you change something after joining the node to the cluster? Please post the output of systemctl list-unit-files --state=masked.

You should unmask these services and start them by running systemctl unmask pvestatd pveproxy and systemctl enable --now pvestatd pveproxy

Also, in order to post the content of the journal correctly, dump the content to a file by running journalctl -b > journal.txt and upload the file as attachment here.
 
No he modificado nada. resultado adjunto
 

Attachments

  • systemctl.txt
    1.6 KB · Views: 2
cabling said:
No he modificado nada. resultado adjunto
Click to expand...
The file you posted does not contain the journal, but the output of the systemctl status command. Nevertheless, this shows that most of the pve services are masked, which might indicate that something went wrong during an upgrade of pve-manager as it seems these services should be unmasked during dpkg configure. Try to reconfigure by running
Code: 
dpkg-reconfigure pve-manager
 
root@PROXMOX9:~# dpkg-reconfigure pve-manager

/usr/sbin/dpkg-reconfigure: pve-manager is broken or not fully installed
 
What do you get by running
Code: 
apt-get update
apt-get dist-upgrade
?
 
this is results
 

Attachments

  • apt upgrade.txt
    294 bytes · Views: 3
  • apt update.txt
    8.6 KB · Views: 2
cabling said:
this is results
Click to expand...
Either your repositories are configured incorrectly or you are still running a PVE 5.4 node... Note that this version was released back in 2019 and is end of life since long time.

Please post the output of pveversion -v.

Seems like you have no singning key for that repository, so i suggest you use the no-subscription repository and upgrade you packages to the latest version of PVE5: https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_5_x_repositories

Then you will have to follow these upgrade procedure to get to PVE 8 (or at least PVE 7.4, which at the time of writing is still supported):

https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
 
Last edited:
Yes, but the version you are running is not supported anymore. You will have to upgrade your cluster!

But first fix the issue with the incorrectly installed pve-manager package. If you don't want to fix the pve-manager package with the no-subscription repo, you can also add the gpg key on the node with the issue and run the apt-get update && apt-get dist-upgrade via the enterprise repo. Therefore you will have to run wget http://download.proxmox.com/debian/proxmox-ve-release-5.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg.
 
thanks for your help.
I am interested in leaving the old version so that it is compatible with the other nodes. I will update another time.
What should I do?
Greetings and thanks
 
cabling said:
thanks for your help.
I am interested in leaving the old version so that it is compatible with the other nodes. I will update another time.
What should I do?
Greetings and thanks
Click to expand...
As stated above, you will first have to install the pve release key via the wget command and then perform an apt-get update && apt-get dist-upgrade. Post the output once again afterwards.

Note that not upgrading is not an option, as both Debian 9 https://lists.debian.org/debian-devel-announce/2023/03/msg00006.html and PVE 5 are end of life. So there will be no more updates and support for these versions.
 
Okay, now let's ignore the outdated debian repo errors and try to reinstall the pve-manager package by running apt-get --reinstall install pve-manager. Then post the output again
 
Last edited:
cabling said:
Lo siento, estoy perdido, ¿cuál es el siguiente paso?
Click to expand...
Please post in English. Your next step is the one described in my last post, reinstalling the pve-manager package.
 
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