Proxmox VE not starting anymore - Webinterface not reachable - postfix-problem?

Moguai1978

New Member
Nov 24, 2022
7
0
1
Hello,

after a simple reboot my proxmox ve-Server did not start anymore and the webinterface is not reachable. I did not do anything on system itself.

Syslog says:
Code:
Nov 24 10:42:34 proxmox systemd[1]: Removed slice system-postfix.slice.
Nov 24 10:42:34 proxmox systemd[1]: postfix.service: Succeeded.
Nov 24 10:43:24 proxmox postfix/postsuper[878]: fatal: scan_dir_push: open directory defer: Permission denied
Nov 24 10:43:25 proxmox postfix/postfix-script[889]: fatal: Postfix integrity check failed!
Nov 24 10:43:26 proxmox systemd[1]: postfix@-.service: Control process exited, code=exited, status=1/FAILURE
Nov 24 10:43:26 proxmox systemd[1]: postfix@-.service: Failed with result 'exit-code'.

Any idea or help what went wrong or happened with my system?

Thanks a lot in advice!
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com
Hi,

Is the PVE SSH reachable? if yes - please check from the following:

- Syslog before the server reboots in 30 minutes, at least
- Check if the :8006 port is open (if it's) you can test cURL command

Please also provide us with the output of pveversion -v
 

Moguai1978

New Member
Nov 24, 2022
7
0
1
Hi,

here we are ... syslog is attached.

Port seems to be open:
Code:
root@proxmox:~# nmap localhost -p 8006 -Pn -T5
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-24 18:15 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000035s latency).
rDNS record for 127.0.0.1: localhost.localdomain

PORT     STATE SERVICE
8006/tcp open  wpl-analytics

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

What u mean with test cURL command?

output of pveversion -v:
Code:
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-8
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 

Attachments

  • proxmox_syslog.txt
    570.7 KB · Views: 1

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com
What u mean with test cURL command?
I mean, see the response using the below command:
Bash:
curl -k https://PVE-IP:8006/ | grep title


Thank you for the syslog!

From the Syslog attached, I can see a lot of the following messages, e.g:

Code:
Nov 24 18:09:13 proxmox pveproxy[1792]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Nov 24 18:09:13 proxmox pveproxy[1793]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Nov 24 18:09:13 proxmox pveproxy[1794]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
I would check if the `/var/log/pveproxy/access.log` has a right permission (ls -lh /var/log/pveproxy/access.log)
 

Moguai1978

New Member
Nov 24, 2022
7
0
1
Thanks for your help.

With the curl command I get no reaction till I stop it with strg+c/control+c:

Code:
root@proxmox:~# curl -k https://192.168.2.3:8006/  grep title
^C
root@proxmox:~#nmap localhost -p 8006 -Pn -T5
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-25 23:46 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000033s latency).
rDNS record for 127.0.0.1: localhost.localdomain

PORT     STATE SERVICE
8006/tcp open  wpl-analytics

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds

Permission on access.log looks like following:
Code:
ls -al /var/log/pveproxy/access.log
-rw-r----- 1 www-data www-data 0 25. Nov 00:01 /var/log/pveproxy/access.log
Is this the right permission or is there something wrong?
 

Moguai1978

New Member
Nov 24, 2022
7
0
1
Can you nmap the host IP instead of the localhost on port 8006?
For sure:
Code:
root@proxmox:~# nmap 192.168.2.3 -p 8006 -Pn -T5
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-28 12:31 CET
Nmap scan report for proxmox.lenovo.pve (192.168.2.3)
Host is up (0.000034s latency).

PORT     STATE SERVICE
8006/tcp open  wpl-analytics

Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds

Is it easier for you to write in german? Or should we better use english further?
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com

Moguai1978

New Member
Nov 24, 2022
7
0
1
Sorry, da hat das copy & paste mir wohl einen Streich gespielt.

Code:
root@proxmox:~# curl -k https://192.168.2.3:8006/ | grep title
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:01:24 --:--:--     0

Ich habe dann nach 1 Minute und 24 Sekunden mit Strg + C abgebrochen.
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com
Kannst du mal versuchen, um zu pveproxy neu starten?

Code:
systemctl start pveproxy.service

Wenn auch nicht hilft, poste bitte die Ausgabe von systemctl status pveproxy.service
 

Moguai1978

New Member
Nov 24, 2022
7
0
1
Kannst du mal versuchen, um zu pveproxy neu starten?
Das schaut so als als hätte das nicht funktioniert:
Code:
root@proxmox:~# systemctl start pveproxy.service
root@proxmox:~# curl -k https://192.168.2.3:8006/ | grep title
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:31 --:--:--     0^C
Ich hatte dann wieder nach 31 Sekunden mit Strg + C abgebrochen.

Die Ausgabe von
Code:
systemctl status pveproxy.service
habe ich wieder als Textdatei angehängt. Da taucht wieder häufig der Hinweis auf das fehlende Zugriffsrecht auf /var/log/pveproxy/access.log auf.
 

Attachments

  • status_pveproxy.txt
    33.5 KB · Views: 2

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com
Hallo,

Die Meldung "unable to open log file '/var/log/pveproxy/access.log' - Permission denied" besagt, dass keine Permission vorhanden ist. Kannst du bitte die Permission für den gesamten Ordner überprüfen?

Bash:
ls -al /var/log/pveproxy/

Es sollte wie die folgenden Permissions sein

Bash:
~ ls -al /var/log/pveproxy/
total 6824
drwx------  2 www-data www-data    4096 Nov 28 09:53 .
drwxr-xr-x 24 root     root        4096 Nov 28 09:56 ..
-rw-r-----  1 www-data www-data 2240493 Nov 28 15:12 access.log

Hast du versucht, den Server neu zu starten?
 

Moguai1978

New Member
Nov 24, 2022
7
0
1
Hallo,

Die Meldung "unable to open log file '/var/log/pveproxy/access.log' - Permission denied" besagt, dass keine Permission vorhanden ist. Kannst du bitte die Permission für den gesamten Ordner überprüfen?
Die Zugriffsrechte sehen wie folgt aus:
Code:
root@proxmox:~# ls -al /var/log/pveproxy/
insgesamt 1048
drwx------  2 root     root       4096 25. Nov 00:01 .
drwxr-xr-x 16 root     root       4096 28. Nov 12:29 ..
-rw-r-----  1 www-data www-data      0 25. Nov 00:01 access.log
-rw-r-----  1 root     root      82293 24. Nov 09:56 access.log.1
-rw-r-----  1 root     root      65705 22. Nov 02:42 access.log.2.gz
-rw-r-----  1 root     root     903600 22. Nov 00:00 access.log.3.gz
root@proxmox:~# ls -al /var/log/pve*
-rw-r--r-- 1 root root 10720 28. Nov 13:43 /var/log/pveam.log
-rw-r----- 1 root adm     55 28. Nov 12:29 /var/log/pve-firewall.log
-rw-r----- 1 root adm    358 28. Nov 12:29 /var/log/pve-firewall.log.1
-rw-r----- 1 root adm    168 27. Nov 04:16 /var/log/pve-firewall.log.2.gz
-rw-r----- 1 root root   298 25. Nov 00:01 /var/log/pve-firewall.log.3.gz
-rw-r----- 1 root root   124 24. Nov 00:00 /var/log/pve-firewall.log.4.gz
-rw-r----- 1 root root   124 23. Nov 00:00 /var/log/pve-firewall.log.5.gz
-rw-r--r-- 1 root root   127 22. Nov 00:00 /var/log/pve-firewall.log.6.gz

/var/log/pve:
insgesamt 12
drwxr-xr-x  3 root root 4096 20. Nov 00:28 .
drwxr-xr-x 16 root root 4096 28. Nov 12:29 ..
drwxr-xr-x 18 root root 4096 28. Nov 13:43 tasks

/var/log/pveproxy:
insgesamt 1048
drwx------  2 root     root       4096 25. Nov 00:01 .
drwxr-xr-x 16 root     root       4096 28. Nov 12:29 ..
-rw-r-----  1 www-data www-data      0 25. Nov 00:01 access.log
-rw-r-----  1 root     root      82293 24. Nov 09:56 access.log.1
-rw-r-----  1 root     root      65705 22. Nov 02:42 access.log.2.gz
-rw-r-----  1 root     root     903600 22. Nov 00:00 access.log.3.gz
root@proxmox:~# ls -al /var/log/
insgesamt 49504
drwxr-xr-x  16 root root                4096 28. Nov 12:29 .
drwxr-xr-x  11 root root                4096  4. Mai 2022  ..
-rw-r--r--   1 root root               21830 28. Nov 12:29 alternatives.log
drwxr-xr-x   2 root root                4096 27. Nov 04:16 apt
-rw-r-----   1 root root                4113 28. Nov 17:17 auth.log
-rw-r-----   1 root root               55810 27. Nov 04:16 auth.log.1
-rw-rw----   1 root utmp                2688 28. Nov 12:30 btmp
drwxrws--T   2 root root                4096  8. Mär 2022  ceph
drwxr-x---   2 root root                4096 20. Nov 00:30 chrony
drwxr-xr-x   2 root root                4096  9. Nov 2021  corosync
-rw-r-----   1 root root             5104742 28. Nov 17:53 daemon.log
-rw-r-----   1 root root            17873759 27. Nov 04:16 daemon.log.1
-rw-r-----   1 root root                2005 28. Nov 13:43 debug
-rw-r-----   1 root root               24938 27. Nov 04:16 debug.1
-rw-r--r--   1 root root              468811 27. Nov 04:16 dpkg.log
-rw-r--r--   1 root root             2049472 20. Nov 00:55 faillog
-rw-r--r--   1 root root                1098 20. Nov 00:28 fontconfig.log
drwxr-xr-x   2 root root                4096 18. Mai 2021  glusterfs
drwxr-sr-x+  3 root systemd-journal     4096 20. Nov 00:30 journal
-rw-r-----   1 root root               90379 28. Nov 12:29 kern.log
-rw-r-----   1 root root             1192863 27. Nov 04:16 kern.log.1
-rw-rw-r--   1 root utmp            18701432 28. Nov 12:30 lastlog
drwxr-xr-x   2 root root                4096 20. Nov 00:30 lxc
-rw-r-----   1 root adm                  294 28. Nov 12:29 mail.err
-rw-r-----   1 root adm                 2230 27. Nov 04:16 mail.err.1
-rw-r-----   1 root root                 294 28. Nov 12:29 mail.info
-rw-r-----   1 root root                5765 27. Nov 04:16 mail.info.1
-rw-r-----   1 root root                 294 28. Nov 12:29 mail.log
-rw-r-----   1 root root                5765 27. Nov 04:16 mail.log.1
-rw-r-----   1 root root                 294 28. Nov 12:29 mail.warn
-rw-r-----   1 root root                4260 27. Nov 04:16 mail.warn.1
-rw-r-----   1 root root               87835 28. Nov 12:29 messages
-rw-r-----   1 root root             1168929 27. Nov 04:16 messages.1
drwx------   2 root root                4096 20. Nov 00:28 private
drwxr-xr-x   3 root root                4096 20. Nov 00:28 pve
-rw-r--r--   1 root root               10720 28. Nov 13:43 pveam.log
-rw-r-----   1 root adm                   55 28. Nov 12:29 pve-firewall.log
-rw-r-----   1 root adm                  358 28. Nov 12:29 pve-firewall.log.1
-rw-r-----   1 root adm                  168 27. Nov 04:16 pve-firewall.log.2.gz
-rw-r-----   1 root root                 298 25. Nov 00:01 pve-firewall.log.3.gz
-rw-r-----   1 root root                 124 24. Nov 00:00 pve-firewall.log.4.gz
-rw-r-----   1 root root                 124 23. Nov 00:00 pve-firewall.log.5.gz
-rw-r--r--   1 root root                 127 22. Nov 00:00 pve-firewall.log.6.gz
drwx------   2 root root                4096 25. Nov 00:01 pveproxy
drwxr-xr-x   3 root root                4096 20. Nov 00:27 runit
drwxr-x---   2 root root                4096  3. Feb 2022  samba
-rw-r-----   1 root root             5196599 28. Nov 17:53 syslog
-rw-r-----   1 root root            19093014 27. Nov 04:16 syslog.1
drwxr-x---   2 root root                4096 20. Nov 06:58 unattended-upgrades
-rw-r-----   1 root root                  71 28. Nov 12:29 user.log
-rw-r-----   1 root root                1176 27. Nov 04:16 user.log.1
drwxr-xr-x   2 root root                4096 20. Nov 01:47 vzdump
-rw-rw-r--   1 root utmp               35328 28. Nov 12:30 wtmp

Den Server habe ich zwischenzeitlich mehrfach neu gestartet. Das macht er auch normal via Befehl "reboot" oder alternativ zum Herunterfahren "shutdown -h now".
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,937
160
68
29
Vienna
shop.maurer-it.com
Hello,

Die Permisssion der Ordner sollten wie folgt sein:

Bash:
# ls -la /var/log/pveproxy/
total 32
drwx------  2 www-data www-data  4096 Nov 29 08:04 .
drwxr-xr-x 13 root     root      4096 Nov 29 08:04 ..
-rw-r-----  1 www-data www-data     0 Nov 29 08:04 access.log
-rw-r-----  1 www-data www-data 14255 Nov 24 15:24 access.log.1
-rw-r-----  1 www-data www-data   816 Nov 23 12:58 access.log.2.gz
-rw-r-----  1 www-data www-data  2664 Jul  5 14:50 access.log.3.gz
 

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!

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 your own in 60 seconds.

Buy now!