Another Cannot Access Web GUI

M

mbmast

New Member
May 8, 2024
9
1
3
Another Cannot Access Web GUI

I installed Proxmox a few months ago and have been using it without any issues until recently. Now, I am unable to access the Web GUI. Walking into my office I noticed none of the VMs running and Proxmox had crashed. After rebooting Proxmox, I am unable to access the Web GUI.

Here are some facts:

1. From my Remote Desktop Client machine, I can ping the Proxmox server running on another machine on the same LAN.
2. From the Proxmox server, I can ping the Remote Desktop Client machine.
3. I can SSH into my Proxmox server.
4. Lacking the GUI, from Proxmox's terminal session, I can start VMs and connect to them from my Remote Desktop Client machine. The VMs seem to operate normally.

Anticipating requests for information, here's the output from various commands:

Code: 
root@pve:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.0-1
proxmox-backup-file-restore: 3.2.0-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.1
pve-cluster: 8.0.6
pve-container: 5.0.10
pve-docs: 8.2.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.5
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2


Code: 
root@pve:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: ena>
     Active: active (running) since Mon 2024-08-05 16:56:08 PDT; 1 day 20h ago
    Process: 2135 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited>
    Process: 2137 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCC>
   Main PID: 2139 (pveproxy)
      Tasks: 3 (limit: 154112)
     Memory: 145.7M
        CPU: 39min 28.223s
     CGroup: /system.slice/pveproxy.service
             ├─  2139 pveproxy
             ├─564306 "pveproxy worker"
             └─564307 "pveproxy worker"


Aug 07 13:11:53 pve pveproxy[2139]: starting 1 worker(s)
Aug 07 13:11:53 pve pveproxy[2139]: worker 564306 started
Aug 07 13:11:53 pve pveproxy[564306]: unable to open log file '/var/log/pveprox>
Aug 07 13:11:53 pve pveproxy[564298]: worker exit
Aug 07 13:11:53 pve pveproxy[564297]: worker exit
Aug 07 13:11:53 pve pveproxy[2139]: worker 564298 finished
Aug 07 13:11:53 pve pveproxy[2139]: starting 1 worker(s)
Aug 07 13:11:53 pve pveproxy[2139]: worker 564297 finished
Aug 07 13:11:53 pve pveproxy[2139]: worker 564307 started
Aug 07 13:11:53 pve pveproxy[564307]: unable to open log file '/var/log/pveprox>


Code: 
root@pve:~# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: en>
     Active: active (running) since Mon 2024-08-05 16:56:07 PDT; 1 day 20h ago
    Process: 2089 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUC>
   Main PID: 2122 (pvedaemon)
      Tasks: 4 (limit: 154112)
     Memory: 148.5M
        CPU: 12.941s
     CGroup: /system.slice/pvedaemon.service
             ├─2122 pvedaemon
             ├─2123 "pvedaemon worker"
             ├─2124 "pvedaemon worker"
             └─2125 "pvedaemon worker"


Aug 05 16:56:07 pve systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Aug 05 16:56:07 pve pvedaemon[2122]: starting server
Aug 05 16:56:07 pve pvedaemon[2122]: starting 3 worker(s)
Aug 05 16:56:07 pve pvedaemon[2122]: worker 2123 started
Aug 05 16:56:07 pve pvedaemon[2122]: worker 2124 started
Aug 05 16:56:07 pve pvedaemon[2122]: worker 2125 started
Aug 05 16:56:07 pve systemd[1]: Started pvedaemon.service - PVE API Daemon.


Code: 
root@pve:~# ls -ld /var/log/pveproxy
drwx------ 2 www-data www-data 10 Aug  5 15:56 /var/log/pveproxy


Code: 
root@pve:~# ls -l /var/log/pveproxy
total 3516
-rw------- 1 root     root           0 Aug  5 15:28 access.log
-rw-r----- 1 www-data www-data 9084030 Aug  3 21:02 access.log.1
-rw------- 1 www-data www-data  463605 Aug  3 00:00 access.log.2.gz
-rw-r----- 1 www-data www-data  462625 Aug  2 00:00 access.log.3.gz
-rw-r----- 1 www-data www-data  466138 Aug  1 00:00 access.log.4.gz
-rw-r----- 1 www-data www-data  246476 Jul 31 00:00 access.log.5.gz
-rw-r----- 1 www-data www-data  320585 Jul 24 16:39 access.log.6.gz
-rw-r----- 1 www-data www-data  461483 Jul 24 00:00 access.log.7.gz
 
It may not be the only issue, but you can see that the access.log file has wrong user/group ownership
That can happen if you had file system corruption due to unexpected shutdown.
I'd recommend examining your system's journal (journalctl -b0). Its possible that the on-boot check fixed everything it could. Or you may be missing other data.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
mbmast said:
Aug 07 13:11:53 pve pveproxy[564306]: unable to open log file '/var/log/pveprox>
Click to expand...
The > seems like an indication that this is cut-off and hiding the actual error of why the file could not be opened, normally you can scroll to the right in that case, alternatively use journalctl -b -u pveproxy.service to get all systemd journal messages from that service from the current boot in an actual pager.

But from your last command output, the underlying problem seems to be that the log file is owned by root:

mbmast said:
-rw------- 1 root root 0 Aug 5 15:28 access.log
Click to expand...

As it's empty you can simply delete it, as the directory permissions seem to be correct so on the next start pveproxy should be able to create it:
rm /var/log/pveproxy/access.log

Then restart
systemctl restart pveproxy.service

The real question is naturally still open, why there is an empty access.log file owned by root.
 
Deleting access.log and then restarting fixed the problem.

The question remains, why was there an empty access.log file owned by root?
 
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
Back