Restore the backup to another server with id 1009:
vzdump –restore /vz/backup/vzdump-109.tgz 1009

Networking :

Ref: http://wiki.openvz.org/Virtual_Ethernet_device

Adding ethernet card to container:(101 is container id)

#vzctl set 101 –netif_add eth0,00:12:34:56:78:9A,veth101.0,00:12:34:56:78:9B –save

or

#vzctl set 101 –netif_add eth0,,,,vmbr1 –save

Removing ethernet card from container:(101 is container id)

#vzctl set 101 –netif_del eth0 –save

Bridging:

1. Bridge eth0 with vmbr1:

2. #/etc/vz/bin/vz_easyset -v 101 –bridgenet “ifname=eth1,bridge=vmbr1,addresses=192.168.22.18/24″ -g 192.168.22.18

This will bridge the eth1 interface of container (101) with vmbr1 of physical machine

Get the id of the VM
#qm list
VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID
119 testformekvm         running    512                0.00 2849

Now execute the following to open up vnc port for the machine:

#nc -l -p 5900 -c “qm vncproxy VMID PASSWORD”

e.g.
#nc -l -p 5901 -c “qm vncproxy 119 test123″

Now Go to your local Machine and access the console:

#vncviewer basemachine:5901

The exim configuration for this:

/etc/exim.conf:
hostlist relay_hosts = lsearch;/etc/relayhosts :
localhost

What is antirelayd? antirelayd is a daemon that checks /var/log/maillog for pop3/imap logins and keeps track of valid ones for use with smtp relaying. It manages the /etc/relayhosts file automatically so if you are trying to add a static IP in that file it will be cleaned up by antirelayd.
So how can we whitelist some IP and add it permanently to the allowed hosts to relay mail using the server? Well this is very simple but not documented properly (you can easily see this if you are looking into the file /usr/sbin/antirelayd that is just a perl script). So all you have to do is create a file (if no such file exists) called alwaysrelay in /etc and add the IPs you always want to be allowed to relay outgoing mails on the server. Normally /etc/alwaysrelay will not exist, but if it does just edit the file and append the needed IPs.

/etc/alwaysrelay
192.168.0.100
192.168.0.101

and add each IP on a separate line. After this either restart antirelayd or wait for a little while and it will automatically include these IPs in /etc/relayhosts and they will not be cleaned any more (permanent relay).

The same result can be achieved by creating a different file (for ex. /etc/staticrelay) and including it in the exim configuration (in the relay_hosts config similar to /etc/relayhosts). This file will be manually maintained and not cleaned up by antirelayd so the result is the same. Choose the method that you prefer (either antirelayd or exim.conf)…

Edit/Create the file:
/hsphere/local/var/vpopmail/etc/tcp.smtp
Add the following:

#whitelist IP addresses
$IP1:allow,RBLSMTPD=”"
$IP2:allow,RBLSMTPD=”"

Then: Recompile via Command Line option

cd /hsphere/local/var/vpopmail/etc/
/hsphere/shared/bin/tcprules tcp.smtp.cdb tcp.smtp.tmp < tcp.smtp

spamd on someservr.com failed

Script named “/usr/local/cpanel/etc/init/scripts/centos/chkservd” which spawns up the process of “tailwatchd” which monitors services running on the server as per its config files.

This service checks for the status of the services every 10 Minutes. When it finds particular service (e.g. spamd) down due to some reason it tries to start the service and also gives us an alert. If this alert comes again and again there is something we have to worry about.

Here in this case the alert was a false alert since we checked and find service working fine. Also it was observed that the alert never came back again.

Still there is a need to crossverify and check that the service about which chkservd gave alert is working fine and send out a mail regardingg the same.

Please let me know in case of any doubts or suggessions.

While migrating ensim accounts from one server to another server, after transfering the accounts via FTP to the specified directory  it it was found  that   “/ home” directory is getting full aproximately double the size of accounts  migrated.

On investigation it was found that /home/virtual/FILESYSTEMTEMPLATE/.tmp/* was consuming much amount of space. Those were the temporary files cereated by the Ensim Control Panel While restoring the site.

After investigating on it and  going through many forums it was confirmed that these files can be deleted and this will clean up unwanted data.

Hope this helps someone facing such issue….

Install Nagios  (above 3.0) using RPM:

#yum install nagios

This will install the nagios in your server

# yum install nagios-plugins

This will install nagios plugins

# yum install nagios-nrpe

This will install nrpe

# yum install nagios-nrpe-plugins

Download the rpm of pnp4nagios-0.4.12-2 from following link:

http://www.sysadmin.hep.ac.uk/rpms/egee-SA1/centos5-devel/i386/pnp4nagios-0.4.12-2.el5.i386.rpm

Install the RPM:

rpm -ivh pnp4nagios-0.4.12-2.el5.i386.rpm

Now all the requisite softwares are installed , lets configure it.

Configure pnp4nagios in bulk mode:

/etc/nagios/nagios.cfg :
process_performance_data=1## service performance data#service_perfdata_file=/var/spool/nagios/service-perfdataservice_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$service_perfdata_file_mode=aservice_perfdata_file_processing_interval=15service_perfdata_file_processing_command=process-service-perfdata-file
/etc/nagios/commands.cfg :
define command{        command_name    process-service-perfdata-file        command_line    $USER1$/process_perfdata.pl –bulk=/var/spool/nagios/service-perfdata }
define command{        command_name    process-host-perfdata-file        command_line    $USER1$/process_perfdata.pl –bulk=/var/spool/nagios/host-perfdata }

/etc/nagios/hostextinfo.cfg :
define hostextinfo {    host_name localhost    action_url /nagios/pnp4nagios/index.php?host=$HOSTNAME$    }

Restart the services:

/etc/init.d/npcd  restart

/etc/init.d/nagios restart

#!/bin/bash
#This script monitors the load on the server and takes the backup of each database once the load goes down

check_load() {
echo -n “Checking load average: “
load_avg=`cat /proc/loadavg | tr ‘.’ ‘ ‘ | awk ‘{print$1}’`
if
[ $load_avg -ge 10 ];
then
echo -e “load above 10 ($load_avg) sleeping gor 5 min…..”
sleep 3
check_load1
else
echo “load is $load_avg starting backup..”
fi }
check_load1() {
echo -n “Checking load average: “
load_avg=`cat /proc/loadavg | tr ‘.’  ’ ‘ | awk ‘{print$1}’`
if
[ $load_avg -ge 10 ];
then
echo -e “load above 10 ($load_avg) sleeping gor 5 min…..”
sleep 3
check_load
else
echo “load is $load_avg starting backup..”
fi }

for database in db1 db2 db3 db4 db5 db6 db7 db8
do
check_load
echo -e “Starting backup for db $database”
mysqldump -u root -ppassword $database | /bin/gzip -9 > /backup/dir/mysql/$(date +%F)_$database.sql
if
[ $? -eq 0 ]; then
echo “backup done for db $database”
else
echo -e “backup failed for db $database”
fi
done

Following messages were found in CPanel error logs which indicates that while accessing the disk to get the user  quota its not able to read the disk  information.

“Cpanel::SafeRun::Simple::saferun(‘/usr/sbin/repquota’, ‘-auv’) called at /usr/local/cpanel/bin/safe_fetch_repquota line 25

panic [safe_fetch_repquota] The system failed to return from fetching quota and disk infomation. This function cannot be used until quotas are repaired.

exit level [panic]

[2010-12-02 12:20:23 -0500] panic [safe_fetch_repquota] The system failed to return from fetching quota and disk infomation. This function cannot be used until quotas are repaired. at /usr/local/cpanel/bin/safe_fetch_repquota line 21

main::__ANON__(‘ALRM’) called at /usr/local/cpanel/Cpanel/SafeRun/Simple.pm line 28

eval {…} called at /usr/local/cpanel/Cpanel/SafeRun/Simple.pm line 28

Cpanel::SafeRun::Simple::saferun_r(‘/usr/sbin/repquota’, ‘-auv’) called at /usr/local/cpanel/Cpanel/SafeRun/Simple.pm line 34

Cpanel::SafeRun::Simple::saferun(‘/usr/sbin/repquota’, ‘-auv’) called at /usr/local/cpanel/bin/safe_fetch_repquota line 25

panic [safe_fetch_repquota] The system failed to return from fetching quota and disk infomation. This function cannot be used until quotas are repaired.

exit level [panic]“

It was found that this  occurred since the NFS  share drive which we use for backups  was  inaccessible due to some issues  and the cpanel is trying to get the information of this drive too.

We tried umounting the filesystem using force unmount (umount -f /backup) but it didnt help

Umounting the drive using lazy umount option (umount –l /backup) fixed the issue.