Difference between revisions of "OpenVZ privvmpages limit"
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
probably it's due to privvmpages limits. | probably it's due to privvmpages limits. | ||
| − | You can view the beancounters using next command: | + | You can view the beancounters using next command from inside the vps: |
cat /proc/user_beancounters | cat /proc/user_beancounters | ||
| Line 17: | Line 17: | ||
vzctl set 324 --privvmpages 262144:262144 --save | vzctl set 324 --privvmpages 262144:262144 --save | ||
| + | |||
| + | |||
| + | Note that privvmpages and some other values can be changed using SolusVM admin CP | ||
"[[Category:Admin area]]" | "[[Category:Admin area]]" | ||
Latest revision as of 19:55, 15 September 2013
If customer got error during installing applications or in similar cases like: "unable to fork" probably it's due to privvmpages limits.
You can view the beancounters using next command from inside the vps:
cat /proc/user_beancounters
if privvmpages result equal to :
privvmpages 102486 131072 131072 131072 6701251
you can try to increase it x2 with next command
vzctl set <vmID> --privvmpages <calue>:<value> --save
For example:
vzctl set 324 --privvmpages 262144:262144 --save
Note that privvmpages and some other values can be changed using SolusVM admin CP
""
