"hostname 'pbs' does not resolves to any non-loopback address" after upgrade pbs2 > pbs3

M

MrAlfabet

Member
Jul 17, 2020
8
0
6
39
I'm running PBS in a debian LXC on top of PVE.

The PBS container is set to DHCP, with the IP reserved at the DHCP server.

After upgrading PVE7 to PVE8, and subsequently PBS2 to PBS3, the PBS container gives the error "hostname 'pbs' does not resolves to any non-loopback address" after boot (console). When I `pct` into the LXC, it has received the correct IP and has full internet connectivity. Setting the IPv4 to static for the LXC resolves the problem.

hostname (pbs) is set correctly in /etc/hostname, ethernet interface is set correctly when changed through the PVE web UI (either dhcp or static).

`ping pbs` results in pinging 127.0.1.1 when the LXC is set to DHCP, but results in pinging the correct internal IP address when set to static.

Any idea where I should look to solve this problem? I'd rather not re-create the LXC, or set the IP staticly (current workaround)
 
The IP address in /etc/hosts changes based on DHCP/static IP

Code: 
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
# --- BEGIN PVE ---
<IP here> pbs.mydomain.com pbs
# --- END PVE ---

the <IP here> part is the proper internal IP when set to static, but is 127.0.1.1 when set to DHCP. replaced my domain name with 'mydomain.com' for privacy's sake.
 
OK, I had the same problem PBS reporting 'does not resolves to any non loopback address'.

I use a machine with a physical gigabit port and a wifi port.

With ETH0 enabled and WLAN0 not connected, I get this error on reboot, I wondered if enabling WLAN0 alone might fix it, it doesn't.
Disabling IPV6 doesn't fix it either,

The message itself comes from /etc/issue, which is just plain text, I've seen this file appear on Raspberry Pi OS recently with a Trixie install, so I just deleted it, at reboot it reappeared. There is also an /etc/issue.net test file with the same content.

Then tried a reboot [again], I've also had problems logging in on the GUI, despite EVERYTHING having worked previously, so there's nothing wrong with accounts or passwords. Logins are working, my hosts file looks like
127.0.0.1 localhost
127.0.1.1 servername.local servername

192.168.10.22 nasname.local nasname

# The following lines are desirable for IPv6 capable hosts
#::1 localhost ip6-localhost ip6-loopback
#ff02::1 ip6-allnodes
#ff02::2 ip6-allrouters

$ nslookup
> servername
Server: 192.168.10.13
Address: 192.168.10.13#53

Name: servername.local
Address: 192.168.10.45

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d4:9a:20:ef:11:7c brd ff:ff:ff:ff:ff:ff
altname enxd49a20ef117c
inet 192.168.01.45/24 brd 192.168.10.255 scope global dynamic noprefixroute enp0s10
valid_lft 28703sec preferred_lft 28703sec
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 90:84:0d:f2:5e:99 brd ff:ff:ff:ff:ff:ff
altname wlx90840df25e99
inet 192.168.10.168/24 brd 192.168.10.255 scope global dynamic noprefixroute wlan0
valid_lft 28713sec preferred_lft 28713sec
inet6 fd15:f334:d394:4512:273:2618:674f:8ea3/64 scope global dynamic noprefixroute
valid_lft 1761sec preferred_lft 1761sec
inet6 fe80::b821:3c76:71c7:9f51/64 scope link noprefixroute


I would add at this point that the servername's IP address is DHCP allocated, not static, haven't tried that yet.
 
You must log in or register to reply here.
Top Bottom
Back