Search results

Hallo zusammen, ich habe eine PBS v3.2-2 als VM laufen. Diese kann ich aber nicht sichern lassen. Alle anderen auf dem Node sichern normal. Hat jmd. eine idee? Als Fehlermeldung bekomme ich nur:

Hi, how can i update in debian from v3.2-2.? normal update dist-upgrade dont find new v3.3... regards

hi thanks for answer, if i add in /etc/hosts a entry 192.168.1.22 backup-srv.local and i ping of a other node, it dont ping over intranet, than it goes over internet ip v4 or ipv6, normal it must work over intranet ip, well ip is internal reachable and pingable, but host goes over internet ips...

Ok but if i use FQDN instead of local IP, do Servers use internal Network for Backup and not public IP with FQDN? I mean no...

hi as id i use full qualified domain name and in server lokal ip address of pbs well it comes all over internal ip network.

update, if i remove fingerprint on proxmox storage, i have no access to proxmox backup server. pbs have a ssl from letsencrypt, is not a self generated ssl. it dont work without fingerprint :( and with after 3 months i must change on all proxmox clusters - any ideas?

hi, tonight we have the problem, thats the fingerprint of backup server was automatical changed. ssl was changed too. all proxmox nodes / servers dont have access after it, why all servers have other fingerprint key. why it do change automatical? what is problem and how can i solve it without...

No thats wront, well with old kernel it boots. i have disable VT-d in BIOS of Server, than it works fine. For other, i hope it help to solve your problems. regards

Hi, anyone a idea? regards

same issue after set entry and update and reboot. thats not solution :( with 6.5.* it works wihtout errors.

nice information, that i have overread. thanks i would test it. also only add in /etc/default/grub the entry: intel_iommu=off than update-grub and reboot right? regards

Hi all, in last kernels we have many Problems, We cant use only kernel 6.5.13-5-pve as last working kernel. All newer kernels >= 6.8.* have following error: ...iock error debug interrupt for reason 61 on cpu 0... system hang up and was not reachable.... only hard reboot with power off works...

hi, a small question, how can i create a prune-job for special vm-ids only. i would save for special vm-ids weekly abnd monthly backups 1x, but i dont find a option to set vm-ids on a job. on normal job all backups are in the job. any ideas here? regards

was a problem with pve kernel, older kernal and newer kernal works fine. dm error comes too in the used version... regards

Im Log fand ich noch: nmi iock error (debug interrupt ) for reason 71 on cpu 0 CPU ist aber OK.

hi all, same issu again on backup, network was unreachable after a while o running backup with newest proxmox version. any ideas to solve?

solution: delete all ssl in pve dir and under folders than renew ssl´s reboot node and cluster than add again works fine regards

# rm /etc/pve/pve-root-ca.pem and than # pvecm updatecerts --force on new node than restart than add again dont work, same issue.

hi all i get following error message if i add a new node on web gui. waiting for quorum...OK (re)generate node files generate new node certificate Certificate request self-signature ok subject=OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = phoenix.mydomain.de CA certificate and CA...

hi all in proxmox i have receive today a network firmware bug. all network ports a disabled/unreachable after start automatival backup, any ideas. log in attachment version here... i have make a upgrade after hard reboot ot node... after i have newer pve version as before... log are old vetsion...