Quantcast
Channel: Proxmox Support Forum
Viewing all 171654 articles
Browse latest View live

PVE Kernel igb driver problem

$
0
0
Proxmox VE release 3.3 has compatibility issues with Intel ethernet cards.
Igb driver version 5.2.94 included in kernels versions pve-kernel-2.6.32-32-pve and pve-kernel-3.10.0-4-pve does not initialize the interface in a correct way, see the included image for console log.
igb-hang.PNG
Kernels pve-kernel-2.6.32-31-pve and pve-kernel-3.10.0-3-pve with igb driver version 5.1.2 are not affected.
My hardware is:
Dell XS23-TY3 Server
Intel WG82576EB cards
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Attached Images

Proxmox 3.3-1 SRV corosync restart failed waiting for quorum Timed out waiting cluste

$
0
0
Dear Promox community,


we wanted to set up a Proxmox cluster with 3 nodes :


srv005 10.5.1.5
srv04 10.5.1.4
srv01 10.5.1.30




we had the three servers installed with Proxmox 3.2 wihout clustering, made the upgrade to Proxmox 3.3.


Then we changed the ip addresses von 10.3.1.XX to 10.5.1.XX


All VMs from the srv04 and srv01 were backed up to get a clean machine, but on srv005 all VMs were not deleted.


we modified /etc/hosts on every server


127.0.0.1 localhost.localdomain localhost
10.5.1.4 srv04.xxxxxxxx.com srv04 pvelocalhost
10.5.1.5 srv005.xxxxxxxx.com srv005
10.5.1.30 srv01.xxxxxxxx.com srv01


Then we took srv005 for our first node, and added two more nodes : srv01 and srv04

Something went wrong or we did a mstake, this now the result :

SRV corosync restart failed waiting for quorum Timed out waiting for cluster


Proxmox_SRV_corosync_Restart.png


We can start and stop VMs on srv005, but we cannot create new VMS on the other two servers.
All servers below the datacenter are marked red

Proxmox_cluster_server_red01.png

Error from the syslog :

cpg_send_message failed

Proxmox_cluster_server_corosync_syslog.png


We have checked multicast with asmping, should be working fine

Proxmox_cluster_server_red01_multicast_working.png


root@srv005:/etc/init.d# pvecm nodes
Node Sts Inc Joined Name
1 M 4 2014-09-21 17:44:05 srv005
2 X 300 srv01
3 X 12 srv04


root@srv005:/etc/init.d# pvecm status
Version: 6.2.0
Config Version: 3
Cluster Name: rzdog01
Cluster Id: 14245
Cluster Member: Yes
Cluster Generation: 6420
Membership state: Cluster-Member
Nodes: 1
Expected votes: 1
Total votes: 1
Node votes: 1
Quorum: 2 Activity blocked
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: srv005
Node ID: 1
Multicast addresses: 239.192.55.220
Node addresses: 10.5.1.5
root@srv005:/etc/init.d#



any tips and hints to get this cluster working are welcome, thanks !

Infiniband 40gbps capped at 12.5gbps

$
0
0
To all my fellow Infiniband users,
Is there a reason why the link between two 40gbps Infiniband hosts are capped no more than 12.5gbps? I setup Infiniband in Proxmox following this wiki https://pve.proxmox.com/wiki/Infiniband

iperf tests always shows between 12.1 to 12.5 gbps.

Missing some configuration?

Hmm, after upgrade no firewall or HTML5

Terminal graphics problem on Ubuntu 14.04 Desktop w/ VNC

$
0
0
Does anyone happen to know why my Terminal window looks all messed up on Ubuntu 14.04 Desktop? I'm running it in a VM and everything else seems to be perfectly fine (see cnn.com website in background). For some reason, my Terminal looks like this whether connected via Proxmox console (VNC) or external VNC app (RealVNC & Chrome VNC Viewer). It also makes no difference if I use the built in Desktop Sharing (vino I think) or x11vnc. I have chosen the Default display option if that makes a difference.

I like my Ubuntu Desktop and this is the only thing keeping me from moving away from my ESXi setup where I do not have this problem.

Thanks in advance!

Screenshot:



This is how I expect it would look. This is a screenshot from my ESXi/VMWare setup:

Cluster and IBM storage

$
0
0
Good day.
I have 2 servers IBM X3550 M3 with HBA SAS adapter and IBM System Storage DH3524 SAS. I have installed Proxmox 3.3 on it. When I try to connect the storage system, it sees only one node.

pvecm status
Code:

root@pve1:~# pvecm status
Version: 6.2.0
Config Version: 2
Cluster Name: pve-cluster
Cluster Id: 23476
Cluster Member: Yes
Cluster Generation: 20
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0 11
Node name: pve1
Node ID: 1
Multicast addresses: 239.192.91.16
Node addresses: 192.168.199.200

fdisk -l on pve1
Code:

root@pve1:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 146.0 GB, 145999527936 bytes
255 heads, 63 sectors/track, 17750 cylinders, total 285155328 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

  Device Boot      Start        End      Blocks  Id  System
/dev/sda1              1  285155327  142577663+  ee  GPT

Disk /dev/sdb: 1796.4 GB, 1796370071552 bytes
57 heads, 28 sectors/track, 2198330 cylinders, total 3508535296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa14806fa

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1            2048  3508535295  1754266624  83  Linux

Disk /dev/mapper/pve-root: 36.2 GB, 36238786560 bytes
255 heads, 63 sectors/track, 4405 cylinders, total 70778880 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-root doesn't contain a valid partition table

Disk /dev/mapper/pve-swap: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders, total 31457280 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-swap doesn't contain a valid partition table

Disk /dev/mapper/pve-data: 75.9 GB, 75937873920 bytes
255 heads, 63 sectors/track, 9232 cylinders, total 148316160 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-data doesn't contain a valid partition table

fdisk -l on pve2
Code:

root@pve2:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 146.0 GB, 145999527936 bytes
255 heads, 63 sectors/track, 17750 cylinders, total 285155328 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

  Device Boot      Start        End      Blocks  Id  System
/dev/sda1              1  285155327  142577663+  ee  GPT

Disk /dev/sdb: 1796.4 GB, 1796370071552 bytes
57 heads, 28 sectors/track, 2198330 cylinders, total 3508535296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa14806fa

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1            2048  3508535295  1754266624  83  Linux

Disk /dev/mapper/pve-root: 36.2 GB, 36238786560 bytes
255 heads, 63 sectors/track, 4405 cylinders, total 70778880 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-root doesn't contain a valid partition table

Disk /dev/mapper/pve-swap: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders, total 31457280 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-swap doesn't contain a valid partition table

Disk /dev/mapper/pve-data: 75.9 GB, 75937873920 bytes
255 heads, 63 sectors/track, 9232 cylinders, total 148316160 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-data doesn't contain a valid partition table

/dev/sdb - Storage System.

At the first node performs the following:

Code:

root@pve1:~# pvcreate /dev/sdb1
  Physical volume "/dev/sdb1" successfully created
root@pve1:~# vgcreate storage1 /dev/sdb1
  Clustered volume group "storage1" successfully created
root@pve1:~# pvs
  PV        VG      Fmt  Attr PSize  PFree
  /dev/sda3  pve      lvm2 a--  135.47g 16.00g
  /dev/sdb1  storage1 lvm2 a--    1.63t  1.63t
root@pve1:~# vgs
  VG      #PV #LV #SN Attr  VSize  VFree
  pve        1  3  0 wz--n- 135.47g 16.00g
  storage1  1  0  0 wz--nc  1.63t  1.63t

but on the second node pvs and vgs display nothing:

Code:

root@pve2:~# pvs
  PV        VG  Fmt  Attr PSize  PFree
  /dev/sda3  pve  lvm2 a--  135.47g 16.00g
root@pve2:~# vgs
  VG  #PV #LV #SN Attr  VSize  VFree
  pve    1  3  0 wz--n- 135.47g 16.00g

In Web panel add storage LVM, choose volume group storage1. First node connects and works well with storage.

Any idea why not see the second node storage?

Best Regards.

Allow some encrypted archives

$
0
0
Hi.

I'm new with proxmox mail gateway, I need to allow encrypted archives from certain senders, and otherwise block them.
I have set Virus Detector -> Options -> Block encrypted archives
but did not really I can find outwards to make the rules to allow the few.
is there anyone who can give me a guide?

unable to generate pve certificate

$
0
0
HI,

I try to install proxmox on Debian Wheezy following the wiki http://pve.proxmox.com/wiki/Install_..._Debian_Wheezy

The installation is complete but I don't understand why I can't generate the pve certificates :mad:

When I tried to generate the certifiicate I got the following message :

# pvecm updatecerts
unable to generate pve www key:
command 'openssl genrsa -out /etc/pve/pve-www.key 2048' failed: open3: exec of openssl genrsa -out /etc/pve/pve-www.key 2048 failed at /usr/share/perl5/PVE/Tools.pm line 307

Here my conf :

#uname -a
Linux proxmox-6-177.proxmox.com 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux


# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1


I tryed to execute the command to generate certificate on my own but it fail when I try to generete pve-ssl.pem
Does anyone have any ideas pls?:(:(

VM backup

$
0
0
Hello,

is it possible to make automatic monthly backups with proxmox ?

Best regards,

FATEH Nour-Eddine

Proxmox 3.3 Passthrough

$
0
0
Hallo Leute,

ich habe mir auf meinen Server Primergy TX100 S3p, 32GB Ram, 3x3TB Raid5, 2x1TB Raid0, Xeon E3 1220v2, PCIe Nvidia GT610
Proxmox 3.3 mit Software Raid installiert.
Das erstellen einer VM mit Win7 funktioniert auch einwandfrei.

Mein Problem ist nun das ich Passthrough der Nvidia GF610 auf das Win7 nicht zum Laufen bekomme.

Meine Einstellungen:

Code:

grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on"

Code:

lspci
  01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)

Code:

  bootdisk: virtio0
  cores: 4
  #hostpci0: 01:00.0
  #hostpci1: 01:00.1
  ide0: Datacenter:iso/Win_client_installer.iso,media=cdrom,size=37016K
  ide1: Datacenter:iso/Win_7.SP1.All.in.One.Oktober.2013.German.iso,media=cdrom
  memory: 4096
  name: Win7
  net0: virtio=F6:54:51:01:5A:D9,bridge=vmbr0
  ostype: win7
  smbios1: uuid=fdc91541-e133-495e-a626-dd235abf7f0a
  sockets: 1
  vga: cirrus
  virtio0: Datacenter:200/vm-200-disk-1.qcow2,format=qcow2,cache=writeback,backup=no,size=50G
  hostpci0: 01:00.0
  hostpci1: 01:00.1


Starte ich nun die VM, so bekomme ich im Gerätemanager einen Ausrufezeichen.
Treiber Installation bringt auch keine Veränderung.


Installiere ich einen neuen kernel 3.10.xx so starten meine VM´s nicht mehr.


Kann mir bitte jemand helfen.
Attached Images

open vnc error: Unsupported security types: 19

$
0
0
On some systems I get this when trying to run console:

Unsupported security types: 19

that happens only on some systems .


using VNC works . so it is not a big deal.

still any clues on how to fix?

Multiple clients with mail gateway

$
0
0
Maybe I'm missing it in the configuration but I'm not seeing a way to forward mail onto other mail servers? Ideally, I'd like to host the mail gateway at our datacenter and then forward the mails (after being processed) over to the correct mail server for that particular domain. Is there a way to do this with the mail gateway?

pfSense 2.2

$
0
0
Hi all,

I have just tested pfSense-2.2-beta x86_64. I am very pleased to inform you that it worked out of the box on Proxmox. Still only able to boot with qemu64.

virtio-disk and virtio-net worked out of the box and CPU idles at a nice 3-4%;)

The virtio-net means full net speed when routing for clients behind it with minimal CPU overhead.

How to achieve ~10Gbps network speed with CT?

$
0
0
I am running PVE version 3.1-21.

When I run VMs with VirtIO, I can achieve (within same host) VM to VM iperf performance ~10Gbps
But when I use CTs (within same host), the iperf network performance is at highest about 1.5Gbps. There seems to be not much configuration to change (resources in vzctl seems resources are not saturated, buffers, mem etc.) Does anyone know any way to improve the network performance?

The host is dual amd Opteron 6128.

Thanks.

USB3 disconnect issues

$
0
0
Hi guys

I recently installed latest version of Proxmox on Zotac box, which runs fine (thanks for great work!), except of annoying USB3 disconnects

as you can se from below msg's external drive randomly disconnects and then reconnects with different device name, because I use LVM ... I need to .. umount un-accessible filesystems
disable/enable volume group, and then I can mount filesystems again, this happens several time per day, I noticed that on heavy i/o it would disconnect in matter of minutes.

is this kernel issue? I found many posts that point to kernel.. after days of searching for solution I decided to post my issue on your forum.

thanks


DMIDECODE
Code:

Base Board Information
    Manufacturer: ZOTAC
    Product Name: ZBOX-ID92/ZBOX-IQ01


DMESG

Code:

EXT4-fs (dm-3): recovery complete
EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts:
EXT4-fs (dm-4): recovery complete
EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts:
usb 4-1: Disable of device-initiated U1 failed.
usb 4-1: USB disconnect, device number 2
usb 4-1: Disable of device-initiated U2 failed.
scsi 6:0:0:0: rejecting I/O to offline device
scsi 6:0:0:0: [sdb] killing request
scsi 6:0:0:0: [sdb] Unhandled error code
scsi 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
scsi 6:0:0:0: [sdb] CDB: Read(10): 28 00 02 19 b7 80 00 00 f0 00
scsi 6:0:0:0: rejecting I/O to offline device
scsi 6:0:0:0: [sdb] killing request
scsi 6:0:0:0: [sdb] Unhandled error code
scsi 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
scsi 6:0:0:0: [sdb] CDB: Read(10): 28 00 02 19 b8 70 00 00 10 00
usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
usb 4-1: New USB device found, idVendor=0480, idProduct=a006
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-1: Product: External USB 3.0
usb 4-1: Manufacturer: TOSHIBA
usb 4-1: SerialNumber: 20130906026575
usb 4-1: configuration #1 chosen from 1 choice
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 7:0:0:0: Direct-Access    TOSHIBA  External USB 3.0 0101 PQ: 0 ANSI: 6
sd 7:0:0:0: Attached scsi generic sg1 type 0
sd 7:0:0:0: [sdc] 1953525164 512-byte logical blocks: (1.00 TB/931 GiB)
sd 7:0:0:0: [sdc] Write Protect is off
sd 7:0:0:0: [sdc] Mode Sense: 1f 00 00 00
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI disk

TOSHIBA DISK
Code:

Bus 004 Device 003: ID 0480:a006 Toshiba America Info. Systems, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType        1
  bcdUSB              3.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass        0
  bDeviceProtocol        0
  bMaxPacketSize0        9
  idVendor          0x0480 Toshiba America Info. Systems, Inc.
  idProduct          0xa006
  bcdDevice            1.07
  iManufacturer          1 TOSHIBA
  iProduct                2 External USB 3.0
  iSerial                3 20130906026575


VM network problem

$
0
0
I have built a Proxmox cluster with 2 physical nodes. On the physical cluster, I want to build a nested Proxmox cluster.
Now I have installed 3 virtual proxmox server on physical node A, but the virtual proxmox server cann't communicate with each other.

Now the situation is as followings:
The physical node A was connect with a physical 2-level switch which were set using default factory settings. And I have a console PC 192.168.100.100 and a windows 2012 server 192.168.100.33 connected with the physical 2-level switch too.
I have set linux bridge vmbr0 on physical node A with ip address 192.168.100.101, gateway 192.168.100.1, netmask 255.255.255.0.
All of the 3 virtual proxmox server were bridged with vmbr0 of the physical node A.
I have set virtual proxmox server ip address by 192.168.100.90, 192.168.100.91, 192.168.100.92 respectively, gateway and netmask settings were kept same with vmbr0 of physical node A.

And the problem is that:
Ping virtual server 192.168.100.90/91/92 from physical node A 192.168.100.101 successfully but with lost package reports sometimes.
Ping virtual server 192.168.100.90/91/92 from console pc 192.168.100.100 successfully.
Ping windows 2012 server 192.168.100.33 from virtual server 192.168.100.90/91/92 failed.
Ping virtual server 192.168.100.90 from virtual server 192.168.100.91 failed.
Ping virtual server 192.168.100.91 from virtual server 192.168.100.92 failed.
Ping virtual server 192.168.100.92 from virtual server 192.168.100.90 failed.

Am I doing some thing wrong? any suggestions?

Is Proxmox Vulnerable to CVE-2014-6271

Cluster IP and noVNC

$
0
0
Hi all

We have defined a Cluster IP in /etc/pve/cluster.conf:

Code:

  <rm>
    <service autostart="1" exclusive="0" name="cluster_ip" recovery="relocate">
      <ip address="xxx.xxx.xxx.xxx"/>
    </service>


When we connect to the Cluster with this Cluster IP and using noVNC we always get the error: Server disconnected (code:1006)

When we connect with a real IP from one of the machines in the cluster noVNC is working fine.

Connecting with the Cluster IP and using the VNC or SPICE Console is working fine.

Is there a solution to fix this Cluster IP and noVNC problem?

Best
Andreas

Traffic Shaping with PVE Firewall - possible?

$
0
0
Is it possible to do traffic shaping to control amount of bandwidth through pve firewall for VMs?

Update failed

$
0
0
Hi,

I just tried to update one of my Proxmox servers and it failed. I'm now no longer able to log in to the web GUI although VMs are still running.

Update output:

Code:

apt-get upgrade
Reading package lists... Done
Building dependency tree     
Reading state information... Done
The following packages have been kept back:
  ceph-common fence-agents-pve glusterfs-client glusterfs-common libpve-access-control librados2 librbd1 proxmox-ve-2.6.32 pve-manager pve-qemu-kvm python-ceph qemu-server
The following packages will be upgraded:
  apt apt-utils bash bind9 bind9-host bind9utils corosync-pve dnsutils file gnupg gpgv iceweasel krb5-locales libapt-inst1.5 libapt-pkg4.12 libbind9-80 libc-bin libc6 libc6-i386 libcorosync4-pve libcurl3-gnutls libdbus-1-3 libdns88 libgpgme11 libgssapi-krb5-2 libgssrpc4 libisc84 libisccc80 libisccfg82 libk5crypto3 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkrb5-3 libkrb5support0 liblua5.1-0 liblwres80 liblzo2-2
  libmagic1 libmozjs24d libnss3 libpve-common-perl libpve-storage-perl libssl1.0.0 locales multiarch-support openssl procmail pve-cluster python-reportbug reportbug vncterm vzctl xulrunner-24.0
54 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Need to get 54.7 MB of archives.
After this operation, 94.2 kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://download.proxmox.com/debian/ wheezy/pve-no-subscription libpve-common-perl all 3.0-19 [44.6 kB]
Get:2 http://download.proxmox.com/debian/ wheezy/pve-no-subscription libpve-storage-perl all 3.0-23 [54.0 kB]     
Get:3 http://security.debian.org/ wheezy/updates/main bash amd64 4.2+dfsg-0.1+deb7u1 [1,498 kB]
Get:4 http://download.proxmox.com/debian/ wheezy/pve-no-subscription libcorosync4-pve amd64 1.4.7-1 [318 kB]
Get:5 http://download.proxmox.com/debian/ wheezy/pve-no-subscription pve-cluster amd64 3.0-15 [147 kB]
Get:6 http://download.proxmox.com/debian/ wheezy/pve-no-subscription vncterm amd64 1.1-8 [206 kB]
Get:7 http://download.proxmox.com/debian/ wheezy/pve-no-subscription vzctl amd64 4.0-1pve6 [280 kB]
Get:8 http://download.proxmox.com/debian/ wheezy/pve-no-subscription corosync-pve amd64 1.4.7-1 [380 kB]
Get:9 http://security.debian.org/ wheezy/updates/main libc6-i386 amd64 2.13-38+deb7u4 [3,912 kB]
Get:10 http://security.debian.org/ wheezy/updates/main libc-bin amd64 2.13-38+deb7u4 [1,271 kB]
Get:11 http://security.debian.org/ wheezy/updates/main libc6 amd64 2.13-38+deb7u4 [4,221 kB]
Get:12 http://security.debian.org/ wheezy/updates/main libapt-pkg4.12 amd64 0.9.7.9+deb7u5 [891 kB]
Get:13 http://security.debian.org/ wheezy/updates/main gpgv amd64 1.4.12-7+deb7u6 [228 kB]
Get:14 http://security.debian.org/ wheezy/updates/main gnupg amd64 1.4.12-7+deb7u6 [1,955 kB]
Get:15 http://security.debian.org/ wheezy/updates/main apt amd64 0.9.7.9+deb7u5 [1,262 kB]
Get:16 http://security.debian.org/ wheezy/updates/main libapt-inst1.5 amd64 0.9.7.9+deb7u5 [167 kB]
Get:17 http://security.debian.org/ wheezy/updates/main libssl1.0.0 amd64 1.0.1e-2+deb7u12 [1,259 kB]
Get:18 http://security.debian.org/ wheezy/updates/main libk5crypto3 amd64 1.10.1+dfsg-5+deb7u2 [113 kB]
Get:19 http://security.debian.org/ wheezy/updates/main libgssapi-krb5-2 amd64 1.10.1+dfsg-5+deb7u2 [148 kB]
Get:20 http://security.debian.org/ wheezy/updates/main libkrb5-3 amd64 1.10.1+dfsg-5+deb7u2 [393 kB]
Get:21 http://security.debian.org/ wheezy/updates/main libkrb5support0 amd64 1.10.1+dfsg-5+deb7u2 [49.8 kB]
Get:22 http://security.debian.org/ wheezy/updates/main libgssrpc4 amd64 1.10.1+dfsg-5+deb7u2 [87.7 kB]
Get:23 http://security.debian.org/ wheezy/updates/main libkadm5clnt-mit8 amd64 1.10.1+dfsg-5+deb7u2 [68.0 kB]
Get:24 http://security.debian.org/ wheezy/updates/main libkdb5-6 amd64 1.10.1+dfsg-5+deb7u2 [67.1 kB]
Get:25 http://security.debian.org/ wheezy/updates/main libkadm5srv-mit8 amd64 1.10.1+dfsg-5+deb7u2 [84.9 kB]
Get:26 http://security.debian.org/ wheezy/updates/main file amd64 5.11-2+deb7u5 [52.6 kB]
Get:27 http://security.debian.org/ wheezy/updates/main libmagic1 amd64 5.11-2+deb7u5 [203 kB]
Get:28 http://security.debian.org/ wheezy/updates/main libcurl3-gnutls amd64 7.26.0-1+wheezy10 [322 kB]
Get:29 http://security.debian.org/ wheezy/updates/main libdbus-1-3 amd64 1.6.8-1+deb7u4 [173 kB]
Get:30 http://security.debian.org/ wheezy/updates/main liblua5.1-0 amd64 5.1.5-4+deb7u1 [180 kB]
Get:31 http://security.debian.org/ wheezy/updates/main liblzo2-2 amd64 2.06-1+deb7u1 [59.0 kB]
Get:32 http://security.debian.org/ wheezy/updates/main libnss3 amd64 2:3.14.5-1+deb7u2 [1,062 kB]
Get:33 http://security.debian.org/ wheezy/updates/main multiarch-support amd64 2.13-38+deb7u4 [151 kB]
Get:34 http://security.debian.org/ wheezy/updates/main apt-utils amd64 0.9.7.9+deb7u5 [378 kB]
Get:35 http://security.debian.org/ wheezy/updates/main dnsutils amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [166 kB]
Get:36 http://security.debian.org/ wheezy/updates/main bind9-host amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [73.5 kB]
Get:37 http://security.debian.org/ wheezy/updates/main bind9 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [373 kB]
Get:38 http://security.debian.org/ wheezy/updates/main libisc84 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [183 kB]
Get:39 http://security.debian.org/ wheezy/updates/main libisccc80 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [36.0 kB]
Get:40 http://security.debian.org/ wheezy/updates/main libisccfg82 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [62.9 kB]
Get:41 http://security.debian.org/ wheezy/updates/main liblwres80 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [55.3 kB]
Get:42 http://security.debian.org/ wheezy/updates/main bind9utils amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [128 kB]
Get:43 http://security.debian.org/ wheezy/updates/main libdns88 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [750 kB]
Get:44 http://security.debian.org/ wheezy/updates/main libbind9-80 amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u2 [42.4 kB]
Get:45 http://security.debian.org/ wheezy/updates/main krb5-locales all 1.10.1+dfsg-5+deb7u2 [1,503 kB]
Get:46 http://security.debian.org/ wheezy/updates/main locales all 2.13-38+deb7u4 [5,657 kB]
Get:47 http://security.debian.org/ wheezy/updates/main procmail amd64 3.22-20+deb7u1 [159 kB]
Get:48 http://security.debian.org/ wheezy/updates/main reportbug all 6.4.4+deb7u1 [128 kB]
Get:49 http://security.debian.org/ wheezy/updates/main python-reportbug all 6.4.4+deb7u1 [136 kB]
Get:50 http://security.debian.org/ wheezy/updates/main iceweasel amd64 24.8.1esr-1~deb7u1 [2,868 kB]
Get:51 http://security.debian.org/ wheezy/updates/main xulrunner-24.0 amd64 24.8.1esr-1~deb7u1 [17.9 MB]
Get:52 http://security.debian.org/ wheezy/updates/main libmozjs24d amd64 24.8.1esr-1~deb7u1 [1,680 kB]
Get:53 http://security.debian.org/ wheezy/updates/main libgpgme11 amd64 1.2.0-1.4+deb7u1 [349 kB]
Get:54 http://security.debian.org/ wheezy/updates/main openssl amd64 1.0.1e-2+deb7u12 [701 kB]
Fetched 54.7 MB in 2s (21.6 MB/s)
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace bash 4.2+dfsg-0.1 (using .../bash_4.2+dfsg-0.1+deb7u1_amd64.deb) ...
Unpacking replacement bash ...
Processing triggers for man-db ...
Setting up bash (4.2+dfsg-0.1+deb7u1) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace libc6-i386 2.13-38+deb7u3 (using .../libc6-i386_2.13-38+deb7u4_amd64.deb) ...
Unpacking replacement libc6-i386 ...
Preparing to replace libc-bin 2.13-38+deb7u3 (using .../libc-bin_2.13-38+deb7u4_amd64.deb) ...
Unpacking replacement libc-bin ...
Processing triggers for man-db ...
Setting up libc-bin (2.13-38+deb7u4) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace libc6:amd64 2.13-38+deb7u3 (using .../libc6_2.13-38+deb7u4_amd64.deb) ...
Unpacking replacement libc6:amd64 ...
Setting up libc6:amd64 (2.13-38+deb7u4) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace libapt-pkg4.12:amd64 0.9.7.9+deb7u2 (using .../libapt-pkg4.12_0.9.7.9+deb7u5_amd64.deb) ...
Unpacking replacement libapt-pkg4.12:amd64 ...
Setting up libapt-pkg4.12:amd64 (0.9.7.9+deb7u5) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace gpgv 1.4.12-7+deb7u4 (using .../gpgv_1.4.12-7+deb7u6_amd64.deb) ...
Unpacking replacement gpgv ...
Processing triggers for man-db ...
Setting up gpgv (1.4.12-7+deb7u6) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace gnupg 1.4.12-7+deb7u4 (using .../gnupg_1.4.12-7+deb7u6_amd64.deb) ...
Unpacking replacement gnupg ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Setting up gnupg (1.4.12-7+deb7u6) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace apt 0.9.7.9+deb7u2 (using .../apt_0.9.7.9+deb7u5_amd64.deb) ...
Unpacking replacement apt ...
Processing triggers for man-db ...
Setting up apt (0.9.7.9+deb7u5) ...
gpg: key B98321F9: "Squeeze Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key 473041FA: "Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>" not changed
gpg: key 65FFB764: "Wheezy Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key 46925553: "Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>" not changed
gpg: Total number processed: 4
gpg:              unchanged: 4
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace libapt-inst1.5:amd64 0.9.7.9+deb7u2 (using .../libapt-inst1.5_0.9.7.9+deb7u5_amd64.deb) ...
Unpacking replacement libapt-inst1.5:amd64 ...
Preparing to replace libssl1.0.0:amd64 1.0.1e-2+deb7u11 (using .../libssl1.0.0_1.0.1e-2+deb7u12_amd64.deb) ...
Unpacking replacement libssl1.0.0:amd64 ...
Preparing to replace libk5crypto3:amd64 1.10.1+dfsg-5+deb7u1 (using .../libk5crypto3_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libk5crypto3:amd64 ...
Preparing to replace libgssapi-krb5-2:amd64 1.10.1+dfsg-5+deb7u1 (using .../libgssapi-krb5-2_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libgssapi-krb5-2:amd64 ...
Preparing to replace libkrb5-3:amd64 1.10.1+dfsg-5+deb7u1 (using .../libkrb5-3_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libkrb5-3:amd64 ...
Preparing to replace libkrb5support0:amd64 1.10.1+dfsg-5+deb7u1 (using .../libkrb5support0_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libkrb5support0:amd64 ...
Preparing to replace libgssrpc4:amd64 1.10.1+dfsg-5+deb7u1 (using .../libgssrpc4_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libgssrpc4:amd64 ...
Preparing to replace libkadm5clnt-mit8:amd64 1.10.1+dfsg-5+deb7u1 (using .../libkadm5clnt-mit8_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libkadm5clnt-mit8:amd64 ...
Preparing to replace libkdb5-6:amd64 1.10.1+dfsg-5+deb7u1 (using .../libkdb5-6_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libkdb5-6:amd64 ...
Preparing to replace libkadm5srv-mit8:amd64 1.10.1+dfsg-5+deb7u1 (using .../libkadm5srv-mit8_1.10.1+dfsg-5+deb7u2_amd64.deb) ...
Unpacking replacement libkadm5srv-mit8:amd64 ...
Preparing to replace file 5.11-2+deb7u3 (using .../file_5.11-2+deb7u5_amd64.deb) ...
Unpacking replacement file ...
Preparing to replace libmagic1:amd64 5.11-2+deb7u3 (using .../libmagic1_5.11-2+deb7u5_amd64.deb) ...
Unpacking replacement libmagic1:amd64 ...
Preparing to replace libcurl3-gnutls:amd64 7.26.0-1+wheezy9 (using .../libcurl3-gnutls_7.26.0-1+wheezy10_amd64.deb) ...
Unpacking replacement libcurl3-gnutls:amd64 ...
Preparing to replace libdbus-1-3:amd64 1.6.8-1+deb7u3 (using .../libdbus-1-3_1.6.8-1+deb7u4_amd64.deb) ...
Unpacking replacement libdbus-1-3:amd64 ...
Preparing to replace liblua5.1-0:amd64 5.1.5-4 (using .../liblua5.1-0_5.1.5-4+deb7u1_amd64.deb) ...
Unpacking replacement liblua5.1-0:amd64 ...
Preparing to replace liblzo2-2:amd64 2.06-1 (using .../liblzo2-2_2.06-1+deb7u1_amd64.deb) ...
Unpacking replacement liblzo2-2:amd64 ...
Preparing to replace libnss3:amd64 2:3.14.5-1 (using .../libnss3_2%3a3.14.5-1+deb7u2_amd64.deb) ...
Unpacking replacement libnss3:amd64 ...
Preparing to replace multiarch-support 2.13-38+deb7u3 (using .../multiarch-support_2.13-38+deb7u4_amd64.deb) ...
Unpacking replacement multiarch-support ...
Processing triggers for man-db ...
Setting up multiarch-support (2.13-38+deb7u4) ...
(Reading database ... 41440 files and directories currently installed.)
Preparing to replace apt-utils 0.9.7.9+deb7u2 (using .../apt-utils_0.9.7.9+deb7u5_amd64.deb) ...
Unpacking replacement apt-utils ...
Preparing to replace dnsutils 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../dnsutils_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement dnsutils ...
Preparing to replace bind9-host 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../bind9-host_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement bind9-host ...
Preparing to replace bind9 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../bind9_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement bind9 ...
Preparing to replace libisc84 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../libisc84_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement libisc84 ...
Preparing to replace libisccc80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../libisccc80_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement libisccc80 ...
Preparing to replace libisccfg82 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../libisccfg82_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement libisccfg82 ...
Preparing to replace liblwres80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../liblwres80_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement liblwres80 ...
Preparing to replace bind9utils 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../bind9utils_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement bind9utils ...
Preparing to replace libdns88 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../libdns88_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement libdns88 ...
Preparing to replace libbind9-80 1:9.8.4.dfsg.P1-6+nmu2+deb7u1 (using .../libbind9-80_1%3a9.8.4.dfsg.P1-6+nmu2+deb7u2_amd64.deb) ...
Unpacking replacement libbind9-80 ...
Preparing to replace krb5-locales 1.10.1+dfsg-5+deb7u1 (using .../krb5-locales_1.10.1+dfsg-5+deb7u2_all.deb) ...
Unpacking replacement krb5-locales ...
Preparing to replace locales 2.13-38+deb7u3 (using .../locales_2.13-38+deb7u4_all.deb) ...
Unpacking replacement locales ...
Preparing to replace procmail 3.22-20 (using .../procmail_3.22-20+deb7u1_amd64.deb) ...
Unpacking replacement procmail ...
Preparing to replace reportbug 6.4.4 (using .../reportbug_6.4.4+deb7u1_all.deb) ...
Unpacking replacement reportbug ...
Preparing to replace python-reportbug 6.4.4 (using .../python-reportbug_6.4.4+deb7u1_all.deb) ...
Unpacking replacement python-reportbug ...
Preparing to replace iceweasel 24.7.0esr-1~deb7u1 (using .../iceweasel_24.8.1esr-1~deb7u1_amd64.deb) ...
Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by iceweasel'
Unpacking replacement iceweasel ...
Preparing to replace xulrunner-24.0 24.7.0esr-1~deb7u1 (using .../xulrunner-24.0_24.8.1esr-1~deb7u1_amd64.deb) ...
Unpacking replacement xulrunner-24.0 ...
Preparing to replace libmozjs24d 24.7.0esr-1~deb7u1 (using .../libmozjs24d_24.8.1esr-1~deb7u1_amd64.deb) ...
Unpacking replacement libmozjs24d ...
Preparing to replace libgpgme11 1.2.0-1.4 (using .../libgpgme11_1.2.0-1.4+deb7u1_amd64.deb) ...
Unpacking replacement libgpgme11 ...
Preparing to replace libpve-common-perl 3.0-18 (using .../libpve-common-perl_3.0-19_all.deb) ...
Unpacking replacement libpve-common-perl ...
Preparing to replace libpve-storage-perl 3.0-19 (using .../libpve-storage-perl_3.0-23_all.deb) ...
Unpacking replacement libpve-storage-perl ...
Preparing to replace openssl 1.0.1e-2+deb7u11 (using .../openssl_1.0.1e-2+deb7u12_amd64.deb) ...
Unpacking replacement openssl ...
Preparing to replace libcorosync4-pve 1.4.5-1 (using .../libcorosync4-pve_1.4.7-1_amd64.deb) ...
Unpacking replacement libcorosync4-pve ...
Preparing to replace pve-cluster 3.0-12 (using .../pve-cluster_3.0-15_amd64.deb) ...
Unpacking replacement pve-cluster ...
Preparing to replace vncterm 1.1-6 (using .../vncterm_1.1-8_amd64.deb) ...
Unpacking replacement vncterm ...
Preparing to replace vzctl 4.0-1pve5 (using .../vzctl_4.0-1pve6_amd64.deb) ...
Unpacking replacement vzctl ...
Preparing to replace corosync-pve 1.4.5-1 (using .../corosync-pve_1.4.7-1_amd64.deb) ...
Unpacking replacement corosync-pve ...
Processing triggers for man-db ...
Processing triggers for ufw ...
Processing triggers for python-support ...
Processing triggers for mime-support ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for pve-manager ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
Restarting PVE API Proxy Server: pveproxy.
Restarting PVE SPICE Proxy Server: spiceproxy.
Setting up libc6-i386 (2.13-38+deb7u4) ...
Setting up libapt-inst1.5:amd64 (0.9.7.9+deb7u5) ...
Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u12) ...
Setting up libkrb5support0:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libk5crypto3:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libkrb5-3:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libgssapi-krb5-2:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libgssrpc4:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libkadm5clnt-mit8:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libkdb5-6:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libkadm5srv-mit8:amd64 (1.10.1+dfsg-5+deb7u2) ...
Setting up libmagic1:amd64 (5.11-2+deb7u5) ...
Setting up file (5.11-2+deb7u5) ...
Setting up libcurl3-gnutls:amd64 (7.26.0-1+wheezy10) ...
Setting up libdbus-1-3:amd64 (1.6.8-1+deb7u4) ...
Setting up liblua5.1-0:amd64 (5.1.5-4+deb7u1) ...
Setting up liblzo2-2:amd64 (2.06-1+deb7u1) ...
Setting up libnss3:amd64 (2:3.14.5-1+deb7u2) ...
Setting up apt-utils (0.9.7.9+deb7u5) ...
Setting up libisc84 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up libdns88 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up libisccc80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up libisccfg82 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up libbind9-80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up liblwres80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up bind9-host (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up dnsutils (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up bind9utils (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Setting up bind9 (1:9.8.4.dfsg.P1-6+nmu2+deb7u2) ...
Stopping domain name service...: bind9waiting for pid 2656 to die
.
Starting domain name service...: bind9.
Setting up krb5-locales (1.10.1+dfsg-5+deb7u2) ...
Setting up locales (2.13-38+deb7u4) ...
Generating locales (this might take a while)...
  en_GB.UTF-8... done
  en_US.UTF-8... done
Generation complete.
Setting up procmail (3.22-20+deb7u1) ...
Setting up python-reportbug (6.4.4+deb7u1) ...
Setting up reportbug (6.4.4+deb7u1) ...
Setting up libmozjs24d (24.8.1esr-1~deb7u1) ...
Setting up xulrunner-24.0 (24.8.1esr-1~deb7u1) ...
Setting up iceweasel (24.8.1esr-1~deb7u1) ...
Setting up libgpgme11 (1.2.0-1.4+deb7u1) ...
Setting up libpve-common-perl (3.0-19) ...
Setting up libpve-storage-perl (3.0-23) ...
Setting up openssl (1.0.1e-2+deb7u12) ...
Setting up libcorosync4-pve (1.4.7-1) ...
Setting up pve-cluster (3.0-15) ...
Restarting pve cluster filesystem: pve-clusterfuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected
[main] notice: exit proxmox configuration filesystem (-1)
 (warning).
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing pve-cluster (--configure):
 subprocess installed post-installation script returned error exit status 255
Setting up vncterm (1.1-8) ...
dpkg: dependency problems prevent configuration of vzctl:
 vzctl depends on pve-cluster; however:
  Package pve-cluster is not configured yet.

dpkg: error processing vzctl (--configure):
 dependency problems - leaving unconfigured
Setting up corosync-pve (1.4.7-1) ...
Processing triggers for python-support ...
Errors were encountered while processing:
 pve-cluster
 vzctl
E: Sub-process /usr/bin/dpkg returned an error code (1)


pveversion -v
Code:

proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-31-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: not correctly installed
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

I notice that the update failed when restarting the pve cluster filesystem. It's probably worth noting this machine wasn't part of a cluster.

Would really appreciate some help.

[Edit]

Tried a few things:
Code:

pvecm status
pve configuration filesystem not mounted

Code:

ls -l /etc/pve
ls: cannot access /etc/pve: Transport endpoint is not connected

Code:

service pve-cluster restart
Restarting pve cluster filesystem: pve-clusterstart-stop-daemon: warning: failed to kill 2675: No such process
fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected
[main] notice: exit proxmox configuration filesystem (-1)
 (warning).

Viewing all 171654 articles
Browse latest View live