A big problem appeared today.
1. Those errors appear in console:
a)
b)
2. It is a LVM-Thin device, that Proxmox shows as 100% usage:
3. Device information shows 325Gb (actually it is a 300Gb WD Velociraptor RAID-1 HDD):
4. lvs -a output from the host, shows 100% of some 185 Gb "data"...
After I deleted the Debian line in hosts I could install proxmox, but still no GUI in browser... As I mentioned in first post:
The connection has timed out
The server at 192.168.1.3 is taking too long to respond.
But wget connects.
I did installed following the guide.
I had problem with host name.
Here it is:
https://forum.proxmox.com/threads/etc-pve-local-pve-ssl-key-failed-to-load-local-private-key-key_file-or-key-at-usr-share-perl5.48943/#post-229246
This was the fix:
* get rid of the line `127.0.1.1 debian` unless you need it
Now all is installed, but...
I have a problem. Installed Proxmox 5.3. Debian.
I cannot connect to Proxmox UI.
From localhost:
wget --no-check-certificate https://192.168.1.3:8006
--2018-12-10 18:21:07-- https://192.168.1.3:8006/
Connecting to 192.168.1.3:8006... connected.
wget https://192.168.1.3:8006
--2018-12-10...
I commented the debian line out and am in 1 step further! :)
root@debian:/etc/apt/trusted.gpg.d# systemctl status -l pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active...
root@debian:/etc/apt/trusted.gpg.d# journalctl -u pve-cluster
-- Logs begin at Tue 2018-11-20 21:20:02 EST, end at Wed 2018-11-21 12:02:42 EST. --
Nov 21 06:42:32 debian systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 21 06:42:33 debian pmxcfs[6417]: [main] crit: Unable to get...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.