[SOLVED] Ich kann nach Stromausfall nicht mehr auf Proxmox Web-Overfläche

shrdlicka

Active Member
Staff member
May 2, 2022
406
46
28
Wie schaut den deine derzeitige /etc/network/interfaces aus?

Wenn du deine derzeitige IP sehen willst kannst du diesen Befehl ausführen:
Code:
ip address
 

snaxo

New Member
Jun 17, 2022
15
0
1
Wie schaut den deine derzeitige /etc/network/interfaces aus?

Wenn du deine derzeitige IP sehen willst kannst du diesen Befehl ausführen:
Code:
ip address
Moin, / interfaces:
auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.188.4/24
gateway 192.168.188.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

unter ip adress:
Object "adress" is unknown, try "ip help".
 

shrdlicka

Active Member
Staff member
May 2, 2022
406
46
28
Hi,

dann füge am besten unter 127.0.0.1 localhost.localdomain localhost in der /etc/hosts Datei das hinzu:

Code:
192.168.188.4 pve
 

snaxo

New Member
Jun 17, 2022
15
0
1
Hi,

dann füge am besten unter 127.0.0.1 localhost.localdomain localhost in der /etc/hosts Datei das hinzu:

Code:
192.168.188.4 pve
ok habe ich gemacht und gespeichert. Soll ich den Server danach neustarten?
 

snaxo

New Member
Jun 17, 2022
15
0
1
Neuste Logs sagen mir das:
-- Journal begins at Sun 2022-06-12 02:23:32 CEST, ends at Tue 2022-06-21 15:58:42 CEST. --
Jun 21 09:11:39 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:39 pve pmxcfs[1099]: fuse: mountpoint is not empty
Jun 21 09:11:39 pve pmxcfs[1099]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:39 pve pmxcfs[1099]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1099]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve pmxcfs[1099]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1099]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:39 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Jun 21 09:11:39 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:39 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:39 pve pmxcfs[1169]: fuse: mountpoint is not empty
Jun 21 09:11:39 pve pmxcfs[1169]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:39 pve pmxcfs[1169]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1169]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve pmxcfs[1169]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:39 pve pmxcfs[1169]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:39 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:39 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1170]: fuse: mountpoint is not empty
Jun 21 09:11:40 pve pmxcfs[1170]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:40 pve pmxcfs[1170]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1170]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve pmxcfs[1170]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1170]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:40 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1171]: fuse: mountpoint is not empty
Jun 21 09:11:40 pve pmxcfs[1171]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Jun 21 09:11:40 pve pmxcfs[1171]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1171]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve pmxcfs[1171]: [main] crit: fuse_mount error: File exists
Jun 21 09:11:40 pve pmxcfs[1171]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 21 09:11:40 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
Jun 21 09:11:40 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 21 09:11:40 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 21 09:11:40 pve pmxcfs[1172]: fuse: mountpoint is not empty


Ich bin nochmal die Steps zum SSL erstellen durchgegangen und bei folgendem sagt er mir es gibt keinen File/Directory:
cp pve-ssl.key /etc/pve/local/pve-ssl.key
cp pve-ssl.pem /etc/pve/local/pve-ssl.pem

alles anderen Schritte haben ohne Probleme geklappt...
 
Last edited:

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!