Error in Perl code: command '/sbin/vgchange -aly renders' failed with exit code 5

macky

New Member
Feb 16, 2010
3
0
1
hey all,
Some noob questions here so my apologies up front for this..


I think I managed to bork something up, I did a kernel install from .18 to .24 on the master and a cluster node.
They now report this ...
Master: Linux 2.6.24-8-pve #1 SMP PREEMPT Fri Oct 16 11:17:55 CEST 2009
ClsuterNode: Linux 2.6.24-10-pve #1 SMP PREEMPT Tue Dec 29 10:16:15 CET 2009

Does the -8 and -10 mean I need to fix one or the other to max the kernel builds?

I'm getting the following error when I try to access the virtual machines hardware section
Cluster Node 'KPMC2' /
Virtual Machine Configuration / Hardware
Click this tab gives:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.
[4625]ERR: 24: Error in Perl code: command '/sbin/vgchange -aly renders' failed with exit code 5
Apache Embperl 2.2.0 [Tue Feb 16 11:31:21 2010]



Q: Did I do something stupid doing the kernel changes?
Q: Can I drop back to .18 with no problems in respect to downgrading? Or should I go to .32?


Thanks for your patience :)
 
hey all,
Some noob questions here so my apologies up front for this..


I think I managed to bork something up, I did a kernel install from .18 to .24 on the master and a cluster node.
They now report this ...
Master: Linux 2.6.24-8-pve #1 SMP PREEMPT Fri Oct 16 11:17:55 CEST 2009
ClsuterNode: Linux 2.6.24-10-pve #1 SMP PREEMPT Tue Dec 29 10:16:15 CET 2009

Does the -8 and -10 mean I need to fix one or the other to max the kernel builds?

I'm getting the following error when I try to access the virtual machines hardware section
Cluster Node 'KPMC2' /
Virtual Machine Configuration / Hardware
Click this tab gives:




Q: Did I do something stupid doing the kernel changes?
Q: Can I drop back to .18 with no problems in respect to downgrading? Or should I go to .32?


Thanks for your patience :)
[/LEFT]

Hi,
first (2.6.24-8/10) this means, that your master node are not up-to-date (apt-get upgrade).

The perl-error looks like, that you define a storage (volumegroup) there are only accessible on one host. pve tried to activate the storage on the other node and fail.

Udo
 
rgr
will shutdown and upgrade server properly
thx

The perl-error looks like, that you define a storage (volumegroup) there are only accessible on one host. pve tried to activate the storage on the other node and fail.
I did indeed install a HD and added it into the volume group.
I followed these two threads to help me do this;
http://forum.proxmox.com/threads/2751-2nd-Hard-Disc-LVM2-Questions?highlight=volume+group
http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups

I made this HD;
Renders LVM Yes Yes Yes 465.00 465.76 99.84%

which was shared into the base servers unbuntu server install for formatting / mapping inside that virtual kvm, so the kvm on the master sees the following HD's
Hard disks
local:101/vm-101-disk-1.raw
Renders:vm-101-disk-1

Also if I check the storage area, and edit the new HD
Edit LVM Group
Shared: ticked

Should I turn this option off or do I need to go ahead and create an smb share for this in the smb.conf on the prox server ? and make sure all the fstabs for the clusters mount this?
 
Hi,
shared storage means, that the storage is usable by all nodes - you need this to use live-migration (a very nice feature).
In your case, switch off the shared option. But why you want the storage share with smb? Try nfs.

Udo
 
Hi,
shared storage means, that the storage is usable by all nodes - you need this to use live-migration (a very nice feature).
In your case, switch off the shared option. But why you want the storage share with smb? Try nfs.
Udo

Yeah I don't need that actual storage avail for anything other than the server, which I've then setup an smb share to from inside the kvm for some project storage.
I'm using smb cause in the past I ran into some issues with nfs that as a linux newbie (only been using it for 1 1/2 years) caused me some headaches, with 9.10 ubuntu release smb appears to be working v well out of the box with minor tweeks etc so I guess the short answer is it's letting my head recover after being banged against the keyboard too many times before I give nfs a go again :) *wink*

James

*upgrading atm... will see how it goes :)