I can't install proxmox-ve

P

prib

New Member
May 24, 2020
7
0
1
38
Hi!

I can't install proxmox-ve. I have plesk server and I try add proxmox

/etc/hosts
127.0.0.1 localhost.localdomain localhost
127.0.1.1 mysite.com mysite pvelocalhost
52.67.*.134 mysite.com mysite

proxmox-ve is already the newest version (5.4-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up pve-manager (5.4-15) ...
Job for spiceproxy.service failed because the control process exited with error code.
See "systemctl status spiceproxy.service" and "journalctl -xe" for details.
spiceproxy.service couldn't start.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

● spiceproxy.service - PVE SPICE Proxy Server
Loaded: loaded (/lib/systemd/system/spiceproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-05-24 08:34:34 UTC; 2min 16s ago
Process: 8684 ExecStart=/usr/bin/spiceproxy start (code=exited, status=255)
CPU: 403ms
May 24 08:34:33 systemd[1]: Starting PVE SPICE Proxy Server...
May 24 08:34:34 spiceproxy[8684]: start failed - unable to create socket - Address already in use
May 24 08:34:34 spiceproxy[8684]: start failed - unable to create socket - Address already in use
May 24 08:34:34 systemd[1]: spiceproxy.service: Control process exited, code=exited status=255
May 24 08:34:34 systemd[1]: Failed to start PVE SPICE Proxy Server.
May 24 08:34:34 systemd[1]: spiceproxy.service: Unit entered failed state.
May 24 08:34:34 systemd[1]: spiceproxy.service: Failed with result 'exit-code'.

demons logs:
May 24 08:38:57 pveproxy[23461]: worker 13850 finished
May 24 08:38:57 pveproxy[23461]: starting 2 worker(s)
May 24 08:38:57 pveproxy[23461]: worker 13953 started
May 24 08:38:57 pveproxy[13952]: /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 1687.
May 24 08:38:57 pveproxy[23461]: worker 13954 started
May 24 08:38:57 pveproxy[13954]: /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 1687.
May 24 08:38:57 pveproxy[13953]: /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 1687.
 
hi,

try removing this line: 127.0.1.1 mysite.com mysite pvelocalhost from /etc/hosts. make sure when you run hostname --ip-address you get 52.67.*.134 as output (i'm assuming this is the redacted public IP? )
 
Yes, is the redacted public IP. I binded 127.0.1.1 and I had normal demons logs.

But not work spiceproxy.service? May be problem is it my firewall or apache?

Code: 
● spiceproxy.service - PVE SPICE Proxy Server
   Loaded: loaded (/lib/systemd/system/spiceproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-05-25 14:42:54 UTC; 23s ago
  Process: 14231 ExecStart=/usr/bin/spiceproxy start (code=exited, status=255)
      CPU: 440ms

May 25 14:42:53  systemd[1]: Starting PVE SPICE Proxy Server...
May 25 14:42:54  spiceproxy[14231]: start failed - unable to create socket - Address already in use
May 25 14:42:54  spiceproxy[14231]: start failed - unable to create socket - Address already in use
May 25 14:42:54  systemd[1]: spiceproxy.service: Control process exited, code=exited status=255
May 25 14:42:54  systemd[1]: Failed to start PVE SPICE Proxy Server.
May 25 14:42:54  systemd[1]: spiceproxy.service: Unit entered failed state.
May 25 14:42:54  systemd[1]: spiceproxy.service: Failed with result 'exit-code'.
 
please remove/comment the line i told you and try reinstalling the package proxmox-ve after checking the output of the hostname --ip-address command....
 
Doesn't work.
Code: 
admin@myserver:~$ hostname --ip-address
52.67.*.134
admin@myserver:~$ sudo apt install proxmox-ve

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for admin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (5.4-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up pve-manager (5.4-15) ...
Job for spiceproxy.service failed because the control process exited with error code.
See "systemctl status spiceproxy.service" and "journalctl -xe" for details.
spiceproxy.service couldn't start.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: 
● spiceproxy.service - PVE SPICE Proxy Server
   Loaded: loaded (/lib/systemd/system/spiceproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-05-26 11:59:55 UTC; 14min ago
  Process: 15165 ExecStart=/usr/bin/spiceproxy start (code=exited, status=255)
      CPU: 353ms

May 26 11:59:55 myserver.com systemd[1]: Starting PVE SPICE Proxy Server...
May 26 11:59:55 myserver.com spiceproxy[15165]: start failed - unable to create socket - Address already in use
May 26 11:59:55 myserver.com spiceproxy[15165]: start failed - unable to create socket - Address already in use
May 26 11:59:55 myserver.com systemd[1]: spiceproxy.service: Control process exited, code=exited status=255
May 26 11:59:55 myserver.com systemd[1]: Failed to start PVE SPICE Proxy Server.
May 26 11:59:55 myserver.com systemd[1]: spiceproxy.service: Unit entered failed state.
May 26 11:59:55 myserver.com systemd[1]: spiceproxy.service: Failed with result 'exit-code'.

Code: 
tcp        0      0 0.0.0.0:8006            0.0.0.0:*               LISTEN      6985/pveproxy
tcp        0      0 127.0.0.1:85            0.0.0.0:*               LISTEN      15343/pvedaemon

Code: 
root     15343  0.0  0.3 552172 107992 ?       Ss   May25   0:01 pvedaemon
root     15347  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker
root     15348  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker
root     15349  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker

Code: 
proxmox-ve: not correctly installed (running kernel: 4.9.185-xxxx-std-ipv6-64)
pve-manager: not correctly installed (running version: 5.4-15/d0ec33c6)
pve-kernel-4.15: 5.4-17
pve-kernel-4.15.18-28-pve: 4.15.18-56
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
 
Last edited:
i'm guessing spiceproxy process got stuck in a D state after failing the installation.. can you try to reboot and try installing again?
 
Spiceproxy process in a S. I will try reboot, but I don't sure it is help me

Code: 
root     15343  0.0  0.3 552172 107992 ?       Ss   May25   0:01 pvedaemon
root     15347  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker
root     15348  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker
root     15349  0.0  0.3 552744 108996 ?       S    May25   0:03 pvedaemon worker

Code: 
www-data  6985  0.0  0.3 559948 109648 ?       Ss   May24   0:02 pveproxy
www-data  6989  0.0  0.3 560512 113364 ?       S    May24   0:07 pveproxy worker
www-data  6990  0.0  0.3 560512 113356 ?       S    May24   0:06 pveproxy worker
www-data  6991  0.0  0.3 560512 113360 ?       S    May24   0:06 pveproxy worker
 
spiceproxy != pveproxy

pveproxy is our frontend and spiceproxy is used for connecting to guest display
 
did it work after rebooting?
 
Thank you! Understood! I don't reboot my server. I found a spiproxy code, port 3128 was specified there. On my server there was a squid who used this port. Why proxmox patch the kernel?
Code: 
service squid stop
 
ah...

prib said:
Why proxmox patch the kernel?
Click to expand...

we use our custom kernel based on the ubuntu kernel with some extra patches..

so it works after disabling/changing port of squid?
 
It works. ;) I made bridge using systemd-networkd. I have been trying to improve NAT to my VM using iptables.
 
great, then you can mark the thread as [SOLVED] so others in the same situation can know what to expect :)
 
You must log in or register to reply here.
Top Bottom