[SOLVED] odd issue with greyout?

K

killmasta93

Renowned Member
Aug 13, 2017
985
62
93
32
Hi
Currently running proxmox in cluster and everything is working well. Whats odd is that i see the other hosts greyed out but i check each host and i can see each other VM no issue. I then thought it was that host but on every host i access they showed greyd out each one (see pictures) i checked the corosync shows fine i checked service pvestatd status and its fine also so not sure whats the issue there?


https://imgur.com/LjfAoeo.png

https://imgur.com/KJWaNsP.png


https://imgur.com/Er8Oa2x.png


Code: 
root@prometheus:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-07-10 22:12:12 -05; 4 months 25 days ago
  Process: 13194 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
 Main PID: 3095 (pveproxy)
    Tasks: 4 (limit: 7372)
   Memory: 162.6M
      CPU: 51min 46.963s
   CGroup: /system.slice/pveproxy.service
           ├─ 3095 pveproxy
           ├─13321 pveproxy worker
           ├─13322 pveproxy worker
           └─13323 pveproxy worker

Dec 04 06:25:03 prometheus pveproxy[3095]: starting 3 worker(s)
Dec 04 06:25:03 prometheus pveproxy[3095]: worker 13321 started
Dec 04 06:25:03 prometheus pveproxy[3095]: worker 13322 started
Dec 04 06:25:03 prometheus pveproxy[3095]: worker 13323 started
Dec 04 06:25:08 prometheus pveproxy[13644]: worker exit
Dec 04 06:25:08 prometheus pveproxy[36263]: worker exit
Dec 04 06:25:08 prometheus pveproxy[2712]: worker exit
Dec 04 06:25:08 prometheus pveproxy[3095]: worker 13644 finished
Dec 04 06:25:08 prometheus pveproxy[3095]: worker 36263 finished
Dec 04 06:25:08 prometheus pveproxy[3095]: worker 2712 finished
root@prometheus:~# service pvestatd status
● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-07-10 22:12:11 -05; 4 months 25 days ago
 Main PID: 3034 (pvestatd)
    Tasks: 1 (limit: 7372)
   Memory: 97.1M
      CPU: 23h 28min 41.756s
   CGroup: /system.slice/pvestatd.service
           └─3034 pvestatd

Jul 10 22:12:11 prometheus pvestatd[3034]: starting server
Jul 10 22:12:11 prometheus systemd[1]: Started PVE Status Daemon.
Nov 03 05:18:15 prometheus pvestatd[3034]: status update time (7.577 seconds)
Nov 07 20:35:15 prometheus pvestatd[3034]: vm 225 - unable to parse value of 'runningcpu' - unknown setting 'runningcpu'
Nov 11 09:21:36 prometheus pvestatd[3034]: status update time (10.122 seconds)
Nov 16 21:35:09 prometheus pvestatd[3034]: could not activate storage 'local-zfs', zfs error: use the form 'zpool import <pool | id> <newpool>' to give it a new name
Nov 16 21:35:09 prometheus pvestatd[3034]: status update time (7.398 seconds)
Nov 23 15:59:57 prometheus pvestatd[3034]: status update time (9.393 seconds)
Nov 23 16:00:12 prometheus pvestatd[3034]: status update time (14.391 seconds)
Nov 30 12:44:16 prometheus pvestatd[3034]: status update time (8.182 seconds)
Thank you
 
Fixed it running these commands

Code: 
service pvestatd daemon status
   service pvestatd status
   service pve-cluster stop
   service corosync stop
   service pvestatd stop
   service pveproxy stop
   service pvedaemon stop
   service pve-cluster start
   service corosync start
   service pvestatd start
   service pveproxy start
   service pvedaemon start
 
You must log in or register to reply here.
Top Bottom