headers
Benjamin Henrion | 3 Jan 2012 14:50

/usr/sbin/vzctl: undefined symbol: get_set_opt..failed

Hi,

I am hiting a bug with vzctl, when I do a "vzctl -a", it hangs, and a
similar behaviour when I restart /etc/init.d/vz:

==============================================================================
root <at> molotov /etc/vz/dists [42]# /etc/init.d/vz restart
Bringing down interface venet0: ..done
Stopping OpenVZ: ..done
Starting OpenVZ: ..done
Bringing up interface venet0: ..done
- Warning: IP forwarding is not enabled
vzctl set 0 --cpuunits 1000 failed: /usr/sbin/vzctl: symbol lookup
error: /usr/sbin/vzctl: undefined symbol: get_set_opt..failed
^[[A
==============================================================================

I reinstalled the openvz kernel, vzctl and vzdump, no change of behaviour.

Any idea what this might be?

Maybe a libc6 problem?

Best,

--

-- 
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Benjamin Henrion | 3 Jan 2012 15:08

Re: /usr/sbin/vzctl: undefined symbol: get_set_opt..failed

On Tue, Jan 3, 2012 at 2:50 PM, Benjamin Henrion <bh@...> wrote:
> Hi,
>
> I am hiting a bug with vzctl, when I do a "vzctl -a", it hangs, and a
> similar behaviour when I restart /etc/init.d/vz:
>
> ==============================================================================
> root <at> molotov /etc/vz/dists [42]# /etc/init.d/vz restart
> Bringing down interface venet0: ..done
> Stopping OpenVZ: ..done
> Starting OpenVZ: ..done
> Bringing up interface venet0: ..done
> - Warning: IP forwarding is not enabled
> vzctl set 0 --cpuunits 1000 failed: /usr/sbin/vzctl: symbol lookup
> error: /usr/sbin/vzctl: undefined symbol: get_set_opt..failed
> ^[[A
> ==============================================================================
>
> I reinstalled the openvz kernel, vzctl and vzdump, no change of behaviour.
>
> Any idea what this might be?
>
> Maybe a libc6 problem?

I recompiled a vzctl binary from the git master trunk, moved it to
/usr/sbin, and it works now.

--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kir Kolyshkin | 3 Jan 2012 17:27
Favicon

Re: /usr/sbin/vzctl: undefined symbol: get_set_opt..failed

Your vzctl and vzctl-lib are out of sync.

On Jan 3, 2012 5:53 PM, "Benjamin Henrion" <bh-wt5ZJWH5N74@public.gmane.org> wrote:
Hi,

I am hiting a bug with vzctl, when I do a "vzctl -a", it hangs, and a
similar behaviour when I restart /etc/init.d/vz:

==============================================================================
root <at> molotov /etc/vz/dists [42]# /etc/init.d/vz restart
Bringing down interface venet0: ..done
Stopping OpenVZ: ..done
Starting OpenVZ: ..done
Bringing up interface venet0: ..done
- Warning: IP forwarding is not enabled
vzctl set 0 --cpuunits 1000 failed: /usr/sbin/vzctl: symbol lookup
error: /usr/sbin/vzctl: undefined symbol: get_set_opt..failed
^[[A
==============================================================================

I reinstalled the openvz kernel, vzctl and vzdump, no change of behaviour.

Any idea what this might be?

Maybe a libc6 problem?

Best,

--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."
_______________________________________________
Users mailing list
Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
https://openvz.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users
Permalink | Reply | 0 comments |
headers
Benjamin Henrion | 4 Jan 2012 09:27

Openvz at FOSDEM

Hi,

Just saw there will a talk about openvz at FOSDEM:

http://fosdem.org/2012/schedule/event/hypervisors_openvz

If you want to share experience with OpenVZ, maybe people of this list
can meet somewhere after the talk?

Best,

--

-- 
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."
Permalink | Reply | 0 comments |
headers
Benjamin Henrion | 4 Jan 2012 10:24

Running puppetd in openvz displays a warning

Hi,

I am running puppet clients in openvz containers, but I get a warning
message like this:

=============================================================
sabayon / # puppetd --test
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
info: Caching catalog for sabayon
info: Applying configuration version '1325668910'
notice: Finished catalog run in 0.01 seconds
=============================================================

I compiled puppetd without the selinux use flag, any idea how to get
rid of this warning?

Best,

--

-- 
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."
Permalink | Reply | 1 comment |
headers
Matthew Franz | 4 Jan 2012 11:48
Picon

Re: Running puppetd in openvz displays a warning

What version of puppet?

What version of Linux in your containers?

Anytime you see memory errors you should check /proc/user_beancounters for hits

I recall having some NON-FATAL puppet errors due to selinux  at some
point in time during puppet runs with Ubuntu 10.04 and Centos 5/6
containers and the ancient puppet from the Ubuntu repos whatever is in
EPEL.

- mdf

On Wed, Jan 4, 2012 at 4:24 AM, Benjamin Henrion <bh@...> wrote:
> Hi,
>
> I am running puppet clients in openvz containers, but I get a warning
> message like this:
>
> =============================================================
> sabayon / # puppetd --test
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> Could not retrieve selinux: Cannot allocate memory - /proc/self/mountinfo
> info: Caching catalog for sabayon
> info: Applying configuration version '1325668910'
> notice: Finished catalog run in 0.01 seconds
> =============================================================
>
> I compiled puppetd without the selinux use flag, any idea how to get
> rid of this warning?
>
> Best,
>
> --
> Benjamin Henrion <bhenrion at ffii.org>
> FFII Brussels - +32-484-566109 - +32-2-4148403
> "In July 2005, after several failed attempts to legalise software
> patents in Europe, the patent establishment changed its strategy.
> Instead of explicitly seeking to sanction the patentability of
> software, they are now seeking to create a central European patent
> court, which would establish and enforce patentability rules in their
> favor, without any possibility of correction by competing courts or
> democratically elected legislators."
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users

--

-- 
--
Matthew Franz
mdfranz@...
Permalink | Reply | 0 comments |
headers
Rick van Rein | 5 Jan 2012 12:32
Picon

Using a layered filesystem as private dir?

Hello,

I've just started using OpenVZ, and it feels more natural than the
alternatives I've seen -- my compliments!

I can get a host runnig from a ZFS volume like /tank/vzdemo, which then
also gets shown at /var/lib/vz/vz-$VEID.  But what I really want to
do is use a layered FS (like aufs) as the private directory for the
container.  But trying to do that leads to an error:

bash# mount -t aufs -o br:/tank/vzdemo=rw:/tank/squeeze=ro none /mnt
bash# grep VE_ /etc/vz/conf/777.conf 
VE_PRIVATE=/mnt
bash# vzctl create 777
Private area already exists in /mnt
Creation of container private area failed

What is this trying to say?  Is there a way to do what I am trying
to do?  Did I understand well that the private area is a directory,
not a device?

Thanks,
 -Rick

P.S. To capture any "why" questions :- I am trying to share as many
     resources as possible.  Containers beat Xen/KVM/VMware in that
     respect, and when I can share the base OS and only have a thin
     layer on top, it should mean that even the buffer cache is
     shared between containers.  It also means that upgrades can be
     reduced to a minimum of repetition.
Permalink | Reply | 5 comments |
headers
Scott Dowdle | 5 Jan 2012 18:08
Favicon

Re: Using a layered filesystem as private dir?

Greeting,

----- Original Message -----
> bash# mount -t aufs -o br:/tank/vzdemo=rw:/tank/squeeze=ro none /mnt
> bash# grep VE_ /etc/vz/conf/777.conf
> VE_PRIVATE=/mnt
> bash# vzctl create 777
> Private area already exists in /mnt
> Creation of container private area failed

/mnt isn't your private directory... it should be /mnt/777/private and of course you need a root directory too.

So far as sharing files between containers in a CoW situation, Virtuozzo and Linux-VServer offer those
features, but OpenVZ does not.  It appears you are trying to engineer your own solution.  I don't know if what
you want to do will work or not because I haven't tried it.  Nor have I tried ZFS in Linux. I suspect it won't
work though... but I do wish you luck.

TYL,
--

-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
Permalink | Reply | 1 comment |
headers
Kirill Korotaev | 5 Jan 2012 19:52
Favicon

Re: Using a layered filesystem as private dir?

As Scott mentioned we have VZFS in commercial version of Parallels Containers.
It helps to save a lot of IOPS by sharing files between containers and is fully POSIX compliant.

Thanks,
Kirill

On Jan 5, 2012, at 15:32 , Rick van Rein wrote:

> Hello,
> 
> I've just started using OpenVZ, and it feels more natural than the
> alternatives I've seen -- my compliments!
> 
> I can get a host runnig from a ZFS volume like /tank/vzdemo, which then
> also gets shown at /var/lib/vz/vz-$VEID.  But what I really want to
> do is use a layered FS (like aufs) as the private directory for the
> container.  But trying to do that leads to an error:
> 
> bash# mount -t aufs -o br:/tank/vzdemo=rw:/tank/squeeze=ro none /mnt
> bash# grep VE_ /etc/vz/conf/777.conf 
> VE_PRIVATE=/mnt
> bash# vzctl create 777
> Private area already exists in /mnt
> Creation of container private area failed
> 
> What is this trying to say?  Is there a way to do what I am trying
> to do?  Did I understand well that the private area is a directory,
> not a device?
> 
> 
> Thanks,
> -Rick
> 
> 
> P.S. To capture any "why" questions :- I am trying to share as many
>     resources as possible.  Containers beat Xen/KVM/VMware in that
>     respect, and when I can share the base OS and only have a thin
>     layer on top, it should mean that even the buffer cache is
>     shared between containers.  It also means that upgrades can be
>     reduced to a minimum of repetition.
> 
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users
Permalink | Reply | 2 comments |
headers
jjs - mainphrame | 5 Jan 2012 20:07

Re: Using a layered filesystem as private dir?

I have postfix servers running on openvz and in general give it high marks, but there's little point in trying to make it something it's not. If you have the budget, the extra features of virtuozzo are well worth the money. There are good reasons why virtuozzo is more expensive, but if you can only afford openvz, my advice would be to let it do what it does best, and don't obsess over disk space which is a rather affordable commodity these days.


Joe

On Thu, Jan 5, 2012 at 10:52 AM, Kirill Korotaev <dev-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org> wrote:
As Scott mentioned we have VZFS in commercial version of Parallels Containers.
It helps to save a lot of IOPS by sharing files between containers and is fully POSIX compliant.

Thanks,
Kirill


On Jan 5, 2012, at 15:32 , Rick van Rein wrote:

> Hello,
>
> I've just started using OpenVZ, and it feels more natural than the
> alternatives I've seen -- my compliments!
>
> I can get a host runnig from a ZFS volume like /tank/vzdemo, which then
> also gets shown at /var/lib/vz/vz-$VEID.  But what I really want to
> do is use a layered FS (like aufs) as the private directory for the
> container.  But trying to do that leads to an error:
>
> bash# mount -t aufs -o br:/tank/vzdemo=rw:/tank/squeeze=ro none /mnt
> bash# grep VE_ /etc/vz/conf/777.conf
> VE_PRIVATE=/mnt
> bash# vzctl create 777
> Private area already exists in /mnt
> Creation of container private area failed
>
> What is this trying to say?  Is there a way to do what I am trying
> to do?  Did I understand well that the private area is a directory,
> not a device?
>
>
> Thanks,
> -Rick
>
>
> P.S. To capture any "why" questions :- I am trying to share as many
>     resources as possible.  Containers beat Xen/KVM/VMware in that
>     respect, and when I can share the base OS and only have a thin
>     layer on top, it should mean that even the buffer cache is
>     shared between containers.  It also means that upgrades can be
>     reduced to a minimum of repetition.
>
> _______________________________________________
> Users mailing list
> Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
> https://openvz.org/mailman/listinfo/users


_______________________________________________
Users mailing list
Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
https://openvz.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users
Permalink | Reply | 0 comments |

Gmane