Recent content by NPK

No idea ? :(

Hi, I've added a new node on my cluster, but there are some problems : At boot, if I connect to this node, I see a question mark on all nodes, all VM - and no name appears for each VM, just "VM XXX" (where XXX is the VMID). But, I can see details about VM / node, it's working. After a few tens...

Nice, I didn't see it for storage in the pool. Tha'ts a good point ! The same one for network could be great, I hope in a next release :) So, I can close this topic. Thanks !

Edit : pools are on /pool/xxx, storage on /storage/xxx, network on /sdn/xxx... so I suppose administrator is for /pool/xxx only and that's why pool administrators can't configure network and storage. Is it a simple way to allow administrators to network & storage, instead of adding permissions...

Hi, Proxmox VE 8.0.4 (sorry, I can't upgrade this cluster as often as I want) I have many pools, one per user. Each user has "administrator" role for their pool. But, for VM in their pool, users can't see storage for adding a disk, can't see network bridges for adding network cards. They can...

I tried to restart some nodes, or just restart corosync.service & pve-cluster.service. Some nodes were alone in their cluster, some nodes don't... I finally decided to stop all 17 nodes and restart all : it was the solution, all nodes were up at restart, all in the same cluster. Yesterday and...

Some information this morning : another node is "green checked", in the same cluster with node-01 & node-08, while I haven't updated or restarted this node (uptime : 6 days so no power outage). Can I restart all nodes and after that, upgrade another nodes?

Yes, pve7to8 was executed without warnings. Not tried the --full mode (any interest if pve7to8 has no fail, no warning ?). I used this resource to upgrade. I upgraded 2 other plaforms before this one, with the same resource, and no problem with them. Can I restart all nodes and after that...

Additional information: I restarted node 08 (without upgrade, so node 01 is on PVE v8.0.4, other nodes on PVE v7.4.16). At boot, many changes : • I can login on GUI • pvescheduler on node 08 is dead (like node 01) • Node 01 and node 08 are on same cluster... Node 01: root@cloud-node-01:~#...

Here is journal from node 08. Like the other one yesterday, I replaced some details (CLOUD instead of the cluster real name, and internet.local instead of our real domain name), for privacy reasons.

Some additional informations: On upgraded node : root@cloud-node-01:~# systemctl status pvescheduler.service ○ pvescheduler.service - Proxmox VE scheduler Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; preset: enabled) Active: inactive (dead) On non upgraded...

Thanks for reply. On node 1 (upgraded) : auto lo iface lo inet loopback iface eno1 inet manual iface ens4f1 inet manual auto ens3f0 iface ens3f0 inet manual iface enx3a68dd057237 inet manual auto ens3f1 iface ens3f1 inet manual iface ens3f2 inet manual iface eno2 inet manual iface...

Hi, I have a problem with upgrade on my 17-nodes cluster. I've upgraded my first node to PVE 8.0.4 and at reboot, all other nodes are red cross marked. It's impossible to connect on other nodes by GUI (SSH is OK) : "please wait" during a long time and, finally, "Login failed". On node 1 ...

Hi, I have a PVE7 cluster with 3 nodes, and SAN storage by fiber channel for storing VMs. With the old kernel (5.15.53-1-pve), all is perfect : nodes can access to LUNs and VMs migration between nodes is OK. I updated the first node 2 weeks ago, to kernel 5-15-64-1-pve, and SAN is not working...

Solved ! I replaced download.proxmox.com with download.cdn.proxmox.com in sources.list, and it works... why ? I don't really know. Both seems to be the same : root@pve01:~# host download.proxmox.com download.proxmox.com is an alias for download.cdn.proxmox.com. download.cdn.proxmox.com is an...