Upgraded to debian 8. Proxmox gives errors.

Chris_C

New Member
Jul 28, 2012
12
0
1
I upgraded to Debian 8 on the physical linux machine which proxmox VE is installed on.

Code:
root@machine:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 clvm : Depends: libdlm3 but it is not installed
 init-system-helpers : Depends: perl-base (>= 5.20.1-3) but 5.14.2-21+deb7u4 is installed
 libanyevent-perl : Depends: perlapi-5.20.0
                    Recommends: libasync-interrupt-perl but it is not installed
                    Recommends: libguard-perl but it is not installed
 libapache2-mod-perl2 : Depends: perlapi-5.20.2
                        Recommends: libbsd-resource-perl but it is not installed
                        Recommends: libapache2-reload-perl but it is not installed
 libapache2-request-perl : Depends: perlapi-5.20.0
 libapparmor-perl : Depends: perl-base (>= 5.20.1-3) but 5.14.2-21+deb7u4 is installed
                    Depends: perlapi-5.20.1
 libcommon-sense-perl : Depends: perlapi-5.20.2
 libcrypt-ssleay-perl : Depends: perlapi-5.20.0
 libperl5.20 : Depends: perl-base (= 5.20.2-3+deb8u6) but 5.14.2-21+deb7u4 is installed
 librados2-perl : Depends: perlapi-5.20.0
 libterm-readline-gnu-perl : Depends: perlapi-5.20.0
 libtext-charwidth-perl : Depends: perl-base (>= 5.20.0-4) but 5.14.2-21+deb7u4 is installed
                          Depends: perlapi-5.20.0
 lsof : Depends: libperl4-corelibs-perl but it is not installed or
                 perl (< 5.12.3-7) but 5.20.2-3+deb8u6 is installed
 perl : Depends: perl-base (= 5.20.2-3+deb8u6) but 5.14.2-21+deb7u4 is installed
        Recommends: rename but it is not installed
 perl-modules : Depends: perl-base (>= 5.20.2-3+deb8u6) but 5.14.2-21+deb7u4 is installed
                Recommends: libarchive-extract-perl but it is not installed
                Recommends: libmodule-pluggable-perl but it is not installed
                Recommends: libpod-latex-perl but it is not installed
                Recommends: libterm-ui-perl but it is not installed
                Recommends: libtext-soundex-perl but it is not installed
                Recommends: libcgi-pm-perl but it is not installed
                Recommends: libmodule-build-perl but it is not installed
                Recommends: libpackage-constants-perl but it is not installed
 pve-cluster : Depends: perlapi-5.20.0
 python : Depends: python-minimal (= 2.7.3-4+deb7u1) but 2.7.9-1 is installed
 update-inetd : Depends: libfile-temp-perl
E: Unmet dependencies. Try using -f.
root@machine:~#

Help!
There is no backup of the one large important openvz container running on this proxmox 3.4 physical machine, it contains 100GB or more of media, which would be impossible to recreate if lost.
The containers seem to be able to start and run OK (vzctl start 122), when you stop the container (vzctl stop 122) it gives errors, but it stops (vzlist shows no containers running).
How to fix this catch-22 situation in-place (upgrade OS packages), without damaging the container, without requiring dumping 100GB+ off the vz container, and loading it back on again!?
This must be relatively common issue, so is there possibly a script available to fix this ?!
 
Last edited:
Help.
Same machine, the openvz containers cannot reach the internet, DNS serves are configured right, yet during debian upgrade it appears something changed the network config.

Code:
root@proxmox:~# ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 Scope:Global
          inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:170816 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95042 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19499959 (18.5 MiB)  TX bytes:9268083 (8.8 MiB)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1432 (1.3 KiB)  TX bytes:1432 (1.3 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:112490 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8988280 (8.5 MiB)  TX bytes:2634 (2.5 KiB)

vmbr0     Link encap:Ethernet  HWaddr 0e:19:92:71:3d:cc
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::c19:92ff:fe71:3dcc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2562 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:220284 (215.1 KiB)

Inside the OpenVZ container:
Code:
root@owncloud6:~# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:436636 errors:0 dropped:0 overruns:0 frame:0
          TX packets:436636 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:233415463 (222.6 MiB)  TX bytes:233415463 (222.6 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76012 errors:0 dropped:798 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:6104456 (5.8 MiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.1.114  P-t-P:192.168.1.114  Bcast:192.168.1.114  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

From the proxmox machine:
* DNS works.
* Internet traffic works.

Inside the container:
* DNS servers are configured correctly
* DNS doesn't work - "nslookup yahoo.com" gives: ";; connection timed out; no servers could be reached".
* PING works only to the proxmox IP (192.168.0.100) and to the local internet gateway (192.168.0.1)
* PING fails both for internet DNS names and for internet IP addresses.

Help. How to fix this??
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!