Search results

Bitte entschuldige, da habe ich dich missverstanden. Habe ein LVM konfiguriert.

Der hat "Disk-Image, ISO Image, Container Template, Container" Files.

Der Storage, auf welchen die Backups gehen, hat als Inhalt "VZDump backup file" konfiguriert. Kurios, dass einige LXC Backups angelegt werden, und dann stoppt er auf einmal.

Hallo Community, ich muss einige Backups der KVM und LXC Maschinen anlegen. Ich nutze dazu die Proxmox GUI Backup Funktion. Zunächst alle LXC Server. Dabei folgender Fehler: Wie genau ist das zu deuten? Habe GZIP gewählt und Snapshot mode. Bei einigen klappt es, dann wieder nicht.

It seems like the node is running as cluster configuration. How can i set up / change to single node?

I already restarted the services as i mentioned. The problem is still there. service pvedaemon restart service pveproxy restart service pvestatd restart Then i can browse a while throug the interface. KVM is visible but lxc has a question mark on the icon in the server list.

No. It is productive. But the server itself is running fine. Every VM shows this graph (related to the timestamp) So from this time the connection get lost i think.

What exactly do you need? Yes, i have already tried this. It seems that this problem is related to a backup job. The problem occurred at 3 o'clock at night. Exactly at the time when a backup job of a container should be running / running. I have 2 HDDs running with an ext4 file system in...

All right, I have to take a closer look. At the moment I understood it the same way, that everything is OK. Nevertheless, I did not want to omit any "find" here :) The problem is still there. What I find curious is that I can now access the VMs via the GUI and via the console, but the CTs and...

I found another strange thing. lsblk shows: df -lh shwos: I have checked the HDDs, there are fine. I seems like i have only 1 TB HDD in use, but pvs shows: And when i list the physical volume it shows with pvdisplay: df -lh shows enough free space, but pvdisplay does not. What's this...

Alright, I've come a bit closer to my goal. I have restarted the services pvedaemon, pveproxy and pvestatd. Login is clean. Now all VMs are displayed online. Furthermore, I can manage the VMs via the console and via the GUI. Unfortunately, the problem persists with LXC.

Any other ideas? Unfortunately, I can not access the VMs and CTs on the host. Thank you so much for your support!

Here the output: CLOSE-WAIT 426 0 127.0.0.1:85 127.0.0.1:41430 CLOSE-WAIT 426 0 127.0.0.1:85 127.0.0.1:41646 CLOSE-WAIT 426 0 127.0.0.1:85 127.0.0.1:41808 CLOSE-WAIT 426 0...

It seems like. There is now no CLOSE_WAIT when i execute 'ss -tnp'. I have checked this. When i stop the daemon there is nothing with port 85 and when i stop proxy there is nothing with port 8006. Alright! I have execute the command with the flag and try to login. Following output: EDIT://...

But only when I wanted to login. Before, I did not try to sign up. Many of this entries: State Recv-Q Send-Q Local Address:Port Peer Address:Port CLOSE-WAIT 426 0...

I restart the services (vpeproxy & vpedaemon) and login into the GUI. After that, the timeout occured. Output journal:

It is a single Node. pvestatd is running fine. What exactly should i check? I see no network problems....

There are no stranger infos in the logs. I can restart the pveproxy without any error. The curios thing is that i can access the GUI after i reboot the pvedaemon (not the proxy). But after a couple of seconds the load-gif is there an i can dont do anything. Furtehrmore, the LXC and VMs on...

No, i already checked this. When i try to login the load-gif is present for round about 20 seconds and then i get an "Login failed. Pleaste try again". When i restart now the pvedaemon and try to login again, it works fine for a few seconds. Then, when i am logged in into the GUI, i only see...

I have found this. But what does this mean in relation to my problem? Server is running fine without any issue.