meta data for this page
This is an old revision of the document!
Debian
Install Proxmox on ready Debian system. Benefits:
- unusual disk setup (i.e. not using ZFS for raid, only generic MD or LVM raid)
- for lazy people: running system with remote access only
Setup repositories
Package Repositories Detailed step-by-step instuciton wiki
It is very important (to SSL key generation), that hostname is resolved do IP address of device:
hostname --ip-address 192.168.15.77 # should return your IP address here
echo 'deb http://download.proxmox.com/debian/pve buster pve-no-subscription' > /etc/apt/sources.list.d/pve-no-sub.list
wget http://download.proxmox.com/debian/proxmox-ve-release-6.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg apt-get update apt-get install proxmox-ve </code>
issues
Proxmox was installed with incorrect /etc/hosts configuration. After fixing it still shows errors in journal:
pveproxy[26742]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1727. pveproxy[26743]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1727.
journalctl -u pve-cluster systemd[1]: Stopped The Proxmox VE cluster filesystem. systemd[1]: Starting The Proxmox VE cluster filesystem... pmxcfs[2398]: [main] crit: Unable to get local IP address pmxcfs[2398]: [main] crit: Unable to get local IP address systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION systemd[1]: pve-cluster.service: Failed with result 'exit-code'. systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Reason cluster FS on /etc/pve
was not started, symlinks to nodes points to nowhere:
/etc/pve# tree . ├── local -> nodes/host281 ├── lxc -> nodes/host281/lxc ├── openvz -> nodes/host281/openvz └── qemu-server -> nodes/host281/qemu-server
systemctl restart pve-cluster