Recent content by bfwdd

Ahhhhh, I found the culprit - creating new monitors in Ceph/Monitor DOES NOT update Storage Definition in Datacenter/Storage! So no monitor was found.... It would really be nice, if at least pvesm status is telling the root cause (got timeout from mon xyz) Best regards Konrad

Thanks, kernel pinned and yes we are replacing them. BUT pvesm status still shows my pools as inactive got timeout got timeout got timeout Name Type Status Total Used Available % backup nfs active 19260043264 11389441024...

Thanks, cluster is running 6.5, BUT: pvesm status got timeout got timeout got timeout Name Type Status Total Used Available % backup nfs active 19260043264 11389441024 7870602240 59.14% ceph-hdd rbd...

2024-05-13T17:24:37.057563+02:00 udo pvestatd[2406]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 51 retries 2024-05-13T17:24:42.105803+02:00 udo pvestatd[2406]: got timeout 2024-05-13T17:24:47.118265+02:00...

Hi, we are running proxmox+ceph since 2017, 15 hosts, amd AMD Opteron(tm) Processor 6380 (2 Sockets) + AMD EPYC 7513. After the latest update on 8.Mai 2024 three opteron hosts are locked - red X and (no ping, no ssh, all vms with grey (?) mark) after reboot everything ok. After 6 hours two...

Problem solved. Thanks.

Yes, same problem. ok - so I have to wait, thanks

Hi, we're are having a serious issues with live migration during upgrade to PVE 7.3 Our cluster is a 15 node cluster with external Ceph storage (no HA configured) Since 4 years we are updating our cluster with an ansible script: (Upgrade packages on host, migrate vms to spare host, reboot and...

Hey, The standard Config (not working): iptables PVEFW-IPS Chain PVEFW-IPS (1 references) pkts bytes target prot opt in out source destination 54 2k NFQUEUE all -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-out...

it looks like this post-up iptables -I PVEFW-IPS -m physdev --physdev-is-out -j NFQUEUE --queue-bypass

Hello everyone, according to WIKI the suricata integration take place under /etc/pve/firewall/<VMID>.fw, and the rule will be automatically added to the iptables . It is exactly my case however i am not receiving alerts at Suricata. this is how the rule looks like: 2 NFQUEUE all --...

I tried this but, it seems that "post-up " runs before the iptables service so the rule will not be added to the table chain

I am actually trying to link Pve-IPS output to suricata. I am running suricata using the NFQ mode and im sending traffic to suricata with the gateway-scenario using the following cmd: # iptables -I FORWARD -j PVEFW-IPS The problem is every time i restart the host the added rule is gone (-A...

After some minutes I got: 2021-08-12 14:48:06 ssh: connect to host 10.39.0.6 port 22: Connection timed out 2021-08-12 14:48:06 ERROR: migration aborted (duration 00:02:09): Can't connect to destination address using public key So I added a ssh rule and migration is working..., BUT shouldn't...

Hi, as soon as i enable firewall, live migration stops working. I have inserted on datacenter level one rule for ceph (macro) an the following: live migration (VM memory and local-disk data): 60000-60050 (TCP) Migration uses dedicated network (the same as corosync traffic)...