Brain's Workbench
To get a count of messages in the queue
exim -bpc
Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient)
exim -bp
Print a summary of messages in the queue (count, volume, oldest, newest, domain, and totals):
exim -bp | exiqsumm
Print what Exim is doing right now:
exiwhat
Display the version of Exim and the location of Exim configuration file:
Just a small hack, but worked good on my ISPConfig 3 setup. Add the following:
nano /etc/postfix/main.cf mailbox_size_limit = 104857600
Save and restart postfix service.
According to official postfix documentation:
message_size_limit (default: 10240000) The maximal size in bytes of a message, including envelope information. Note: be careful when making changes. Excessively small values will result in the loss of non-delivery notifications, when a bounce message size exceeds the local or remote MTA’s message size limit.
For DNS resolution to succeed to 192.168.0.1, the DNS server at 192.168.0.1 will need to accept TCP and UDP traffic over port 53 from our server. A port scanner such as the nmap tool can be used to confirm if the DNS server is available on port 53 as shown below.
Note: To install nmap run ‘yum install nmap -y’.
[root@centos ~]# nmap -sU -p 53 192.168.0.1 Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-26 15:22 AEST Nmap scan report for 192.168.0.1 Host is up (0.00091s latency). PORT STATE SERVICE 53/udp open|filtered domain MAC Address: 02:00:79:55:00:0D (Unknown) Nmap done: 1 IP address (1 host up) scanned in 0.29 seconds [root@centos ~]# nmap -sT -p 53 192.168.0.1 Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-26 15:22 AEST Nmap scan report for 192.168.0.1 Host is up (0.00099s latency). PORT STATE SERVICE 53/tcp open domain MAC Address: 02:00:79:55:00:0D (Unknown) Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds
In order to install Certbot on your server, follow the next steps: (make sure you have “git” installed on your system)
$sudo apt-get install git (if not previously installed) $cd /opt $sudo git clone https://github.com/certbot/certbot
Running the above commands will download the Certbot latest release from their git repo in the /opt folder. Then we need to stop any service that might be using port 80 on our server, since the installation type we will be performing on this tutorial is the “standalone” type described on the Cerbot documentation, there are other ways to install the certificates, it is up to your preference.
Since this tutorial is about Pound, we are assuming the daemon is already installed so we need to stop it:
$sudo service pound stop
once the service is stopped, run:
$cd /opt/certbot $sudo ./letsencrypt-auto --text --email YOUR@EMAIL -d YOUR_DOMAIN --agree-tos --standalone certonly
by default, running the command above will generate the necessary key files (*.pem) in the following folder:
/etc/letsencrypt/live/YOUR_DOMAIN/
now, we need to create a private key file that Pound can understand, to do so run the following:
$sudo cat /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem > /etc/ssl/YOUR_DOMAIN.pem
doing so, will concatenate the privkey.pem file and the fullchain.pem file generated by Cerbot into a single file that will be stored into your ssl certificates folder, this is very important!
Installing the RPM
If you are using the RPM version of Webmin, first download the file from the downloads page, or run the command :
wget http://prdownloads.sourceforge.net/webadmin/webmin-1.870-1.noarch.rpm
then install optional dependencies with :
yum -y install perl perl-Net-SSLeay openssl perl-IO-Tty perl-Encode-Detect
and then run the command :
rpm -U webmin-1.870-1.noarch.rpm
It’s a bit silly process, googled hours but found not solid way to update my old 32bit centos 5 linux box. So came up with a solution of my own. It might work for you, but no guarantee!
Step-1
Remove all .repo inside /etc/yum.conf.d/ directory
Step-2
Create a new repo file inside /etc/yum.conf.d/
nano /etc/yum.conf.d/CentOS-Vault.repo
Update with the following section:
You need to define ACL in /etc/named.conf or /etc/bind/named.conf.local file. Let us say IP 1.2.3.4 and 1.2.3.5 are allowed to transfer your zones.
# vi named.conf or vi /etc/bind/named.conf.local
Here is sample entry for domain domain.org.bd (ns1 configuration):
acl trusted-servers {
1.2.3.4; //ns1
1.2.3.5; //ns2
};
zone "domain.org.bd" {
type master;
file "/var/lib/bind/domain.org.bd.hosts";
also-notify {
1.2.3.5;
};
notify yes;
allow-transfer { trusted-servers; };
};
In this guide, we’ll walk you through installing all of these components (except for Linux, which is already installed as your OS when you create the server).
Install the Extra Packages for Enterprise Linux Repository (or EPEL for short):sudo yum install epel-release
Run a yum update to sync your packages with the new EPEL repository:
sudo yum update
Install MySQL:
sudo yum install mysql-server
Activate MySQL:
sudo service mysqld start
Configure your MySQL installation:
sudo /usr/bin/mysql_secure_installation
Make it so that MySQL will start automatically on server reboot:
Prerequisites
Server with CentOS 7 – 64bit
2 GB or more RAM (Recommended)
Root Privileges on the server
Step 1 – Install Java (JRE and JDK)
In this step, we will install the Java JRE and JDK from the CentOS repository. We will install Java 1.8.11 on the server with the yum command.
Run this command to install Java JRE and JDK from CentOS repository with yum:
yum -y install java-1.8.0-openjdk.x86_64 java-1.8.0-openjdk-devel.x86_64
It will take some time, wait until the installation finished.
Then you should check the Java version with the command below:
java -version
You should see results similar to the ones below:
openjdk version "1.8.0_111" OpenJDK Runtime Environment (build 1.8.0_111-b15) OpenJDK 64-Bit Server VM (build 25.111-b15, mixed mode)
Step 2 – Configure the Java Home Environment
For this setup, we need four nodes (two Apache nodes and two load balancer nodes) and five IP addresses: one for each node and one virtual IP address that will be shared by the load balancer nodes and used for incoming HTTP requests.
I will use the following setup here:
Apache node 1: webserver1.tm.local (webserver1) – IP address: 192.168.0.103; Apache document root: /var/www
Apache node 2: webserver2.tm.local (webserver2) – IP address: 192.168.0.104; Apache document root: /var/www
Load Balancer node 1: loadb1.tm.local (loadb1) – IP address: 192.168.0.101
Load Balancer node 2: loadb2.tm.local (loadb2) – IP address: 192.168.0.102
Virtual IP Address: 192.168.0.105 (used for incoming requests)
In this tutorial I will use Ubuntu 8.04 LTS for all four nodes, just install basic Ubuntu 8.04 LTS on all four nodes. I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you! I also recommend you to have a DNS server in place.