Accidentally deleted /var/log cannot access web interface

paxmobile · 2024-09-21T00:31:38+0200

I feel secure backupping my VMs and LXCs but didn't think about a proxmox host backup and started my learning curve finding it easier to reinstall PM, allowing me to try new versions from time to time. Now I would prefer to solve this issue rather than reinstall but manually recreating the directory thru ssh and cli seems to much for me.
I can ssh the server on port 22 but it don't show up the web ui on port 8006.

pveversion -v > seems to be ok

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
root@paxserver:~#

Not being a linux master I copy'n'pasted the command below that I found in another post and many errors came out:

root@paxserver:/var/log# systemctl status pveproxy pvedaemon pve-cluster pvestatd
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-09-20 21:10:19 CEST; 2h 31min ago
Process: 1133 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1135 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 1137 (pveproxy)
Tasks: 4 (limit: 18944)
Memory: 135.8M
CPU: 3min 5.095s
CGroup: /system.slice/pveproxy.service
├─ 1137 pveproxy
├─103276 "pveproxy worker"
├─103277 "pveproxy worker"
└─103278 "pveproxy worker"

Sep 20 23:41:59 paxserver pveproxy[1137]: starting 2 worker(s)
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103276 started
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103277 started
Sep 20 23:41:59 paxserver pveproxy[103276]: unable to open log file '/var/log/pveproxy/access.log' - No such>
Sep 20 23:41:59 paxserver pveproxy[103277]: unable to open log file '/var/log/pveproxy/access.log' - No such>
Sep 20 23:41:59 paxserver pveproxy[103181]: worker exit
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103181 finished
Sep 20 23:41:59 paxserver pveproxy[1137]: starting 1 worker(s)
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103278 started
Sep 20 23:41:59 paxserver pveproxy[103278]: unable to open log file '/var/log/pveproxy/access.log' - No such>

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-09-20 21:10:18 CEST; 2h 31min ago
Process: 1094 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 1128 (pvedaemon)
Tasks: 4 (limit: 18944)
Memory: 137.1M
CPU: 1.188s
CGroup: /system.slice/pvedaemon.service
├─1128 pvedaemon
├─1129 "pvedaemon worker"
...skipping...
Active: active (running) since Fri 2024-09-20 21:10:19 CEST; 2h 31min ago
Process: 1133 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1135 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 1137 (pveproxy)
Tasks: 4 (limit: 18944)
Memory: 135.8M
CPU: 3min 5.095s
CGroup: /system.slice/pveproxy.service
├─ 1137 pveproxy
├─103276 "pveproxy worker"
├─103277 "pveproxy worker"
└─103278 "pveproxy worker"

Sep 20 23:41:59 paxserver pveproxy[1137]: starting 2 worker(s)
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103276 started
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103277 started
Sep 20 23:41:59 paxserver pveproxy[103276]: unable to open log file '/var/log/pveproxy/access.log' - No such>
Sep 20 23:41:59 paxserver pveproxy[103277]: unable to open log file '/var/log/pveproxy/access.log' - No such>
Sep 20 23:41:59 paxserver pveproxy[103181]: worker exit
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103181 finished
Sep 20 23:41:59 paxserver pveproxy[1137]: starting 1 worker(s)
Sep 20 23:41:59 paxserver pveproxy[1137]: worker 103278 started
Sep 20 23:41:59 paxserver pveproxy[103278]: unable to open log file '/var/log/pveproxy/access.log' - No such>

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-09-20 21:10:18 CEST; 2h 31min ago
Process: 1094 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 1128 (pvedaemon)
Tasks: 4 (limit: 18944)
Memory: 137.1M
CPU: 1.188s
CGroup: /system.slice/pvedaemon.service
├─1128 pvedaemon
├─1129 "pvedaemon worker"

Is there any command to restore the missing /var/log content ?

Thanks in advance, advise of an expert is very appreciated.

bbgeek17 · 2024-09-21T00:37:18+0200

Have you tried:
mkdir -p /var/log/pveproxy
mkdir -p /var/log/pve
chown -R www-data:www-data /var/log/pveproxy
systemctl try-reload-or-restart pvedaemon pveproxy pvestatd pvescheduler pve-ha-lrm

You could still have many more system issues. You may need to create and properly chown all these folders:

Code:

root@pve-1:~# ls -ald1 /var/log/*|grep ^d
drwxr-xr-x   2 root     root              4096 Sep  1 00:00 /var/log/apt
drwxr-----   3 root     root              4096 Apr 18 22:29 /var/log/blockbridge-proxmox
drwxrws--T   2 ceph     ceph              4096 Jan  9  2024 /var/log/ceph
drwxr-x---   2 _chrony  _chrony           4096 Apr 15 19:51 /var/log/chrony
drwxr-xr-x   2 root     root              4096 May  7  2023 /var/log/corosync
drwxr-x---   2 frr      frr               4096 Aug 30  2023 /var/log/frr
drwxr-xr-x   2 root     root              4096 May 24  2023 /var/log/glusterfs
drwxr-xr-x  45 root     root              4096 Sep 20 22:39 /var/log/ifupdown2
drwxr-sr-x+  3 root     systemd-journal   4096 Apr 15 19:51 /var/log/journal
drwxr-xr-x   2 root     root              4096 May  5  2023 /var/log/lxc
drwx------   2 root     root              4096 Apr 15 19:46 /var/log/private
drwxr-xr-x   3 root     root              4096 Apr 15 19:46 /var/log/pve
drwx------   2 www-data www-data          4096 Sep 19 00:00 /var/log/pveproxy
drwxr-xr-x   4 root     root              4096 Apr 19 02:52 /var/log/runit
drwxr-x---   2 root     adm               4096 Oct 10  2023 /var/log/samba
drwxr-xr-x   2 stunnel4 stunnel4          4096 Apr 18 21:58 /var/log/stunnel4
drwxr-xr-x   2 root     root              4096 May 13 17:42 /var/log/vzdump

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Search

Search

Accidentally deleted /var/log cannot access web interface

paxmobile

New Member

bbgeek17

Distinguished Member