pveproxy.service Problem

[Wanja Johann]

Hello everyone,

our environment.

- 2 servers in cluster operation (node1-node2)
- DMZ
- Bond is configured on both.

Everything was running fine, then node1 was restarted.
Since then the GUI is not reachable under 10.167.25.40:8006.
After many searches there is a problem with “pveproxy.service - PVE API Proxy Server”









- Ping localhost does not work
- it does not listen on port 8006




in Hosts or interface has not been changed........

Do you have any idea where the error is coming from and what I can do to fix it?

Many thanks in advance.

 

[bbgeek17]

Hi @Wanja Johann , welcome to forum.

in Hosts or interface has not been changed........

It may not have changed, but it can still be wrong. The easiest way to determine that is to see the exact file context. I'd recommend that you share it here, as text encoded in "CODE" tags, to start with.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Wanja Johann]

Hi @Wanja Johann , welcome to forum.


It may not have changed, but it can still be wrong. The easiest way to determine that is to see the exact file context. I'd recommend that you share it here, as text encoded in "CODE" tags, to start with.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Host


Interface

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

iface ens1f0 inet manual

iface ens1f1 inet manual

iface ens2f0 inet manual

iface ens2f1 inet manual

iface enx5ef3fcbd035b inet manual

auto bond0
iface bond0 inet manual
        bond-slaves eno1 eno2
        bond-miimon 100
        bond-mode balance-alb

auto vmbr0
iface vmbr0 inet manual
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vlan3078
iface vlan3078 inet static
        address 10.167.25.40/24
        gateway 10.167.25.1
        vlan-raw-device bond0

source /etc/network/interfaces.d/*

 

[bbgeek17]

Reboot your system and examine the system log from start: journalctl -b0

Your system seems to be in a very precarious state. I suspect there are potentially more revealing messages in system log.
Have you reviewed the output of "ip a" ?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Wanja Johann]

Reboot your system and examine the system log from start: journalctl -b0

Your system seems to be in a very precarious state. I suspect there are potentially more revealing messages in system log.
Have you reviewed the output of "ip a" ?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

journalctl -b0








ip a

 

[bbgeek17]

Well, line 833 has to do with localhost :
$socket = IO::Socket::IP->new( LocalHost => '::', %sockargs) //

So, the fact that your basic networking is in disarray is likely the primary cause of your issues.
It could be due to filesystem corruption on restart. Or, there was a change made a while back that only took effect after the reboot.

In summary, you have a Linux network stack problem that is the root cause of your Proxmox issue.
I don't have a solution based on the provided information.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Wanja Johann]

Well, line 833 has to do with localhost :
$socket = IO::Socket::IP->new( LocalHost => '::', %sockargs) //

So, the fact that your basic networking is in disarray is likely the primary cause of your issues.
It could be due to filesystem corruption on restart. Or, there was a change made a while back that only took effect after the reboot.

In summary, you have a Linux network stack problem that is the root cause of your Proxmox issue.
I don't have a solution based on the provided information.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

What information do you need? I will be happy to provide you with all the necessary information.
Are there no possible solutions to narrow down the error?

Does anyone else have any ideas as to where this is coming from and what you can try?

 

[bbgeek17]

Are there no possible solutions to narrow down the error?

Plug-in "ubuntu cannot ping localhost" into Google. There are more than a few ways that people get into similar situations. Go through the threads, hopefully one of them applies to you.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Wanja Johann]

Plug-in "ubuntu cannot ping localhost" in Google. Es gibt mehr als ein paar Möglichkeiten, wie Menschen in ähnliche Situationen geraten. Gehen Sie die Threads durch, hoffentlich trifft einer davon auf Sie zu.

Viel Glück

---

Blockbridge: All-NVME-Speicher mit extrem niedriger Latenz für Proxmox - https://www.blockbridge.com/proxmox

I did that, but unfortunately without success, which is why I opened this post.

 

[Wanja Johann]

I was able to solve the problem, and here is the solution, in case someone else also gets this error.

I had 2 servers as node1 and node2 in the cluster, when I prepared a node3 server, i.e. set it up (but not yet included in the cluster), I gave node3 a static IP xxx.xxx.xxx.43 (node1 had xxx.xxx.xxx.40 and node2 xxx.xxx.xxx.42)

The error was that node3 had the following IP in its /Hosts file xxx.xxx.xxx.40.
After node1 was restarted, the problem arose because node3 took the IP of node1.

How node3 took the IP from node1 remains a mystery to me.
After I changed the IP in node3, everything works again.

Translated with DeepL.com (free version)