[PVE-User] backup job blocked

[Tonci Stipicevic]

Dear all,

yesterday I had problem that link between pve host and nfs backup share
was down
and backup could not not successfully proceed. VM that was backing up in
this moment was in backup-lock and unavailable.

At this time both pve hosts (from cluster) had "dead" pve-web manager
console and I had to restart services and this was no problem.

In order to (re)start VM I could not kill this vzdump job ... at the
end I had to restart the node manually ... pressing the power button

It turns out that losing link with backup nfs share could be very
sensitive issue (during the backup) ?!

What are we supposed to do in such situation ? is there any reliable
way to shutdown jobs that block the entire cluster

thank you in advance and

/
/
/srdac(an pozdrav / best regards/

Tonc(i Stipic(evic', dipl. ing. Elektr.
/direktor / manager/

[Ola Karlsson]

I had a similar issue on my lab installation a week ago.
There was some issue during the backup to a NFS share which resulted in a locked vm.
I should of course fix the backup problem but it doesn’t feel right that a VM gets locked due to a communication error during backup.

BR
Ola



Från: pve-user-***@pve.proxmox.com [mailto:pve-user-***@pve.proxmox.com] För Tonci Stipicevic
Skickat: den 10 februari 2014 09:56
Till: pve-***@pve.proxmox.com
Ämne: [PVE-User] backup job blocked

Dear all,

yesterday I had problem that link between pve host and nfs backup share was down
and backup could not not successfully proceed. VM that was backing up in this moment was in backup-lock and unavailable.

At this time both pve hosts (from cluster) had "dead" pve-web manager console and I had to restart services and this was no problem.

In order to (re)start VM I could not kill this vzdump job ... at the end I had to restart the node manually ... pressing the power button

It turns out that losing link with backup nfs share could be very sensitive issue (during the backup) ?!

What are we supposed to do in such situation ? is there any reliable way to shutdown jobs that block the entire cluster

thank you in advance and

srdaèan pozdrav / best regards

Tonèi Stipièeviã, dipl. ing. Elektr.
direktor / manager

[Tonči Stipičević]

Hello to everybody

I still haven't figured out how to install (upgrade to) 3.2 beta
proxmoxm host ?

PLease help ... putting pvetest in sources.lst does not help at all

Can it be installed from scratch ?

thank you very much in advance

and

/
/
/srdačan pozdrav / best regards/

Tonči Stipičević

Send pve-user mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of pve-user digest..."
1. Re: problems with 3.2-beta (Adam Thompson)
----------------------------------------------------------------------
Message: 1
Date: Sat, 08 Feb 2014 12:43:50 -0600
Subject: Re: [PVE-User] problems with 3.2-beta
Content-Type: text/plain; charset=UTF-8; format=flowed

Overall, the Ceph GUI is great. I actually got Ceph up and running
(and working) this time! Syncing ceph.conf through corosync is such
an obvious way to simplify things... for small clusters, anyway.
I am seeing some problems, however, and I'm not sure if they're just
1. I have one node that's up and running just fine, pvecm claims
everything's fine, but I can't migrate VMs that started somewhere else
to it - migration always fails, claiming the node is dead. Nothing
unusual appears in any logfile that I can see... or at least nothing
that looks bad to me. I can create a new VM there, migrate it
(online) to another node and migrate it back (online, again), but VMs
that were started on another node won't migrate.
5. Stopping VMs with HA enabled is now an *extremely* slow process...
If I disable HA for a particular VM, I now notice that Stopping also
produces a Shutdown task, and it takes longer than previously, but not
unreasonably slow. I don't understand why Stop isn't instantaneous,
though. I notice that typing "stop" into a qm monitor also is slow...
the only way I have to rapidly stop a VM is to kill the KVM process
running it.

FYI: Completely shutting down all four nodes (note: the last two refused
to shutdown cleanly, I had to remove power) and rebooting them seems to
have solved both these problems.

[Martin Maurer]

Hello to everybody

I still haven't figured out how to install (upgrade to) 3.2 beta proxmoxm host ?

PLease help ... putting pvetest in sources.lst does not help at all

[Martin Maurer] Just add the pvetest repo, see http://pve.proxmox.com/wiki/Package_repositories#Proxmox_VE_pvetest_Repository
Next, run ‘apt-get update’ and ‘apt-get dist-upgrade’
Martin

[Tonči Stipičević]

Here is my output :

***@pve1:~# apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://ftp.debian.org wheezy Release.gpg
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://ftp.debian.org wheezy Release
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://ftp.debian.org wheezy/main amd64 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://ftp.debian.org wheezy/contrib amd64 Packages
Hit http://ftp.debian.org wheezy/contrib Translation-en
Hit http://download.proxmox.com wheezy Release.gpg
Hit http://ftp.debian.org wheezy/main Translation-en
Hit http://download.proxmox.com wheezy Release
Hit http://download.proxmox.com wheezy/pvetest amd64 Packages
Ign http://download.proxmox.com wheezy/pvetest Translation-en_US
Ign http://download.proxmox.com wheezy/pvetest Translation-en
Reading package lists... Done
***@pve1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
***@pve1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-43 (running version: 3.1-43/1d4b0dfb)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-13
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
***@pve1:~#

/
/
/srdačan pozdrav / best regards/

Tonči Stipičević
/direktor / manager/**
**



d.o.o.
ltd.

*podrška / upravljanje
**IT*/ sustavima za male i srednje tvrtke/

/Small & Medium Business
/*IT*//*support / management*

Badalićeva 27 / 10000 Zagreb / Hrvatska – Croatia
url: www.suma-informatika.hr
mob: [phone]
fax: [phone]

Post by Tonči Stipičević
Hello to everybody
I still haven't figured out how to install (upgrade to) 3.2 beta proxmoxm host ?
PLease help ... putting pvetest in sources.lst does not help at all
*/[Martin Maurer] Just add the pvetest repo, see
http://pve.proxmox.com/wiki/Package_repositories#Proxmox_VE_pvetest_Repository/*
*/Next, run ‘apt-get update’ and ‘apt-get dist-upgrade’/*
*/Martin/*

[Martin Maurer]

Your list shows latest beta packages. The version number is still 3.1, so maybe this is confusing here.

Martin

[Diaolin (Giuliano Natali)]

I'm currently using it except for the 3.1 kernel

_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user