Editing VPS Management (section)

=== CentOS can't get on the network ===

When CentOS system was running, but can't get on the network, they probably updated iproute via yum.

Copy an older version of the iproute rpm to their VPS.

<pre>cp -p /root/iproute/iproute-2.6.32-23.el6.<i686>.rpm /vz2/private/<1527>/fs/root</pre>

Enter their ve, install rpm, restart network, and prevent yum from updating iproute.

<pre>
ve <1527>
rpm -i --force iproute-2.6.32-23.el6.<i686>.rpm
rpm -q iproute
rpm -e <new iproute rpm>
service network restart
echo "exclude=iproute" >>/etc/yum/ip-exclude
echo "include=/etc/yum/ip-exclude" >>/etc/yum.conf
</pre>




----

in a ve i do:

<pre>cd /
du -h .</pre>

and get: 483M    .

i do:

<pre>bash-2.05a# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/vzfs             4.0G  2.3G  1.7G  56% /</pre>

how can this be?

Is it possible that quota file was corrupted somehow? Please try to:   
<pre>vzctl stop <VEID>
vzquota drop <VEID>
vzquota init <VEID>
vzctl start <VEID></pre>

----

How to stop vz from starting after reboot:

 VIRTUOZZO=no 
in 
 /etc/sysconfig/vz

To start: 
 service vz start
(after setting VIRTUOZZO=yes in /etc/sysconfig/vz)

service vz restart will do some kind of 'soft reboot' -- restart all
VPSes and reload modules without rebooting the node

if you need to shut down all VPSes really really fast, run killall -9 init

----

Postfix tip:

You may want to tweak settings: default_process_limit=10

----

* uptime/load that vz users see isn’t what we see- it's their own load
* Vz overwrites resolve.conf on every boot to what’s in ve config file. Also overwrites hostname
* Quotas in vz: set Gid_limit in vz config file and restart ve. Errors leading up to this will be out of files but no inode or space issues. set to 2000 in conf, and restart vz