Help -- Node web interface dead

K

KcWeBBy

New Member
Sep 15, 2017
2
0
1
43
I am pretty sure I have messed up my config somehow.

I'm not to worried about it as I'm going to move off this server shortly, but I would like to get it back up and running (at least the three machines on it).

I currently have a 501 error every time I try to access my web interface via 8006.

just to check, I've verified the services are running:

Code: 
root@bmsipve:~# systemctl status pveproxy.service pvedaemon.service pve-cluster.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: active (running) since Thu 2017-09-14 22:43:39 CDT; 9min ago
  Process: 2599 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 2606 (pveproxy)
   CGroup: /system.slice/pveproxy.service
           ├─2606 pveproxy
           ├─2607 pveproxy worker
           ├─2608 pveproxy worker
           └─2609 pveproxy worker

Sep 14 22:43:39 bmsipve pveproxy[2606]: starting server
Sep 14 22:43:39 bmsipve pveproxy[2606]: starting 3 worker(s)
Sep 14 22:43:39 bmsipve pveproxy[2606]: worker 2607 started
Sep 14 22:43:39 bmsipve pveproxy[2606]: worker 2608 started
Sep 14 22:43:39 bmsipve pveproxy[2606]: worker 2609 started
Sep 14 22:43:39 bmsipve systemd[1]: Started PVE API Proxy Server.

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
   Active: active (running) since Thu 2017-09-14 22:43:38 CDT; 9min ago
  Process: 2583 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
 Main PID: 2593 (pvedaemon)
   CGroup: /system.slice/pvedaemon.service
           ├─2593 pvedaemon
           ├─2594 pvedaemon worker
           ├─2595 pvedaemon worker
           └─2596 pvedaemon worker

Sep 14 22:43:35 bmsipve systemd[1]: Starting PVE API Daemon...
Sep 14 22:43:37 bmsipve pvedaemon[2593]: starting server
Sep 14 22:43:37 bmsipve pvedaemon[2593]: starting 3 worker(s)
Sep 14 22:43:37 bmsipve pvedaemon[2593]: worker 2594 started
Sep 14 22:43:37 bmsipve pvedaemon[2593]: worker 2595 started
Sep 14 22:43:37 bmsipve pvedaemon[2593]: worker 2596 started
Sep 14 22:43:38 bmsipve systemd[1]: Started PVE API Daemon.

● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: active (running) since Thu 2017-09-14 22:42:34 CDT; 10min ago
  Process: 2146 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 1995 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 2144 (pmxcfs)
   CGroup: /system.slice/pve-cluster.service
           └─2144 /usr/bin/pmxcfs

Sep 14 22:42:34 bmsipve systemd[1]: Started The Proxmox VE cluster filesystem.


I have also checked the logs and I can't see anything of interest that leads me to something to config..

This was a cluster machine, but I have "unconfigured it" and it was running for a while.... I might have mixed up terminal windows from another clustered server and run some cluster commands, but didn't get errors.

I think the commands I ran related to moving the /etc/pve to /root/pve and then resetting the config somehow.

I have a backup of my qemu hosts and lxc, is there a way I can reset the config of the server without upsetting the storage & other host level config? (network, storage)?

Any diagnosis I can do to help you guys help me figure it out, before I just reinstall the server? (I'm scared to loose my data drive configs for my VM's)

here's the /var/log/pveproxy/access.log from 21:23 when it was working, to 21:28 when I broke it.

Code: 
192.168.1.183 - root@pam [14/Sep/2017:21:23:10 -0500] "GET /api2/json/nodes/bmsipve/qemu/601/status/current HTTP/1.1" 595 -
192.168.1.183 - - [14/Sep/2017:21:28:56 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:29:19 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:29:24 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:30:52 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:30:53 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:34:20 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:34:57 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:39:39 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:44:38 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:49:24 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:49:27 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:21:49:29 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:04:14 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:10:53 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:15:58 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:20:43 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:29:25 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:43:43 -0500] "GET / HTTP/1.1" 501 -
192.168.1.183 - - [14/Sep/2017:22:47:30 -0500] "GET /favicon.ico HTTP/1.1" 200 2336
192.168.1.183 - - [14/Sep/2017:22:47:39 -0500] "GET / HTTP/1.1" 501 -



Your help is appreciated..

Thanks!
 
does the journal say anything ?

Code: 
journalctl
?
 
dcsapak said:
does the journal say anything ?

Code: 
journalctl
?
Click to expand...



No, I was not able to see anything like errors in Journalctl either.... according to the log entries when you restart the server, everything works and no errors are logged...
 
Hi,
sure that's something to do with the config? Perhaps not all packets are installed correct?

What do you have changed? This information will be helpfull.

Can you post the output of following commands?
Code: 
pveversion -v

dpkg -l | grep pve

ls -l /etc/pve/nodes/bmsipve/

touch /etc/pve/xxx_deleteme ; rm /etc/pve/xxx_deleteme

ls -l /usr/share/pve-manager/touch/

curl --insecure https://localhost:8006
Udo
 
You must log in or register to reply here.
Top Bottom