Search results

Hi, Maybe you could use a wrapper that will provide more check in your conf. Have a look there https://git.interior.edu.uy/cielito/proxmox

also impacted on latest proxmox 8.0.3

did you have a look to https://forum.proxmox.com/threads/open-files-issue-on-pve-node.69783/#post-439145 ? If solved could you marked your thread ? thanks

could you marked your thread as solved ?

Hi, There is some issues with the latest OVH templates, cloud init is updated. I faced almost same issues yesterday. Have a look there : https://forum.proxmox.com/threads/strange-proxmox-errors.129419/#post-567511

solved here : https://forum.proxmox.com/threads/strange-proxmox-errors.129419/#post-567511

ah, well done.... you saved my night !

my bad, it concerns the LXC part

found in /usr/share/perl5/PVE/LXC/Setup/Base.pm it explicitely add 127.0.1.1 in /etc/hosts files If you already have set the host name elsewhere it will cause pve-cluster to not start

I confirm that it happens for a standalone upgrdae from a fresh 7.4 installation migrated to v8. Boot still add line in /etc/hosts and it prevent the services to run.

Hi @MapGuy11 , Did the reinstall solve the issue ?

hum... a new card appears in my network conf : enxca016--------

Hi, After upgrading one of my node, I faced an issue with the /etc/hosts file overwritten at each boot https://forum.proxmox.com/threads/strange-proxmox-errors.129419/#post-567471

hum... same issue as https://forum.proxmox.com/threads/rebooted-proxmox-and-messed-up-etc-hosts-file.63268/

hum.... My issue seems to come form the /etc/hosts file. The node name appeared too many times on the line 127.0.1.1 I've commented this and restarted successfully the pve-cluster. BUR, when I reboot the server, a new line with same erronous values has been added : cat /etc/hosts 127.0.0.1...

Hi, I faced the same issue here after upgraing one node of a cluster https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Testing_the_Upgrade One node work perfectly the second failde. It looks like fuse has not started and /etc/pve/ is emty causing the corosync to fail and of cours pveproxy to fail...

by the way I'm using the proxmox modue and not the CLI inside proxmox

Hi, working with latest v7 up to date on a cluster with ceph and running an ansible script for stopping then deleting ct, I also get this error. Did you found any tips ?

interesting @korc thanks

Hi everyone, Always looking to improve PVE setup I've found this ressource : https://www.tweaked.io/guide/kernel/ A point really interesting in this thread is the Process Scheduler part with some improvements with PostgreSQL observed on the PGSQL mailing list. I've successfully change the...