All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
SolusVM OpenVZ Issue...
So i have a few nodes all set up the same... but this one keeps throwing this set of errors:
2013-03-26T16:23:57-0700 vzeventd : Started
2013-03-26T16:23:57-0700 vzctl : Setting CPU units: 1000
2013-03-26T16:23:57-0700 vzctl : WARNING: Settings were not saved to config and will be lost after CT restart (use --save flag)
2013-03-26T17:07:22-0700 vzctl : CT 101 : Creating container private area (centos-6-x86_64)
2013-03-26T17:07:22-0700 vzctl : CT 101 : Creation of container private area failed
2013-03-26T17:07:22-0700 vzctl : CT 101 : Container config file does not exist
2013-03-26T17:07:22-0700 vzctl : CT 101 : Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
2013-03-26T17:07:22-0700 vzctl : CT 101 : Starting container...
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter kmemsize not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter lockedpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter privvmpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter shmpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numproc not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter physpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter vmguarpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter oomguarpages not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numtcpsock not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numflock not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numpty not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numsiginfo not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter tcpsndbuf not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter tcprcvbuf not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter othersockbuf not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter dgramrcvbuf not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numothersock not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numfile not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter dcachesize not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: required UB parameter numiptent not set
2013-03-26T17:07:22-0700 vzctl : CT 101 : Error: failed to apply some parameters, not saving configuration file!
2013-03-26T17:07:22-0700 vzctl : CT 101 : Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
2013-03-26T17:07:22-0700 vzctl : CT 101 : WARNING: /etc/vz/conf/101.conf not found: No such file or directory
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : Bad parameter for --meminfo: 3072M
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : Bad parameter for --ioprio: 4,
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : CT configuration saved to /etc/vz/conf/101.conf
2013-03-26T17:07:22-0700 vzctl : CT 101 : Restarting container
2013-03-26T17:07:22-0700 vzctl : CT 101 : Container private area /vz/private/101 does not exist
Comments
Looks like that VPS isn't properly created, or if it was then something interesting happened to its config file and possibly it's data as well. Is this just after running vzctl start on a container that was previously working?
This is a brand new node, this was the first VPS created on it. My other nodes are setup the same way and no issues on them.
2.6.32-042stab075.2
Does this happen to every container or just this one?
On every container so far... I tried even re-installing the whole OS and solus/openvz
Inside your solusvm LOG > system messages, what is the output under "[build] - virtual server XX | hostname XX | IP xx" ?? or is that the output from that source?
Have you sync'd the media templates to all your nodes? I however assume that because it is ctid 101 that this is a solusvm master you're having an issue with.
Tried a different template to start?
I know they're sometimes useless but have you tried SolusVM support?
log for one of the two:
Creating container private area (ubuntu-11.10-x86_64)
Starting container...
CT configuration saved to /etc/vz/conf/102.conf
CT configuration saved to /etc/vz/conf/102.conf
CT configuration saved to /etc/vz/conf/102.conf
CT configuration saved to /etc/vz/conf/102.conf
CT configuration saved to /etc/vz/conf/102.conf
CT configuration saved to /etc/vz/conf/102.conf
Restarting container
I have synced all the media at least three times now ....
I am also going to open a ticket with solus but i hope to get this resolved quickly.
Have you tried a different template like @jarland said? Hope you get this resolved soon
I feel like if I were sitting at the terminal I'd probably go "oh duh it's this" but I'm scratching my head from the outside. Hopefully they get it resolved for you. If not, if I can do anything for you let me know.
I have tried ubuntu and centos both 32 and 64 bit.
Did you enable vswap in SolusVM for the node?
@KuJoe yes
Output of df -h ?
Filesystem Size Used Avail Use% Mounted on
/dev/md2 9.9G 1.2G 8.2G 13% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/md0 248M 67M 169M 29% /boot
/dev/md3 445G 4.9G 417G 2% /vz
Two 500GB WD Caviar Blue in Software RAID1.
Available 4+, needed 0.3+, insufficient space? If I were at the datacenter, I'd kick it.
I imagine examining the script that is erroring out might give you some ideas. Something appears to be getting a float when it expects an int.
Are you building from SolusVM only? Have you tried building a VPS via the CLI?
@kujoe yes we have tried CLI the ssh window above is the result.
@jarland i wish i could its about 500 miles away from me and i have already missed the last flight until morning...
SolusVM is responding with some really interesting English such as "is server the new" but we shall see if any of it helps.
-Your RAID looks screwed up. You said you have two 500GB drives but you only seem to have 10GB of use-ready space in / and /vz?-
EDIT: i read the table wrong. I is all the tired.
I see 417GB free in /vz but I'm also tired.
I have similar output here, on a perfectly functional node, same datacenter:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 9.9G 3.3G 6.2G 35% /
tmpfs 16G 0 16G 0% /dev/shm
/dev/sda1 248M 87M 149M 37% /boot
/dev/sda5 1.8T 65G 1.7T 4% /vz
[root@redpanda ~]#
This comparison on line 75: [ "$AVAIL" -ge "$NEEDED" ]
$AVAIL is generated on line 43: AVAIL="$(echo "$TMP" | awk 'END{print $4}')"
$NEEDED is generated on lines . . .
48: NEEDED="$(gzip -l "$PRIVATE_TEMPLATE" | \
49: awk 'END {print int($2/1024)}')"
or
54: NEEDED="$(ls -l "$PRIVATE_TEMPLATE" | \
55: awk 'END {print int($5/1024*3)}')"
What output do you get from the command line with these commands?
Maybe a corrupt template, or funky output is screwing with awk.
Did you remember to disable Selinux?
I is all the tired. Read the table wrong.
So a huge thanks to everyone! Turns out the media sync has a nice little bug and well the templates were all corrupt.. Deleted them and added them via a wget and all is good
Nice to see it resolved