OpenVZ Forum


Home » General » Support » [ SOLVED ] Unable to set capability: Invalid argument
[ SOLVED ] Unable to set capability: Invalid argument [message #30238] Sun, 18 May 2008 06:19 Go to next message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
None of my vps's are able to boot because of the following error.

thorpe@oblivion ~ # vzctl start 10100
Starting VE ...
VE is mounted
Unable to set capability: Invalid argument
Unable to set capability
VE start failed
VE is unmounted
thorpe@oblivion ~ # 


A quick search of this board hasn't helped much, someone suggested removing lcap, but I do not have lcap installed.

I am running a custom compiled kernel that I built from the kernel-2.6.24-ovz004.1.src.rpm rpm.

The steps I went through are quit long winded, but I can explain if required.

I am running Debian sid (x86_64) with 8G of memory.

These vps had been running without issue for the last month or so, I' just not sure where to start looking.

My /etc/vz/vz.conf file.
## Global parameters
VIRTUOZZO=yes
LOCKDIR=/var/lib/vz/lock
DUMPDIR=/var/lib/vz/dump
VE0CPUUNITS=1000

## Logging parameters
LOGGING=yes
LOGFILE=/var/log/vzctl.log
LOG_LEVEL=0
VERBOSE=0

## Disk quota parameters
DISK_QUOTA=no
VZFASTBOOT=no

# The name of the device whose ip address will be used as source ip for VE.
# By default automatically assigned.
#VE_ROUTE_SRC_DEV="eth0"

# Controls which interfaces to send ARP requests and modify APR tables on.
NEIGHBOUR_DEVS=detect

## Template parameters
TEMPLATE=/var/lib/vz/template

## Defaults for VEs
VE_ROOT=/var/lib/vz/root/$VEID
VE_PRIVATE=/var/lib/vz/private/$VEID
CONFIGFILE="my-16"
DEF_OSTEMPLATE="debian-4.0"

## Load vzwdog module
VZWDOG="no"

## IPv4 iptables kernel modules
IPTABLES="ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length"

## Enable IPv6
IPV6="no"

## IPv6 ip6tables kernel modules
IP6TABLES="ip6_tables ip6table_filter ip6table_mangle ip6t_REJECT"


My /etc/vz/conf/ve-my-16.conf.sample file
# Configuration file generated by vzsplit for 16 VEs
# on HN with total amount of physical mem 7977 Mb
# low memory 7977 Mb, swap size 1921 Mb, Max treads 8000
# Resourse commit level 0:
# Free resource distribution. Any parameters may be increased
# Primary parameters
NUMPROC="2552:2552"
AVNUMPROC="1276:1276"
NUMTCPSOCK="2552:2552"
NUMOTHERSOCK="2552:2552"
VMGUARPAGES="106535:9223372036854775807"

# Secondary parameters
KMEMSIZE="104566476:115023123"
TCPSNDBUF="24402500:34855492"
TCPRCVBUF="24402500:34855492"
OTHERSOCKBUF="12201250:22654242"
DGRAMRCVBUF="12201250:12201250"
OOMGUARPAGES="106535:9223372036854775807"
PRIVVMPAGES="639210:703131"

# Auxiliary parameters
LOCKEDPAGES="5105:5105"
SHMPAGES="63921:63921"
PHYSPAGES="0:9223372036854775807"
NUMFILE="40832:40832"
NUMFLOCK="1000:1100"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="22834205:23519232"
NUMIPTENT="125:125"
DISKSPACE="936398:1030038"
DISKINODES="254089:279499"
CPUUNITS="17651"


And one of my vps's config files /etc/vz/conf/10100.conf
# Configuration file generated by vzsplit for 20 VEs
# on HN with total amount of physical mem 7977 Mb
# low memory 7977 Mb, swap size 1921 Mb, Max treads 8000
# Resourse commit level 0:
# Free resource distribution. Any parameters may be increased
# Primary parameters
NUMPROC="2552:2552"
AVNUMPROC="1276:1276"
NUMTCPSOCK="2552:2552"
NUMOTHERSOCK="2552:2552"
VMGUARPAGES="106535:9223372036854775807"

# Secondary parameters
KMEMSIZE="104566476:115023123"
TCPSNDBUF="24402500:34855492"
TCPRCVBUF="24402500:34855492"
OTHERSOCKBUF="12201250:22654242"
DGRAMRCVBUF="12201250:12201250"
OOMGUARPAGES="106535:9223372036854775807"
PRIVVMPAGES="639210:703131"

# Auxiliary parameters
LOCKEDPAGES="5105:5105"
SHMPAGES="63921:63921"
PHYSPAGES="0:9223372036854775807"
NUMFILE="40832:40832"
NUMFLOCK="1000:1100"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="22834205:23519232"
NUMIPTENT="125:125"
DISKSPACE="936398:1030038"
DISKINODES="254089:279499"
CPUUNITS="17651"
IP_ADDRESS="192.168.10.100"
HOSTNAME="dns"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-4.0-i386-mydns"
ORIGIN_SAMPLE="my-16"
ONBOOT="yes"
NAME="dns"
NAMESERVER="127.0.0.1"


This is my local nameserver so ignore the NAMESERVER directive.

I am having an issue with klogd not being able to start, not sure if this is at all related.

Any help much appreciated.

[Updated on: Tue, 27 May 2008 05:11]

Report message to a moderator

Re: Unable to set capability: Invalid argument [message #30243 is a reply to message #30238] Sun, 18 May 2008 17:44 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

This is a known issue which will be fixed in the next vzctl release. For now, you have to recompile vzctl against the headers of kernel less than 2.6.25. The header that's causing the problem is /usr/include/linux/capability.h

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Unable to set capability: Invalid argument [message #30245 is a reply to message #30238] Sun, 18 May 2008 23:30 Go to previous messageGo to next message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
Thankyou very much, sounds like a reasonably easy fix.

I'll get to it later today and let you know how it went.
Re: Unable to set capability: Invalid argument [message #30327 is a reply to message #30238] Wed, 21 May 2008 12:04 Go to previous messageGo to next message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
Ok, Iv'e compiled vzctl myself against my 2.6.24 kernel and Ive still got the exact same error.

Any ideas?
Re: Unable to set capability: Invalid argument [message #30329 is a reply to message #30327] Wed, 21 May 2008 13:08 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

Make sure that /usr/include/linux/capability.h is from linux kernel sources 2.6.24 or earlier.

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Unable to set capability: Invalid argument [message #30330 is a reply to message #30238] Wed, 21 May 2008 14:48 Go to previous messageGo to next message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
I'm not at home at the moment so have no way of checking. Ive used the vanilla 2.6.24 kernel from kernel.org.

Why/how would /usr/include/linux/capability.h be from another (newer) version of the kernel? Ive never actually had any kernel newer than 2.6.24 on this machine.
Re: Unable to set capability: Invalid argument [message #30432 is a reply to message #30238] Mon, 26 May 2008 00:30 Go to previous messageGo to next message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
Can anyone shed some more light on this subject? Its really quite annoying.
Re: Unable to set capability: Invalid argument [message #30442 is a reply to message #30432] Mon, 26 May 2008 11:23 Go to previous messageGo to next message
marcusb is currently offline  marcusb
Messages: 5
Registered: May 2008
Location: Göteborg, Sweden
Junior Member

I just got the same issue, with a self-compiled 2.6.24 kernel and vzctl 3.0.22-7 on Debian. Downgrading vzctl to 3.0.11-13 helped, but it used to work with earlier 3.0.22 packages too. So it indeed seems like a recompilation issue.

The capability.h header in Debian comes from the linux-libc-dev package which was updated to mainline 2.6.24.7 (from 2.6.24.4) on May 7.
Re: Unable to set capability: Invalid argument [message #30443 is a reply to message #30432] Mon, 26 May 2008 11:50 Go to previous messageGo to next message
azagzin is currently offline  azagzin
Messages: 38
Registered: May 2008
Location: Vilnius
Member
copy compiler.h and capability.h from kernel-headers-2.6.24 to /usr/include/linux/ (on Gentoo) and then recompile vzctl

see post
http://forum.openvz.org/index.php?t=tree&goto=30146& #msg_30146
this help for me Smile

[Updated on: Mon, 26 May 2008 11:51]

Report message to a moderator

Re: Unable to set capability: Invalid argument [message #30477 is a reply to message #30238] Tue, 27 May 2008 05:10 Go to previous message
thorpe is currently offline  thorpe
Messages: 16
Registered: February 2008
Location: Sydney - Australia
Junior Member
Thanks for the replies, downgrading to 3.0.11-13 seems to have fixed the issue, my vps's are back up and running without issue.
Previous Topic: Veth interface not coming up in VPS
Next Topic: certain iptables filter rules not working ?
Goto Forum:
  


Current Time: Mon Nov 04 14:35:43 GMT 2024

Total time taken to generate the page: 0.03417 seconds