Search results

We have a cluster of 10 PVE nodes, all running pve-manager/8.3.3 (running kernel: 6.8.12-8-pve) We noticed that all nodes in the cluster (BUT the one I am using to access the web UI) are showing grey question mark. We are able to test and reboot only two of the 10 nodes (since they are empty)...

My suggestions here: 1) use pve API instead of hard coded and expiring cookie In Nginx reverse proxy server use something like... proxy_set_header "Authorization" "PVEAPIToken=foo@pam!some-api=XXXXX-XXX-XXX-XXXX-XXXXXXX"; 2) here is the (php) code below that you can use as reference for code...

So over a year ago and I cant FULLY recall the solution but I do think it was the following: Proxmox really didnt like the VNC ticket being created on any other node in the cluster than the one that which hosts the VM/CT you are trying to do the vncproxy for. So long story short, forcing the...

Can you confirm what Motherboard, CPU and maybe additional network cards you have on your system that had issues. Also Can you try to add the proxmox non-subscription repo and do a dist-upgrade to latest and reboot and see if the issue comes back for you?

Did you end up finding the solution to this? additionally what CPU/RAM do you have?

I am seeing the same issue on a fresh install on a Dell R330 - Installing PVE 8.2 ISO = Kernal Panic on boot (post install) - Installing Debain 12 (fine) and then installing latest PVE = Kernal Panic on boot (post install) - Installing PVE 8.1 ISO = WORKS FINE - Upgrading PVE from 8.1 to 8.2 =...

Found the issue/solution. Since we have a few nodes in the cluster what I was doing was making a request to https://node1:8006 (picked at random from the pool of nodes) to create the vncproxy on a URI like /nodes/NODE2/lxc/{vmid}/vncproxy This means that the VNC started on NODE1 (I was...

Hi all I have a weird issue that I have one node in our cluster which is refusing to initialise a API novnc websocket (the other nodes work fine) In the logs I see the following: 2024-01-10T13:02:30.304869+13:00 cook pveproxy[2390675]: connect to 'localhost:5900' failed: Connection refused...

Hi all Been butting my head against the wall for the last few days over this issue. I was hoping if maybe someone has had the same and found a solution Summery: 1) We are using the API (tokens only, no cookies) to get the vnc credentials using the vncproxy endpoint with the added flag of...

Did you ever figure this out?

Did anyone end up finding a fix for this issue where the LXC containers show the hostnode CPU use

this is my output: $ smem --columns="vss command" -r | head -10 VSS Command 657056 /usr/sbin/corosync -f 323904 pvescheduler 329556 pve-ha-crm 329232 pve-ha-lrm 270292 pve-firewall 262108 pvestatd 366600 pveproxy worker 360748 pveproxy worker 838876 /usr/bin/pmxcfs...

Thats the thing... It doesnt show anything special? I have attached a screenshot of the htop order by MEM I am not too sure which processes are taking this memory? root @ elbrus ➜ ~ smem -tw Area Used Cache Noncache firmware/hardware 0...

We have a PVE node (7.1) with 32GB RAM We have only 6 LXC containers running on this node, each (according to PVE WebUI) is using approx. 100MB of ram (max allowed per LXC container is 512MB) So my question is... Why and where did all the RAM go? yes we run ZFS but seems thats only using 509.6 MiB

Sorry I should have been more clear, after reboot the PVE node is running the latest kernal (simple before I did a dist-upgrade and did not do a reboot hence you saw installed kernel not the same as running one) Should have clarified this also, yes we installed snmp on the node, and what I...

This is not intentional at all. even now after a reboot the same issue is still happening that we can not enter any CT. While looking at the journalctl nothing pops up at all. Some (totally unrelated) SNMP stuff comes up but thats not timed with me trying to issue the PCT command. Is there...

From the dmesg, when running modprobe xt_connlimit I get: [8898704.682293] BPF: type_id=77 bits_offset=1216 [8898704.683686] BPF: [8898704.684906] BPF:Invalid name [8898704.686122] BPF: [8898704.688775] failed to validate module [nf_conncount] BTF: -22 When running modprobe ipt_recent I...

@oguz From the node that can enter CT: From the node that CANT enter CT: ---- I doubled checked and the contents in `/etc/apparmor.d/lxc/` are identical in both nodes. You did mention that the error show means the CT doesnt have an apparmor profile is unconfined, the the thing that...

Hey everyone We have a 3 node cluster and for some reason two of the three nodes are refusing to enter any of the LXC containers with the pct enter XXXX command root @ pveNode1 ➜ / pct status 565 status: running root @ pveNode1 ➜ / pct config 565 arch: amd64 cores: 1 description: FooBar...

I cant seem to load them without an error root @ pve-node ➜ ~ modprobe ipt_recent modprobe: ERROR: could not insert 'xt_recent': Invalid argument root @ pve-node ➜ ~ modprobe xt_connlimit modprobe: ERROR: could not insert 'xt_connlimit': Invalid argument Tried reading online and some...