SSH access, responds to pings on ip:8006, but can't access web GUI.

[jezzabell]

Hi All,

I haven't accessed my Proxmox web GUI for a while, while I have accessed other services that I have e.g. Octoprint.
I tried to log in via 192.168.2.5:8006, i.e. the usual IP address, but web access isn't responding (via my laptop or my phone)

I have:
- rebooted the server
- rebooted my router

Things that do work:
- Ping to 192.168.2.5:8006 (shows port is open using 'angry IP scanner')
- SSH access to 192.168.2.5 via root user and password
- ping TO my laptop from 192.168.2.5
- ping TO my router from 192.168.2.5
- ping TO google from 192.168.2.5
- Web access to Octoprint (VM on Proxmox)
- Web access to HomeAssistant (VM on Proxmox)

via SSH, IP address, gives:

4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:97:0e:78:a5:04 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.5/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3e97:eff:fe78:a504/64 scope link
       valid_lft forever preferred_lft forever

Potentially worth mentioning, on the server display, it has generally ALWAYS shown 192.168.100.2:8006 on the screen, even when I have previously connected to it via 2.5, noting that my subnet mask on my dhcp settings is and always has been 255.255.255.0


Any suggestions?
I appreciate your help!

 

[Chris]

Hi,

I tried to log in via 192.168.2.5:8006, i.e. the usual IP address, but web access isn't responding (via my laptop or my phone)

please check the status of the proxy and api daemons by running systemctl status pveproxy.service pvedaemon.service and check for possible firewall rules interfering with the traffic.

Potentially worth mentioning, on the server display, it has generally ALWAYS shown 192.168.100.2:8006 on the screen, even when I have previously connected to it via 2.5, noting that my subnet mask on my dhcp settings is and always has been 255.255.255.0

Double check your /etc/hosts configuration, maybe you have an incorrect IP configured there. Also check the tail -n 10 /var/log/pveproxy/access.log

 

[jezzabell]

Hi Chris,
Thank you for your reply!

Here is:systemctl status pveproxy.service pvedaemon.service:

root@home:~# systemctl status pveproxy.service pvedaemon.service
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
lines 1-17...skipping...
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22137 started
Dec 12 16:18:06 home pveproxy[22137]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory
Dec 12 16:18:06 home pveproxy[22113]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22113 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22138 started
Dec 12 16:18:06 home pveproxy[22138]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory

● pvedaemon.service - PVE API Daemon
lines 1-27...skipping...
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22137 started
Dec 12 16:18:06 home pveproxy[22137]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory
Dec 12 16:18:06 home pveproxy[22113]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22113 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22138 started
Dec 12 16:18:06 home pveproxy[22138]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
lines 1-28...skipping...
● pveproxy.service - PVE API Proxy Server
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22137 started
Dec 12 16:18:06 home pveproxy[22137]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory
Dec 12 16:18:06 home pveproxy[22113]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22113 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22138 started
Dec 12 16:18:06 home pveproxy[22138]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
lines 1-28...skipping...
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22137 started
Dec 12 16:18:06 home pveproxy[22137]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory
Dec 12 16:18:06 home pveproxy[22113]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22113 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22138 started
Dec 12 16:18:06 home pveproxy[22138]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:34 AEDT; 1h 48min ago
    Process: 1042 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1075 (pvedaemon)
      Tasks: 4 (limit: 9227)
     Memory: 148.2M
        CPU: 2.180s
lines 1-34...skipping...
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:36 AEDT; 1h 48min ago
    Process: 1080 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1082 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1084 (pveproxy)
      Tasks: 4 (limit: 9227)
     Memory: 202.4M
        CPU: 4min 44.786s
     CGroup: /system.slice/pveproxy.service
             ├─ 1084 pveproxy
             ├─22135 pveproxy worker
             ├─22137 pveproxy worker
             └─22138 pveproxy worker

Dec 12 16:18:06 home pveproxy[22112]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22112 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22137 started
Dec 12 16:18:06 home pveproxy[22137]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory
Dec 12 16:18:06 home pveproxy[22113]: worker exit
Dec 12 16:18:06 home pveproxy[1084]: worker 22113 finished
Dec 12 16:18:06 home pveproxy[1084]: starting 1 worker(s)
Dec 12 16:18:06 home pveproxy[1084]: worker 22138 started
Dec 12 16:18:06 home pveproxy[22138]: unable to open log file '/var/log/pveproxy/access.log' - No such file or directory

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-12-12 14:29:34 AEDT; 1h 48min ago
    Process: 1042 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1075 (pvedaemon)
      Tasks: 4 (limit: 9227)
     Memory: 148.2M
        CPU: 2.180s
     CGroup: /system.slice/pvedaemon.service
             ├─1075 pvedaemon
             ├─1076 pvedaemon worker
             ├─1077 pvedaemon worker

root@home:~#

I don't have any firewall rules that I am aware of, my DHCP router was factory reset last night, and I can access HA / Octoprint.

I updated the hosts file to (as it was incorrect with the .200.2 IP)

127.0.0.1 localhost.localdomain localhost
192.168.2.5 home.arpa home

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Re: access.log: tail: cannot open '/var/log/pveproxy/access.log' for reading: No such file or directory

I've restarted the server, but still can't access the GUI.

here's my IP link

root@home:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 3c:97:0e:78:a5:04 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 9c:4e:36:a4:36:dc brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 3c:97:0e:78:a5:04 brd ff:ff:ff:ff:ff:ff
5: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 66:fd:da:13:36:c4 brd ff:ff:ff:ff:ff:ff
6: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 26:96:cb:a8:c9:9f brd ff:ff:ff:ff:ff:ff
7: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 72:cb:b8:90:81:09 brd ff:ff:ff:ff:ff:ff
8: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether f6:0d:5a:52:bd:bd brd ff:ff:ff:ff:ff:ff
9: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether 06:ef:47:9c:17:27 brd ff:ff:ff:ff:ff:ff

Any suggestions from here?

edit: I static assign the IP address from the router configuration end (I'm not sure why its called 'wistron')

And this is what my interfaces config file looks like:

auto lo
iface lo inet loopback

iface enp0s25 inet manual

# auto wlp3s0



auto vmbr0
iface vmbr0 inet static
        address 192.168.2.5/24
        gateway 192.168.2.3
        bridge-ports enp0s25 wlp3s0
        bridge-stp off
        bridge-fd 0


iface wlp3s0 inet manual

Thanks again!

 

[Chris]

Re: access.log: tail: cannot open '/var/log/pveproxy/access.log' for reading: No such file or directory

Might be the cause, as the pveproxy worker processes seem to be unable to open that file. Please check the permissions of

stat /var/log/pveproxy
ls -l

The folder should show ownership www-data:www-data and permissions 0700. Did you recently change something related to the contents of the var folder?

 

[jezzabell]

Hi!
Thanks again.
The missing logs continue.

root@home:~# stat /var/log/pveproxy stat: cannot statx '/var/log/pveproxy': No such file or directory

Content from /var/log/

root@home:/var/log# ls -l
total 579216
-rw-r--r-- 1 root    root         1100 Dec 12 17:07 alternatives.log
-rw-r--r-- 1 root    root          275 Dec 11 18:45 alternatives.log.1
-rw-r--r-- 1 root    root          152 Jul 27 21:46 alternatives.log.2.gz
drwxr-xr-x 2 root    root         4096 Dec 12 00:00 apt
-rw-r----- 1 root    adm         68516 Dec 13 13:07 auth.log
-rw-r----- 1 root    adm         37226 Dec  9 23:17 auth.log.1
-rw-r----- 1 root    adm          2323 Dec  2 23:17 auth.log.2.gz
-rw-r----- 1 root    adm          2279 Nov 25 23:17 auth.log.3.gz
-rw-r----- 1 root    adm          7131 Nov 18 23:17 auth.log.4.gz
-rw-rw---- 1 root    utmp        43392 Dec 12 18:36 btmp
-rw-rw---- 1 root    utmp            0 Nov  1 00:00 btmp.1
drwxr-x--- 2 _chrony _chrony      4096 Jul 27 21:36 chrony
-rw-r----- 1 root    adm      84492275 Dec 13 13:09 daemon.log
-rw-r----- 1 root    adm     168946718 Dec 10 00:01 daemon.log.1
-rw-r----- 1 root    adm      11223134 Dec  3 00:01 daemon.log.2.gz
-rw-r----- 1 root    adm      11183068 Nov 26 00:01 daemon.log.3.gz
-rw-r----- 1 root    adm      11139402 Nov 19 00:01 daemon.log.4.gz
-rw-r----- 1 root    adm          7280 Dec 12 17:07 debug
-rw-r----- 1 root    adm          1820 Dec 11 18:45 debug.1
-rw-r----- 1 root    adm      15486269 Jul 27 21:46 debug.2.gz
-rw-r--r-- 1 root    root            0 Dec 12 00:00 dpkg.log
-rw-r--r-- 1 root    root          797 Dec 11 20:26 dpkg.log.1
-rw-r----- 1 root    adm        383651 Dec 12 22:46 kern.log
-rw-r----- 1 root    adm        109609 Dec 11 23:52 kern.log.1
-rw-r----- 1 root    adm           232 Nov 13 13:10 kern.log.2.gz
-rw-r----- 1 root    adm           691 Nov 11 02:12 kern.log.3.gz
-rw-r----- 1 root    adm           746 Nov  6 01:02 kern.log.4.gz
-rw-rw-r-- 1 root    utmp          292 Jul 27 21:45 lastlog
-rw-r----- 1 root    adm          1363 Dec 12 17:07 mail.info
-rw-r----- 1 root    adm           343 Dec 11 18:45 mail.info.1
-rw-r----- 1 root    adm           262 Jul 27 21:46 mail.info.2.gz
-rw-r----- 1 root    adm          1363 Dec 12 17:07 mail.log
-rw-r----- 1 root    adm           343 Dec 11 18:45 mail.log.1
-rw-r----- 1 root    adm           262 Jul 27 21:46 mail.log.2.gz
-rw-r----- 1 root    adm        479975 Dec 12 22:46 messages
-rw-r----- 1 root    adm           145 Dec  3 00:11 messages.1
-rw-r----- 1 root    adm           141 Nov 26 00:11 messages.2.gz
-rw-r----- 1 root    adm           140 Nov 19 00:11 messages.3.gz
-rw-r----- 1 root    adm           323 Nov 13 13:10 messages.4.gz
drwx------ 2 root    root         4096 Jul 27 21:36 private
drwxr-xr-x 3 root    root         4096 Jul 27 21:26 pve
-rw-r--r-- 1 root    root        28908 Dec 13 04:04 pveam.log
-rw-r--r-- 1 root    root        51722 Nov 21 01:17 pveam.log.0
-rw-r----- 1 root    adm            55 Dec 13 00:01 pve-firewall.log
-rw-r----- 1 root    adm           895 Dec 13 00:01 pve-firewall.log.1
-rw-r----- 1 root    adm           147 Dec 12 00:00 pve-firewall.log.2.gz
-rw-r----- 1 root    adm           122 Dec 11 00:00 pve-firewall.log.3.gz
-rw-r----- 1 root    adm           128 Dec 10 00:00 pve-firewall.log.4.gz
-rw-r----- 1 root    adm           122 Dec  9 00:01 pve-firewall.log.5.gz
-rw-r----- 1 root    adm           128 Dec  8 00:01 pve-firewall.log.6.gz
-rw-r----- 1 root    adm           128 Dec  7 00:00 pve-firewall.log.7.gz
-rw-r----- 1 root    adm      85000543 Dec 13 13:09 syslog
-rw-r----- 1 root    adm     168965866 Dec 10 00:01 syslog.1
-rw-r----- 1 root    adm      11248872 Dec  3 00:01 syslog.2.gz
-rw-r----- 1 root    adm      11207523 Nov 26 00:01 syslog.3.gz
-rw-r----- 1 root    adm      11163944 Nov 19 00:01 syslog.4.gz
-rw-r----- 1 root    adm           880 Dec 12 17:07 user.log
-rw-r----- 1 root    adm           372 Dec 11 18:45 user.log.1
-rw-r----- 1 root    adm       1001320 Jul 29 15:59 user.log.2.gz
-rw-rw-r-- 1 root    utmp       605952 Dec 12 17:07 wtmp

pveversion -v gives:

proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.0
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-2
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

I don't have a pve-proxy ?

 

[jezzabell]

Might be the cause, as the pveproxy worker processes seem to be unable to open that file. Please check the permissions of

stat /var/log/pveproxy
ls -l

The folder should show ownership www-data:www-data and permissions 0700. Did you recently change something related to the contents of the var folder?

My other reply is in review, needing moderator approval? In short though, that pveproxy folder doesn't exist. and pveproxy isn't listed via pveversion -v. The whole output is in the pending post.

To answer your question, I haven't changed anything for months.

And the only things I've changed when setting up the operational VMs were:
- VM specific hardware pass through, including webcams (which work and are visible on Octoprint), this wasn't super straight forward (followed this: https://asokolsky.github.io/proxmox/lxc-octoprint.html - mainly had edits to : /etc/pve/nodes and /etc/udev/
- Network config to make their web guis accessible via the VM IPs.

I hope that helps?

 

[Chris]

I don't have a pve-proxy ?

pveproxy is installed as part of the pve-manager package, please verify its integrity via dpkg -V pve-manager. If you get no output than everything is fine.

stat: cannot statx '/var/log/pveproxy': No such file or directory

Well something seems to have deleted the directroy.

You can recreate it and restart the proxy service via:

mkdir /var/log/pveproxy
chown www-data:www-data /var/log/pveproxy
chmod 0700 /var/log/pveproxy
systemctl restart pveproxy.service

 

[jezzabell]

pveproxy is installed as part of the pve-manager package, please verify its integrity via dpkg -V pve-manager. If you get no output than everything is fine

I tried this and...

dpkg -V pve-manager
??5?????? c /etc/apt/sources.list.d/pve-enterprise.list

You can recreate it and restart the proxy service via:

mkdir /var/log/pveproxy
chown www-data:www-data /var/log/pveproxy
chmod 0700 /var/log/pveproxy
systemctl restart pveproxy.service

This got it working again! All sorted now. Thanks so much.
Is there anyway to look back and see what caused the issue, or when/how the directory etc was deleted?

Is there anything else I should check that could be missing? Or a way to bulk check vs package by package?

 

[Chris]

I tried this and...

dpkg -V pve-manager
??5?????? c /etc/apt/sources.list.d/pve-enterprise.list

This got it working again! All sorted now. Thanks so much.
Is there anyway to look back and see what caused the issue, or when/how the directory etc was deleted?

Is there anything else I should check that could be missing? Or a way to bulk check vs package by package?

Glad this solved your issue.

You can/should check the systemd journal for the time when the issue first arouse, this could give you at least a timeframe to look for e.g. ssh logins, further error messages, scripts executed at that time, ... journalctl -r gives you a paginated view to search/scroll the logs.

You can double check the package integrity of the packages listed in the output of pveversion -v via the dpkg -V <package> command. This should give you the files changed with respect to the package state. Or use debsums -s, which you will however need to install first.