Search results

Hi, is there another way for removing/changing a container hookscript than using vi on the container conf? I'd like to use pct for that or the WebUI (Proxmox 6.4)

Hi there, the new Proxmox7 Repos are named like this: ProxmoxVEEnterpriseDebianRepository:stable - in Version 6.x the name was ProxmoxVE This makes it laborious for our monitoring (prometheus node exporter with the apt update systemd timer with default settings) to distinguish between Debian...

"ext-all.js:22 GET https://an1-kvm01-bt01-b.XXXXXXX.net:8006/api2/json/nodes/an1-kvm01-bt01-d/storage/shared-ceph/rrddata?timeframe=hour&cf=AVERAGE 500 (RRD error: rrdcached@unix:/var/run/rrdcached.sock: rrd_fetch_r failed: opening...

It's just pvestatd thats complaining .. i can use the storage on all nodes

Restarting pvestatd does'nt change the situation - i already rebooted the machines .. no change either :(

Hi there, i did a fresh install of Proxmox 6.4 and initialized a CEPH Storage that is "unknown" to 2 of the 4 nodes in the cluster. Any clue why this is happening?

Hi there, any news on that - shouldnt be a big deal to provide those files with your custom rolled kernel. We could really use these information for our ansible scripts to automagically reboot the systems, as we try to manage all our PVE nodes with ansible.

/me plays "metallica hero of the day" for hannes :-)

How about extending the integrated tool instaed of relying on 3rd party stuff? Btw. json-pretty is also not human-readable/tie-compatible.

Hi, the text output does not show the (for me necessary) columns "name", but it's present in the json output. Any idea how the vm name can be shown in the human readable output?

Hi there just ran into an issue with a failing device (ssd decided to die) After rebooting the node, it won't bring up the interfaces, as the "ifupdown2-pre.service" wont succeed .. its basically a "/bin/udevadm settle" that waits till everything is okay. But due to the failing disk device...

Hi there, any plans for ever fixing this issue?

Hi There, i just got an experimental firmware release from mellanox for this specific card - and the "link down" issue is now gone. The startup of the vmbr with vlans is still somehow "shitty" as it still takes about a minute or so to bring up the nic (before it was about 3 minutes) - is this...

Hi Wolfgang, i'd apreciate if you could send me the scripts. I have a bunch of other Servers all with those standard PCIe Connect-X4 LX EN running with PVE, but none uses a vlan aware bridge - so i never bothered ;) Thanks for your help :cool:

AOc-m25g-m4sm - and no the firmware is a bit old and rusty according to aaron (see other ticket 146736)

hi there, just set up a cluster with a weird behaviour: it takes +5 Minutes to bring up the bridge after clicking apply configuration /etc/network/interfaces: auto lo iface lo inet loopback iface enp65s0f0 inet manual iface enp65s0f1 inet manual iface enp65s0f2 inet manual iface enp65s0f3...

Hi there, I'm a bit courious about relying on ifupdown2 when seeing what happened upstream to ifupdown2 (https://bugs.launchpad.net/ubuntu/+source/ifupdown2/+bug/1872590)

Sorry, but without an error message i can't help you ¯\_(ツ)_/¯ try sneaking around in /var/log/ceph and look at the logfiles, or try pinging nodes on the ceph public network, or check if the interface came up .. or or or

Do you have any error message? We have no problems with the same kernel and also mlx cards: root@prox2:~# dmesg |grep -e mlx [ 3.724951] mlx5_core 0000:af:00.0: firmware version: 14.23.1020 [ 3.724981] mlx5_core 0000:af:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [...

is proxy_ndp turned on on the host(firewallsettings)