Need deamon restart to access the WebGUI

S

Sessa45

Well-Known Member
Apr 3, 2018
103
0
56
32
hi Guys,

I have recently had the problem that access to the WebGUI does not work. When I restart the pvedeamon, everything works fine. After a few moments then again not (login, for example, no longer works).
Has somebody an idea what is the problem?

Thank you!
 
Check your server's logs (`journalctl -r`) and the status of the pvedaemon.service (`systemctl status -l pvedaemon.service`).
That should give you some more insight.
 
Unfortunately, there are no strange infos in the logfile.

systemd[1]: Starting PVE API Daemon...
pvedaemon[6136]: starting server
pvedaemon[6136]: starting 3 worker(s)
pvedaemon[6136]: worker 6139 started
pvedaemon[6136]: worker 6140 started
pvedaemon[6136]: worker 6141 started
systemd[1]: Started PVE API Daemon.
pvedaemon[6139]: <root@pam> successful auth for user 'root@pam'
pvedaemon[6139]: <root@pam> successful auth for user 'root@pam'
Click to expand...

After the login there is only the "load..." gif in the middle of the screen - thats it.
 
pvedaemon[17357]: kill worker 17360
pvedaemon[17357]: kill worker 17364
pvedaemon[17357]: kill worker 17361
pvedaemon[17357]: error stopping workers (will kill them now) - timeout
Click to expand...

I have found this. But what does this mean in relation to my problem?
Server is running fine without any issue.
 
Maybe it's a browser problem?
Try with a fresh browser/private mode
 
No, i already checked this.
When i try to login the load-gif is present for round about 20 seconds and then i get an "Login failed. Pleaste try again".
When i restart now the pvedaemon and try to login again, it works fine for a few seconds. Then, when i am logged in into the GUI, i only see the load-gif again. Not more.
 
Hm - please also check pveproxy.service and the logs in `/var/log/pveproxy` (there you have apache-style access logs for all requests)
Your https requests go to the pveproxy, and only some get transferred to the pvedaemon.

The question is why your pvedaemon workers run into timeouts (they have 10 seconds to shutdown cleanly, and get killed afterwards - that's the error message you posted).

Check your journal and the output of `dmesg` - that should show something if the server has problems
 
There are no stranger infos in the logs.
I can restart the pveproxy without any error.

The curios thing is that i can access the GUI after i reboot the pvedaemon (not the proxy).
But after a couple of seconds the load-gif is there an i can dont do anything.
Furtehrmore, the LXC and VMs on the left side right under the "server view" have an "?"... I think that`s because of the connection can not be established?

Hmmm... Very strange. Any idea to fix this?
 
Sessa45 said:
There are no stranger infos in the logs.
Click to expand...
I would consider the pvedaemon workers running into a timeout problematic.

Do you have a cluster or a single node/
You could also try to check pvestatd.

Afterwards i would check the network for problems
 
It is a single Node.
pvestatd is running fine.

What exactly should i check? I see no network problems....
 
Could you maybe share the journal output (start before restarting the daemons, and collect untill you run into the timeout/login problems) - maybe we can spot something odd there.

As for network-problems - I would check the interface statistics for errors (`ip -details -statistics a`) - and also try opening the javascript console in your browser while logging in - the network tab could show some information
 
I restart the services (vpeproxy & vpedaemon) and login into the GUI.
After that, the timeout occured. Output journal:

Dez 28 15:08:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:08:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:07:55 server.proxmox.de pveproxy[12375]: proxy detected vanished client connection
Dez 28 15:07:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56162).
Dez 28 15:07:31 server.proxmox.de pvedaemon[12153]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:17 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:11 server.proxmox.de pvedaemon[12381]: starting vnc proxy UPID:node3:0000305D:3F560560:5C262E0F:vncproxy:166:KVM_378@pve:
Dez 28 15:07:11 server.proxmox.de pvedaemon[12151]: <KVM_378@pve> starting task UPID:node3:0000305D:3F560560:5C262E0F:vncproxy:166:KVM_378@pve:
Dez 28 15:07:10 server.proxmox.de systemd[1]: Started PVE API Proxy Server.
Dez 28 15:07:10 server.proxmox.de pveproxy[12366]: worker 12375 started
Dez 28 15:07:10 server.proxmox.de pveproxy[12366]: worker 12372 started
Dez 28 15:07:10 server.proxmox.de pveproxy[12366]: worker 12368 started
Dez 28 15:07:10 server.proxmox.de pveproxy[12366]: starting 3 worker(s)
Dez 28 15:07:10 server.proxmox.de pveproxy[12366]: starting server
Dez 28 15:07:10 server.proxmox.de pvedaemon[12153]: <KVM_378@pve> end task UPID:node3:00002F8C:3F56018A:5C262E05:vncproxy:166:KVM_378@pve: OK
Dez 28 15:07:10 server.proxmox.de systemd[1]: Starting PVE API Proxy Server...
Dez 28 15:07:10 server.proxmox.de systemd[1]: Stopped PVE API Proxy Server.
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: server stopped
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: worker 21358 finished
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: worker 21362 finished
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: worker 21363 finished
Dez 28 15:07:09 server.proxmox.de pveproxy[21363]: worker exit
Dez 28 15:07:09 server.proxmox.de pveproxy[21362]: worker exit
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: server closing
Dez 28 15:07:09 server.proxmox.de pveproxy[21357]: received signal TERM
Dez 28 15:07:08 server.proxmox.de pvedaemon[12153]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:08 server.proxmox.de systemd[1]: Stopping PVE API Proxy Server...
Dez 28 15:07:07 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:06 server.proxmox.de pvedaemon[12151]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:05 server.proxmox.de pvedaemon[12151]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:04 server.proxmox.de pvedaemon[12153]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:02 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:01 server.proxmox.de pvedaemon[12172]: starting vnc proxy UPID:node3:00002F8C:3F56018A:5C262E05:vncproxy:166:KVM_378@pve:
Dez 28 15:07:01 server.proxmox.de pvedaemon[12153]: <KVM_378@pve> starting task UPID:node3:00002F8C:3F56018A:5C262E05:vncproxy:166:KVM_378@pve:
Dez 28 15:07:01 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:01 server.proxmox.de systemd[1]: Started PVE API Daemon.
Dez 28 15:07:01 server.proxmox.de pvedaemon[12146]: worker 12153 started
Dez 28 15:07:01 server.proxmox.de pvedaemon[12146]: worker 12151 started
Dez 28 15:07:01 server.proxmox.de pvedaemon[12146]: worker 12150 started
Dez 28 15:07:01 server.proxmox.de pvedaemon[12146]: starting 3 worker(s)
Dez 28 15:07:01 server.proxmox.de pvedaemon[12146]: starting server
Dez 28 15:07:00 server.proxmox.de systemd[1]: Starting PVE API Daemon...
Dez 28 15:07:00 server.proxmox.de systemd[1]: Stopped PVE API Daemon.
Dez 28 15:07:00 server.proxmox.de pvedaemon[24781]: Failed to run vncproxy.
Dez 28 15:07:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:07:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:06:59 server.proxmox.de pvedaemon[24643]: server stopped
Dez 28 15:06:59 server.proxmox.de pvedaemon[24643]: kill worker 24647
Dez 28 15:06:59 server.proxmox.de pvedaemon[24643]: error stopping workers (will kill them now) - timeout
Dez 28 15:06:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56146).
Dez 28 15:06:49 server.proxmox.de pvedaemon[24643]: worker 24646 finished
Dez 28 15:06:49 server.proxmox.de pvedaemon[24643]: worker 24648 finished
Dez 28 15:06:49 server.proxmox.de pvedaemon[24643]: server closing
Dez 28 15:06:49 server.proxmox.de pvedaemon[24643]: received signal TERM
Dez 28 15:06:48 server.proxmox.de systemd[1]: Stopping PVE API Daemon...
Dez 28 15:06:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:06:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:05:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56130).
Dez 28 15:05:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:05:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:04:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56114).
Dez 28 15:04:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:04:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:03:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56098).
Dez 28 15:03:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Dez 28 15:03:00 server.proxmox.de systemd[1]: Starting Proxmox VE replication runner...
Dez 28 15:02:51 server.proxmox.de systemd[1]: Started Check_MK (185.73.242.45:56082).
Dez 28 15:02:03 server.proxmox.de pvedaemon[24648]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:02:00 server.proxmox.de systemd[1]: Started Proxmox VE replication runner.
Click to expand...
 
Dez 28 15:07:08 server.proxmox.de systemd[1]: Stopping PVE API Proxy Server...
Dez 28 15:07:07 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:06 server.proxmox.de pvedaemon[12151]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:05 server.proxmox.de pvedaemon[12151]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:04 server.proxmox.de pvedaemon[12153]: <root@pam> successful auth for user 'root@pam'
Dez 28 15:07:02 server.proxmox.de pvedaemon[12150]: <root@pam> successful auth for user 'root@pam'
Click to expand...

quite a few logins in very short succession - do you have any other services connecting to your PVE apart from your browser? (you can check with `ss -tnp` ) - maybe some monitoring?

* you could also try to start pvedaemon/pveproxy in the foreground with the debug flag: `pveproxy start -debug`, `pvedaemon start -debug` (after stopping it beforehand) - maybe this will provide some insight
 
Stoiko Ivanov said:
quite a few logins in very short succession
Click to expand...
But only when I wanted to login. Before, I did not try to sign up.

Stoiko Ivanov said:
check with `ss -tnp`
Click to expand...
Many of this entries:

Code: 
State               Recv-Q        Send-Q                        Local Address:Port                             Peer Address:Port
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38090
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38184
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:37524
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38338
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:37666
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38254
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38194
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:38282
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:37548
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:37648
CLOSE-WAIT              426                  0                                         127.0.0.1:85                                       127.0.0.1:37722

Stoiko Ivanov said:
`pveproxy start -debug`
Click to expand...
6214: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x5641f7d84120)
6214: CLOSE FH10 CONN0
6214: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x5641f87fcea8)
6214: CLOSE FH10 CONN0
6213: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x5641f7d84120)
6213: CLOSE FH10 CONN0
6213: ACCEPT FH10 CONN1
6215: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x5641f87fe750)
6213: CLOSE FH10 CONN0
close connection AnyEvent::Handle=HASH(0x5641f7d84120)
6215: CLOSE FH10 CONN0
6213: ACCEPT FH10 CONN1
6215: ACCEPT FH10 CONN1
6213: ACCEPT FH12 CONN2
6215: ACCEPT FH11 CONN2
6213: ACCEPT FH14 CONN3
6214: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x5641f8982628)
6213: CLOSE FH12 CONN2
close connection AnyEvent::Handle=HASH(0x5641f7d83fd0)
6213: CLOSE FH14 CONN1
close connection AnyEvent::Handle=HASH(0x5641f7d84678)
6215: CLOSE FH10 CONN1
6215: ACCEPT FH10 CONN2
6214: ACCEPT FH12 CONN2
Click to expand...


Stoiko Ivanov said:
`pvedaemon start -debug`
Click to expand...
I tried and waited 5 minutes, but nothing happened. So i started the daemon with 'service pvedaemon start' witout any erros.
 
Sessa45 said:
CLOSE-WAIT 426 0 127.0.0.1:85 127.0.0.1:38090
Click to expand...
* which process is having the socket 127.0.0.1:38090 ? (the -p flag should give you an indication)
* do all of the CLOSE_WAIT sockets vanish once you stop pvedaemon?
* make sure there is nothing listening on port 85 after stopping pvedaemon (and nothing on 8006 after stopping pveproxy)
* pvedaemon with the debug flag does not output anything by default - but you do see once a connection to it is opened
 
Stoiko Ivanov said:
* do all of the CLOSE_WAIT sockets vanish once you stop pvedaemon?
Click to expand...
It seems like. There is now no CLOSE_WAIT when i execute 'ss -tnp'.


Stoiko Ivanov said:
* make sure there is nothing listening on port 85 after stopping pvedaemon (and nothing on 8006 after stopping pveproxy)
Click to expand...
I have checked this. When i stop the daemon there is nothing with port 85 and when i stop proxy there is nothing with port 8006.


Stoiko Ivanov said:
* pvedaemon with the debug flag does not output anything by default - but you do see once a connection to it is opened
Click to expand...
Alright! I have execute the command with the flag and try to login. Following output:

6594: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x5633112b87d8)
6594: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
6596: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x5633112bd628)
6595: CLOSE FH9 CONN0
close connection AnyEvent::Handle=HASH(0x5633112b8628)
6596: CLOSE FH9 CONN0
6594: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563310a59cc0)
6594: CLOSE FH9 CONN0
6596: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563310a59cc0)
6596: CLOSE FH9 CONN0
6594: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563310a68f30)
6594: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563310a691a0)
6595: CLOSE FH9 CONN0
6596: ACCEPT FH9 CONN1
6594: ACCEPT FH9 CONN1
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563310a59c60)
6595: CLOSE FH9 CONN0
close connection AnyEvent::Handle=HASH(0x5633112c2f68)
6594: CLOSE FH9 CONN0
6594: ACCEPT FH9 CONN1
6594: ACCEPT FH12 CONN2
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x5633112fa8f8)
6595: CLOSE FH9 CONN0
close connection AnyEvent::Handle=HASH(0x563311364768)
6594: CLOSE FH9 CONN1
6595: ACCEPT FH9 CONN1
6594: ACCEPT FH9 CONN2
close connection AnyEvent::Handle=HASH(0x563310a69188)
6595: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563311387538)
6595: CLOSE FH9 CONN0
6594: ACCEPT FH14 CONN3
close connection AnyEvent::Handle=HASH(0x56331136a540)
6594: CLOSE FH12 CONN2
close connection AnyEvent::Handle=HASH(0x56331137d390)
6594: CLOSE FH9 CONN1
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x5633113ab770)
6595: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x5633113ab938)
6595: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
close connection AnyEvent::Handle=HASH(0x563311380918)
6595: CLOSE FH9 CONN0
6595: ACCEPT FH9 CONN1
6595: ACCEPT FH12 CONN2
6595: ACCEPT FH14 CONN3
close connection AnyEvent::Handle=HASH(0x56331138c6b8)
6595: CLOSE FH14 CONN2
close connection AnyEvent::Handle=HASH(0x56331138c298)
6595: CLOSE FH12 CONN1
6595: ACCEPT FH12 CONN2
close connection AnyEvent::Handle=HASH(0x5633113565f8)
6595: CLOSE FH12 CONN1
6595: ACCEPT FH12 CONN2
close connection AnyEvent::Handle=HASH(0x56331138d150)
6595: CLOSE FH9 CONN1
Click to expand...


EDIT://
Now there are CLOSE-WAIT ...
 
Which process have an open connection to pvedaemon? (`ss -tnp |grep 85` run as root)
 
Here the output:

Code: 
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41430
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41646
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41808
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42098
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41294
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42158
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41380
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41896
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42146
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41546
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41576
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41644
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42318
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41900
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42096
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42024
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41340
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41346
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41574
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41282
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41496
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41692
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41736
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41738
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41544
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42270
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41678
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41504
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42232
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41776
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42294
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41876
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42054
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41952
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42266
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41954
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42112
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41452
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41564
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41614
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41366
CLOSE-WAIT  1        0               127.0.0.1:85             127.0.0.1:41268    users:(("pvedaemon worke",pid=16674,fd=9))
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41310
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41618
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41696
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41848
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41286
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41914
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41276
SYN-SENT    0        1               127.0.0.1:47542          127.0.0.1:85       users:(("pveproxy worker",pid=17204,fd=12))
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41820
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41790
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41974
CLOSE-WAIT  1        0               127.0.0.1:85             127.0.0.1:39776    users:(("pvedaemon worke",pid=16671,fd=9))
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41620
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41338
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41584
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42330
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41842
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41566
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42144
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41534
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42204
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41334
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41586
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41680
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41788
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42108
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41532
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41844
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41928
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42316
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41934
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41662
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41382
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42300
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42142
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41682
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42202
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41372
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42192
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41484
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41918
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41448
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42250
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41316
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42218
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41902
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41810
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41916
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41996
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41364
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41926
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41826
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41874
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41932
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41418
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41664
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41924
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41694
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41376
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41674
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41284
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41612
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42324
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41498
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42056
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42116
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41752
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42048
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41806
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41352
CLOSE-WAIT  1        0               127.0.0.1:85             127.0.0.1:39794    users:(("pvedaemon worke",pid=16670,fd=9))
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42312
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41978
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42008
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41824
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41478
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41774
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42182
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41542
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42026
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41300
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41296
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42028
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42252
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42082
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41502
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41750
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41850
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42140
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:41930
CLOSE-WAIT  426      0               127.0.0.1:85             127.0.0.1:42086
 
Any other ideas? Unfortunately, I can not access the VMs and CTs on the host.

Thank you so much for your support!
 
Alright, I've come a bit closer to my goal.

I have restarted the services pvedaemon, pveproxy and pvestatd. Login is clean. Now all VMs are displayed online. Furthermore, I can manage the VMs via the console and via the GUI.
Unfortunately, the problem persists with LXC.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom