/etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/

[ezh]

Same problem as described here:
https://forum.proxmox.com/threads/problem-with-installing-proxmox-ve-on-debian.44316/

But my /etc/hosts seems fine:

---------------------------------------------------------------------------
root@debian:/etc/apt/trusted.gpg.d# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 debian
192.168.1.3 proxmox pvelocalhost

following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
---------------------------------------------------------------------------

Please help...

 

[wolfgang]

Hi,

please send the full output of the error.

 

[ezh]

Nov 19 03:22:51 debian pveproxy[2164]: starting 1 worker(s)
Nov 19 03:22:51 debian pveproxy[2164]: worker 19057 started
Nov 19 03:22:51 debian pveproxy[19057]: /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 1647.
Nov 19 03:22:51 debian pveproxy[19055]: worker exit
Nov 19 03:22:51 debian pveproxy[2164]: worker 19055 finished

 

[ezh]

Any ideas?

 

[wolfgang]

Have you changed the ssl-keys?

 

[Stoiko Ivanov]

Is pmxcfs/pve-cluster running? - What's the output of
`systemctl status -l pve-cluster`
`journalctl -u pve-cluster`?

what does `find /etc/pve` output (remove any infromation you consider sensitive!)

 

[ezh]

No, I just imported it, as it was stated here: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch

I tried to delete it and imported as well, but same result.

 

[ezh]

Sorry I missed message..

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: failed (Result: exit-code) since Wed 2018-11-21 06:42:33 EST; 5h 18min ago
Process: 6456 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
CPU: 5ms

Nov 21 06:42:33 debian systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 21 06:42:33 debian pmxcfs[6456]: [main] crit: Unable to get local IP address
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 21 06:42:33 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'.

 

[ezh]

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 local IP address
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 21 06:42:33 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Nov 21 06:42:33 debian systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 21 06:42:33 debian pmxcfs[6434]: [main] crit: Unable to get local IP address
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 21 06:42:33 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Nov 21 06:42:33 debian systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 21 06:42:33 debian pmxcfs[6456]: [main] crit: Unable to get local IP address
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 21 06:42:33 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 21 06:42:33 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'.

 

[Stoiko Ivanov]

Nov 21 06:42:33 debian pmxcfs[6417]: [main] crit: Unable to get local IP address

The problem probably is in /etc/hosts and your hostname (as far as I can see):
* your shell usually includes the hostname - and it looks like the hostname of the server is debian (`hostname -f` and `cat /etc/hostname` should have the authoritative answer).
* your /etc/hosts contains the entry `192.168.1.3 proxmox pvelocalhost` - so, if you have the ip 192.168.1.3 configured, it would expect the hostname to be proxmox.

* get rid of the line `127.0.1.1 debian` unless you need it
* set your hostname, and adapt /etc/hosts to contain the proper hostname

 

[ezh]

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: active (running) since Wed 2018-11-21 12:17:48 EST; 1min 12s ago
Process: 27159 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=1/FAILURE)
Process: 27139 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 27152 (pmxcfs)
Tasks: 6 (limit: 4915)
Memory: 15.4M
CPU: 558ms
CGroup: /system.slice/pve-cluster.service
└─27152 /usr/bin/pmxcfs

Nov 21 12:17:47 debian pvecm[27159]: | o * o |
Nov 21 12:17:47 debian pvecm[27159]: | . . . |
Nov 21 12:17:47 debian pvecm[27159]: +----[SHA256]-----+
Nov 21 12:17:48 debian pvecm[27164]: got inotify poll request in wrong process - disabling inotify
Nov 21 12:17:48 debian pvecm[27159]: Error Loading request extension section v3_req
Nov 21 12:17:48 debian pvecm[27159]: 140477220803840:error:220A4076:X509 V3 routines:a2i_GENERAL_NAME:bad ip address:../crypto/x509v3/v3_alt.c:441:value=fe80::329c:23ff:feb1:2aca%enp24s
Nov 21 12:17:48 debian pvecm[27159]: 140477220803840:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in extension:../crypto/x509v3/v3_conf.c:47:name=subjectAltName, value=IP:127.
Nov 21 12:17:48 debian pvecm[27159]: unable to generate pve certificate request:
Nov 21 12:17:48 debian pvecm[27159]: command 'openssl req -batch -new -config /tmp/pvesslconf-27164.tmp -key /etc/pve/nodes/debian/pve-ssl.key -out /tmp/pvecertreq-27164.tmp' failed: ex
Nov 21 12:17:48 debian systemd[1]: Started The Proxmox VE cluster filesystem.

 

[okieunix1957]

what if the hostname needed to be change how would I change the keys then?

 

[Stoiko Ivanov]

what if the hostname needed to be change how would I change the keys then?

Please don't post below threads from more than one year ago - but rather open a new thread!
for a hostname change you generally need to:
* change the hostname (by writing to /etc/hostname and using the hostname command)
* add a correct entry for ip to hostname resolution to /etc/hosts
* test by running `ping $(uname -n)`

 

[okieunix1957]

Please don't post below threads from more than one year ago - but rather open a new thread!
for a hostname change you generally need to:
* change the hostname (by writing to /etc/hostname and using the hostname command)
* add a correct entry for ip to hostname resolution to /etc/hosts
* test by running `ping $(uname -n)`

Will do, but the problem been fix. thanks

 

[ivenae]

I my case it was a "no space left on device".