I’ve followed the steps described in here : http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install to install Qmail Toaster on Centos 5.5.

If you access the isoqlog and get this error:
Forbidden?You don’t have permission to access /qlogs-toaster/ on this server.

After you do some email traffic run this :

sh /usr/share/toaster/isoqlog/bin/cron.sh

Commands that can be used:

qmailctl stat
/home/vpopmail/bin/vadddomain domain.com password
/home/vpopmail/bin/vadduser user@domain.com password
/home/vpopmail/bin/vmoddomlimits -S domain.com // view domain limits
/home/vpopmail/bin/vpasswd // change pass
/home/vpopmail/bin/vmoduser // modify user stats

Run:

Download http://www.atomicorp.com/installers/atomic.sh
sh atomic.sh
yum update php

Dante socks install :

Download Dante from : ftp://ftp.inet.no/pub/socks/dante-1.2.0.tar.gz

tar zxvf dante-1.2.0.tar.gz
cd dante-1.2.0
yum install gcc make
./configure
make -j4
make install

ifconfig -a |  grep inet | awk ‘{print $2}’ | awk -F ‘:’ ‘{print $2}’ | grep -v 127.0.0.1 >  /root/ips

for i in `cat ips` ;do echo “internal: $i port = 6060″ >> /root/sockd.conf ;done

Example of sockd.conf :

logoutput: stderr
method: username none
external: externalIPtouse
client pass {
from: 0.0.0.0/0 port 1-65535 to: 0.0.0.0/0
}
pass {
from: 0.0.0.0/0 to: 0.0.0.0/0
method: username
protocol: tcp udp
}

Launch using :

sockd -f /root/sockd.conf -d

Login to mysql and run :

select SUM(data_length) + SUM(index_length) as size from information_schema.tables where table_schema = ‘your_database’;

One client has : 11.25.0-E43770 – WHM 11.25.0 – X 3.9 and seems that a lot of core files are create in /root or /usr/local/cpanel/install/ or /usr/local/cpanel/whostmgr/docroot/

To erase the core files just run :

updatedb && locate -r /core\.[0-9] | xargs rm -fv

Also verify if /etc/init.d/httpd has :

ulimit -c 0

I have just installed Centos 5.5 by using the Netinstall version. Seems that on my x64_86 system I have a lot of i386 packages installed. To remove them I had to :

yum -C list installed | grep i386 | awk ‘{print $1}’ | xargs yum remove -y

Also edit /etc/yum.conf and add :

exclude=*.i386 *.i486 *.i586 *.i686 *.athlon

• change to the window you want to move
• type (for example) ^a:number 1
• ^x is the host key (usually ^a on most machines)  (CTRL+A)
• :number (typed literally) is the command
• 1 the number to move the current screen to

In order to compile PHP on 64 bit you need to use the option --with-libdir=lib64 otherwise you will stay forever with the following error

checking for MySQL support... yes
checking for specified location of the MySQL UNIX socket... no
checking for MySQL UNIX socket location... no
checking for mysql_close in -lmysqlclient... no
checking for mysql_error in -lmysqlclient... no
configure: error: mysql configure failed. Please check config.log for more information.

Other possible reasons are :
1. missing the libtool-ltdl-devel package
2. missing the ncurses-devel
3. missing mysql-devel package

yum install libtool-ltdl.x86_64 libtool-ltdl-devel.x86_64

The tcp_max_orphans variable tells the kernel how many TCP sockets that are not attached to any user file handle to maintain. In case this number is exceeded, orphaned connections are immediately reset and a warning is printed.

The only reason for this limit to exist is to prevent some simple DoS attacks. Generally you should not rely on this limit, nor should you lower it artificially. If need be, you should instead increase this limit if your network environment requires such an update. Increasing this limit may require that you get more memory installed to your system. If you hit this limit, you may also tune your network services a little bit to linger and kill sockets in this state more aggressively.

This variable takes an integer value and is per default set to 8192, but heavily depends upon how much memory you have. Each orphan that currently lives eats up 64Kb of unswappable memory, which means that one hell of a lot of data will be used up if problems arise.

If you run into this limit, you will get an error message via the syslog facility kern.info that looks something like this: TCP: too many of orphaned sockets If this shows up, either upgrade the box in question or look closer at the tcp_fin_timeout or tcp_orphans_retries which should give you some help with getting rid of huge amounts of orphaned sockets.