Portal Home > Knowledgebase > Articles Database > Solusvm acting weird!!
Solusvm acting weird!!
| Posted by ballighohosting, 09-21-2014, 06:40 PM |
| Hi guyz,
when trying to create an openvz vps server I can't edit the memory and space fields, there is no fields, instead there is text written in green :
Node Memory Limit 30744MB Available - Limit: 64000MB
Node Disk Limit 1959.4GB Available - Limit: 5859.4GB
and when creating the vps, nothing happens..
also if I try to re-install an existing vps it will go away and disappear from the 'vzlist' command line list ..
however changing the memory and disk of an existing vps works fine..
what on earth is wrong with it, any clues??
Thanks..
|
| Posted by ballighohosting, 09-21-2014, 07:02 PM |
| oh man! what brought this to hosting security and technology forum?? I'm sure I put it in the Hosting software and control panels.. please move it there ..
Thanks..
|
| Posted by Johnny Cache, 09-21-2014, 07:35 PM |
| What's in /var/log/vzctl.log ?
|
| Posted by ballighohosting, 09-21-2014, 07:38 PM |
| ok I cleaned everything in the log file and tried to create a container, these are the new contents of the log file:
2014-09-22T01:38:49+0200 vzctl : CT 120 : Can't load ploop library: libploop.so: cannot open shared object file: No such file or directory
2014-09-22T01:38:49+0200 vzctl : CT 120 : Please install ploop packages!
2014-09-22T01:38:49+0200 vzctl : CT 120 : Creation of container private area failed
2014-09-22T01:38:49+0200 vzctl : CT 120 : Container config file does not exist
2014-09-22T01:38:49+0200 vzctl : CT 120 : Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
2014-09-22T01:38:49+0200 vzctl : CT 120 : Starting container...
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter kmemsize not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter lockedpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter privvmpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter shmpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numproc not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter physpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter vmguarpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter oomguarpages not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numtcpsock not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numflock not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numpty not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numsiginfo not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter tcpsndbuf not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter tcprcvbuf not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter othersockbuf not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter dgramrcvbuf not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numothersock not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numfile not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter dcachesize not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: required UB parameter numiptent not set
2014-09-22T01:38:49+0200 vzctl : CT 120 : Error: failed to apply some parameters, not saving configuration file!
2014-09-22T01:38:49+0200 vzctl : CT 120 : Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
2014-09-22T01:38:49+0200 vzctl : CT 120 : WARNING: /etc/vz/conf/120.conf not found: No such file or directory
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : Bad parameter for --meminfo: 1024M
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : Warning: distribution not specified in CT config, using defaults from /etc/vz/dists/default
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : CT configuration saved to /etc/vz/conf/120.conf
2014-09-22T01:38:49+0200 vzctl : CT 120 : Restarting container
2014-09-22T01:38:49+0200 vzctl : CT 120 : Container private area /vz/private/120 does not exist
|
| Posted by Johnny Cache, 09-21-2014, 07:41 PM |
| Is this a new box? Either disable Ploop from SolusVM or:
# yum install ploop ploop-dev
(ext4-fs only)
I would suggest reading up about Ploop if you intend to use it:
http://openvz.org/Ploop
|
| Posted by ballighohosting, 09-21-2014, 07:43 PM |
| no it's not a new box .. it's been running fine for several months .. but it started doing this a few days ago.. I dunno what ploop is! is it dangerous to install it?
Thanks..
|
| Posted by ballighohosting, 09-21-2014, 08:02 PM |
| DUDE! THANKS A MILLION! This worked perfectly
|
| Posted by Johnny Cache, 09-21-2014, 08:04 PM |
| There are particular configurations where, yes, ploop could potentially be dangerous. Myself and some other OpenVZ admins have been dissecting Ploop on and off for several months and many of these people feel it's a bit risky to use Ploop. You'd have to check the OpenVZ bugzilla for specifics.
I still recommend looking more at Ploop on the OpenVZ website, however. It replaces the former SimFS virtual filesystem on the containers.
|
| Posted by Johnny Cache, 09-21-2014, 08:08 PM |
| LOL. No problem. Still suggest doing some homework on it when you can.
|
Add to Favourites 
Print this Article
Also Read
