[SOLVED] Proxmox missing most functionality

undeadrice

New Member
Jun 4, 2021
3
0
1
29
We've recently purchased a new server and installed proxmox on it followed by installing windows and linux vms.

Everything was working fine for the first few weeks and as of now, whenever I log onto proxmox all of the nodes vms are missing. The create VT/create CT and reboot/shutdowns are greyed and locked out and the only functionality that is left is Users/Api tokens.

am I missing something?
 
please post the output of the following commands
  • pveversion -v
  • systemctl status pveproxy pvedaemon pve-cluster pvestatd
 
pveversion:

Code:
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

systemctl

Code:
pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-06-04 09:16:13 CEST; 55min ago
  Process: 1326 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 1329 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 1331 (pveproxy)
    Tasks: 4 (limit: 9830)
   Memory: 167.3M
   CGroup: /system.slice/pveproxy.service
           ├─1331 pveproxy
           ├─1332 pveproxy worker
           ├─1334 pveproxy worker
           └─9387 pveproxy worker

Jun 04 09:16:13 serwer3 pveproxy[1331]: starting server
Jun 04 09:16:13 serwer3 pveproxy[1331]: starting 3 worker(s)
Jun 04 09:16:13 serwer3 pveproxy[1331]: worker 1332 started
Jun 04 09:16:13 serwer3 pveproxy[1331]: worker 1333 started
Jun 04 09:16:13 serwer3 pveproxy[1331]: worker 1334 started
Jun 04 09:16:13 serwer3 systemd[1]: Started PVE API Proxy Server.
Jun 04 10:10:51 serwer3 pveproxy[1333]: worker exit
Jun 04 10:10:51 serwer3 pveproxy[1331]: worker 1333 finished
Jun 04 10:10:51 serwer3 pveproxy[1331]: starting 1 worker(s)
Jun 04 10:10:51 serwer3 pveproxy[1331]: worker 9387 started

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-06-04 09:16:11 CEST; 55min ago
  Process: 1291 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
 Main PID: 1322 (pvedaemon)
    Tasks: 4 (limit: 9830)
   Memory: 153.5M
   CGroup: /system.slice/pvedaemon.service
           ├─1322 pvedaemon
           ├─1323 pvedaemon worker
           ├─1324 pvedaemon worker
           └─1325 pvedaemon worker

Jun 04 09:16:11 serwer3 pvedaemon[1322]: starting server
Jun 04 09:16:11 serwer3 pvedaemon[1322]: starting 3 worker(s)
Jun 04 09:16:11 serwer3 pvedaemon[1322]: worker 1323 started
Jun 04 09:16:11 serwer3 pvedaemon[1322]: worker 1324 started
Jun 04 09:16:11 serwer3 pvedaemon[1322]: worker 1325 started
Jun 04 09:16:11 serwer3 systemd[1]: Started PVE API Daemon.
Jun 04 09:24:34 serwer3 pvedaemon[1325]: <root@pam> successful auth for user 'kamil@pve'
Jun 04 09:39:35 serwer3 pvedaemon[1325]: <root@pam> successful auth for user 'kamil@pve'
Jun 04 09:54:35 serwer3 pvedaemon[1324]: <root@pam> successful auth for user 'kamil@pve'
Jun 04 10:09:37 serwer3 pvedaemon[1324]: <root@pam> successful auth for user 'kamil@pve'

● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-06-04 09:16:10 CEST; 55min ago
  Process: 1153 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 1175 (pmxcfs)
    Tasks: 7 (limit: 9830)
   Memory: 57.9M
   CGroup: /system.slice/pve-cluster.service
           └─1175 /usr/bin/pmxcfs

Jun 04 09:16:09 serwer3 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 04 09:16:10 serwer3 systemd[1]: Started The Proxmox VE cluster filesystem.

● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-06-04 09:16:11 CEST; 55min ago
  Process: 1289 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 1298 (pvestatd)
    Tasks: 1 (limit: 9830)
   Memory: 113.0M
   CGroup: /system.slice/pvestatd.service
           └─1298 pvestatd

Jun 04 09:16:10 serwer3 systemd[1]: Starting PVE Status Daemon...
Jun 04 09:16:11 serwer3 pvestatd[1298]: starting server
Jun 04 09:16:11 serwer3 systemd[1]: Started PVE Status Daemon.
 
Problem solved, the user i had been loggin on now does not have the requeried permissions, sorry for inconvience.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!