[SOLVED] 127.0.1.1 problem start pve-cluster

[lordhanuman]

I installed proxmox starting from a debian 11, I saw that if in the / etc / hosts there is the entry 127.0.1.1 with the fqdn the pve-cluster daemon fails to start.
Clearly during the installation of proxmox I removed the entry
When the server restarts it reappears and I fail to start the service.
Is there any service I need to turn off to make sure that doesn't happen?


for example my /etc/hosts is
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

141.10.47.22 test.domain.com test


after reboot is

127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


141.10.47.22 test.domain.com test

127.0.1.1 test.domain.com test

and the pve-cluster fail to start
Thanks

 

[oguz]

hi,

I installed proxmox starting from a debian 11, I saw that if in the / etc / hosts there is the entry 127.0.1.1 with the fqdn the pve-cluster daemon fails to start.
Clearly during the installation of proxmox I removed the entry
When the server restarts it reappears and I fail to start the service.

so when you reboot the host the line with 127.0.1.1 comes back? that's not normal behavior.

if you're sure this happens at reboot then you could install auditd and do the following:

auditctl -w /etc/hosts -p war -k hosts-file

then reboot and check:

ausearch -f /etc/hosts| grep exe --color

and it should show you which program is accessing/writing to it.

one way to make it stick would be setting the file immutable: chattr +i /etc/hosts
though this doesn't solve the underlying issue...

 

[lordhanuman]

the amazing thing is that it tells me that the file I edited there with vi.
I believe the person responsible for these changes is cloud-init.
In the best practice of proxmox should it be uninstalled?

 

[lordhanuman]

I confirm the manager is cloud-init
removed the package after the problems (I had to rebuild / etc / hosts by hand)

 

[oguz]

yes your host shouldn't be managed by cloud-init.

glad you found the issue!
you can mark the thread as [SOLVED] so others also know what to expect