Installing over Debian 8 on GCE node fails

F

FuriousGeorge

Renowned Member
Sep 25, 2012
84
2
73
I'd like to set up Proxmox on a GCE node, for use with pve-zsync, in order to create offsite backups from the synced datasets.

I'm following this guide.

When I attempt to install pm, apt-get fails as follows:

Code: 
update failed - see /var/log/pveam.log for details
Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
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
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for systemd (215-17+deb8u6) ...
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.4.44-1-pve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Following the suggestions I checked:

Code: 
# cat /var/log/pveam.log
Mar 14 09:28:03 starting update
Mar 14 09:28:04 start download http://download.proxmox.com/images/aplinfo.dat.asc
Mar 14 09:28:04 download finished: 200 OK
Mar 14 09:28:04 start download http://download.proxmox.com/images/aplinfo.dat.gz
Mar 14 09:28:04 download finished: 200 OK
Mar 14 09:28:04 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.8758.gz'
Mar 14 09:28:04 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
Mar 14 09:28:05 download finished: 200 OK
Mar 14 09:28:05 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.gz
Mar 14 09:28:05 download finished: 200 OK
Mar 14 09:28:05 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.8758.gz'

I'm not convinced that this is the cause, but I suppose it could be

I also checked:

Code: 
# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: failed (Result: exit-code) since Tue 2017-03-14 09:28:27 UTC; 6min ago
Mar 14 09:28:17 pm-test-1 systemd[1]: Starting PVE API Proxy Server...
Mar 14 09:28:27 pm-test-1 pveproxy[8893]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 331.
Mar 14 09:28:27 pm-test-1 pveproxy[8893]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 331.
Mar 14 09:28:27 pm-test-1 systemd[1]: pveproxy.service: control process exited, code=exited status=255
Mar 14 09:28:27 pm-test-1 systemd[1]: Failed to start PVE API Proxy Server.
Mar 14 09:28:27 pm-test-1 systemd[1]: Unit pveproxy.service entered failed state.

And journalctl -xn showed no errors.

I suspected (and still somewhat suspect) that this is caused networking settings, e.g. the /etc/hosts configuration of the GCE node is partially autogenerated on boot:

Code: 
# cat /etc/hosts
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

10.250.0.250 pm-test-1.c.adept-protocol-683.internal pm-test-1 pvelocalhost  # Added by Google
169.254.169.254 metadata.google.internal  # Added by Google

The lines with the comment by google is reinserted on boot if removed. So working with what I had, I added 'pvelocalhost' to the end, and before rebooting attempted to proceed with the install.

Everything looks ok when I check it hostname and ip resolution, as per the wiki article:

Code: 
# getent hosts $(hostname)
10.250.0.250    pm-test-1.c.adept-protocol-683.internal pm-test-1 pvelocalhost
# getent hosts 10.250.0.250
10.250.0.250    pm-test-1.c.adept-protocol-683.internal pm-test-1 pvelocalhost

I believe the compute engine uses 1:1 NAT, essentially mapping a public IP to a private one. I plan to access the server via VPN when needed, so using the internal IP should not be a problem for me, should it?

Once the install fails, I'm unable to add or remove any other packaged via apt. I haven't been able to find a similar case via Google searching. At this point I'm stuck and any help would be appreciated.
 
pve-zsync only requires ssh and zfs on the receiving side, so a regular Debian Jessie with ZFS from backports should be sufficient.
 
  • Like
Reactions: FuriousGeorge
fabian said:
pve-zsync only requires ssh and zfs on the receiving side, so a regular Debian Jessie with ZFS from backports should be sufficient.
Click to expand...

I was wondering that. At least that makes the worst case scenario less bad.

I did install zfs before triggering the fail. I could start from scratch and not attempt to install pm, but it would be nice to have proxmox installed with a working package manager.
 
I don't intend to launch VMs on this server, so I only allocated a node with 0.6 GB of ram. Could that be causing the install to fail?
 
could you post the full journal output? (at least of the pve* services)
 
Fabian, sorry for the delay, I didn't see that you had responded. In the end I decided to simply not install proxmox on that VM. I don't plant on starting instances on that server anyway, so since pve-zsync works without proxmox on the remote side, I'm happy enough.
 
You must log in or register to reply here.
Top Bottom