Search results

Hi @fabian , than ks for the answer, any chance to point the issue so that we could follow up the resolution? Regards

Hi @thesix , did you checked the logs IN the proxmox. Maybe the id you're using are not allowed to browse the API.

Hi @radim.smehlik , I understand your point of view. Yet, AFAICS, the ceph bug talk about the same issue, without proxmox.... So IMHO, ceph should first solve the issue or maybe Proxmox team could propose a solution to the ceph team. It looks much mainstream to me this way. But yeah.... we all...

Hi, It depends on the ceph team, not the proxmox one

Hi @fiona, thanks for your feedback, do you need a test on the pve-kernel-6.2.16-3-pve ?

Hi, I confirm that we also have the same messages in the logs : kernel: pverados[4133454]: segfault at 55c6095fa408 ip 000055c607463cef sp 00007ffe68d860d0 error 7 in perl[55c60737b000+195000] likely on CPU 40 (core 21, socket 0) kernel: Code: 48 89 45 70 48 3b 45 78 0f 84 b6 02 00 00 4c 89 ea...

Hi, I have the same logs in PVE8.0.3 for ovs logs : Jan 24 16:05:56 fava2 ovs-vsctl[68966]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth113i0 Jan 24 16:05:56 fava2 ovs-vsctl[68966]: ovs|00002|db_ctl_base|ERR|no port named veth113i0 Jan 24 16:05:56 fava2 ovs-vsctl[68967]...

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