Steps for configuration change password plugin for squirrelmail/Horde/Rainloop using poppassd are:
Download poppassd.c from https://netwinsite.com/poppassd/
Look at poppassd.c and make sure it looks safe
yum -y install gcc
gcc poppassd.c -o poppassd -lcrypt
mv poppassd /usr/local/bin/
yum -y install xinetd
cp /etc/xinetd.d/time-stream /etc/xinetd.d/poppassd
nano /etc/xinetd.d/poppassdUpdate “service time” to “service poppassd”
disable = no
id = poppasswd
type = UNLISTED
user = root
group = root
server = /usr/local/bin/poppassd
port = 106
systemctl restart xinetd
systemctl enable xinetd
Test by doing “telnet localhost 106” that service is started properly or not.
Your poppassd is now installed on Centos 7 system.
To add a temporary route:
ip route add 172.16.5.0/24 via 10.0.0.101 dev eth0
To make it persist system or network settings restart, create a route-ifname file for an interface through which the subnet is accessed, in this case eth0:
Add the line with the network settings for the other subnet:
172.16.5.0/24 via 10.0.0.101 dev eth0
If your computer is on a network and is not directly connected to the internet, it will be configured with what is called a default gateway, which is usually a router. If the computer cannot find the specific IP address on its local network (aka broadcast domain), as defined by its subnet, it will forward any packets headed to that IP address to the default gateway. The gateway will then attempt to forward packets elsewhere, such as the internet, or another broadcast domain Continue reading “Add a Static Route on CentOS” »
CentOS 7 only allows Fully Qualified Domain Names (FQDN’s). Acceptable values include lower-case letters a to z, numbers 0 to 9, the period, and the hyphen, and between 2 and 63 characters.
At the console, type:
hostnamectl set-hostname my.new-hostname.server
NOTE: Replace my.new-hostname.server with your chosen hostname.
Check the Hostname
In this tutorial, I use the hostname server1.example.com with the IP p 192.168.1.100. These settings might differ for you, so you have to replace them where appropriate.
I will add the EPEL repo here to install latest phpMyAdmin as follows:
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY*
yum -y install epel-release
To edit files on the shell, I’ll install the nano editor. If you prefer vi for file editing, then skip this step.
yum -y install nano
Installing MySQL / MariaDB
MariaDB is a MySQL fork of the original MySQL developer Monty Widenius. MariaDB is compatible with MySQL and I’ve chosen to use MariaDB here instead of MySQL. Run this command to install MariaDB with yum:
yum -y install mariadb-server mariadb
Then we create the system startup links for MySQL (so that MySQL starts automatically whenever the system boots) and start the MySQL server: Continue reading “Install LAMP on Centos 7 with PHP 5.x/7.0/7.1/7.2” »
MariaDB is an open source relational database management system, backward compatible, binary drop-in replacement of MySQL. It is developed by some of the original developers of the MySQL and by many people in the community. With the release of CentOS 7, MySQL was replaced with MariaDB as the default database system.
If you, for any reason need to install MySQL, check the How to Install MySQL on CentOS 7 tutorial. If your application does not have any specific requirements, you should stick with MariaDB, the default database system in CentOS 7.
In this tutorial we will show you how to install the latest version of MariaDB on CentOS 7 using the official MariaDB repositories.
Make sure you are logged in as a user with sudo privileges before proceeding with the tutorial. Continue reading “Install MariaDB on CentOS 7” »
If you are looking for the options to avoid any DNS-related downtime or the way to manage dns across all server you have, you might consider to set up dns cluster.
Create user dns-cluster on a server which will be used as dns slave
On the second server (slave) with vestacp you should create new user with name dns-cluster (via gui or cli)Code:
v-add-user dns-cluster passowrd firstname.lastname@example.org
On the first server (master) you should run this command: Continue reading “Vesta- How to set up master-slave DNS cluster” »
I had few issues on my container and KVM on installing vestacp. Issues were like quite weird, such as-
- Post installation on KVM- it moved into emergency maintenance mode
- Post installation on LXC container- DNS resolution halted
After hours and hours of search, found few root causes-
- I have to withdraw quota with vestacp installation package
- No firewall on LXCcontainer
So let’s start.
Download installation script
curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd yes --proftpd no --iptables no --fail2ban no --quota no --exim yes --dovecot yes --spamassassin yes --clamav yes --softaculous yes --mysql yes --postgresql no --hostname yourdomain.com --email email@example.com --password yourpassword
You can also generate your installation command from vesta website: Continue reading “Install Vesta Control Panel (vestacp) on Centos 7 with PHP-FPM and PHP 7.2” »
To use RHEL/CentOS 6 system as an iSCSI initiator or client, you must have iscsi-initiator-utils package installed. You can verify that this is installed on your system using the rpm command, as shown in the following example:
$ rpm -qa | grep iscsi-initiator-utils
Install the package if its not already available on your system using yum.
# yum install iscsi-initiator-utils
Start the iscsi demaon and use chkconfig to enable it to start after reboot as well.
# service iscsi start
# chkconfig iscsi on
Once you have installed the required package and started the service you can start discovering the available targets. To Obtain a listing of available targets from a given host (please note that ipaddress listed below must be replaced with the resolvable hostname or IP address of the system providing the port if different than default):
# iscsiadm -m discovery -t st -p 192.168.10.10
Continue reading “Configure iSCSI Initiator (client) in CentOS / RHEL 6” »
Device Mapper Multipathing (DM-Multipath) is a native multipathing in Linux, Device Mapper Multipathing (DM-Multipath) can be used for Redundancy and to Improve the Performance. It aggregates or combines the multiple I/O paths between Servers and Storage, so it creates a single device at the OS Level.
For example, Lets say a server with two HBA card attached to a storage controller with single ports on each HBA cards. One lun assigned to the single server via two wwn number of both cards. So OS detects two devices: /dev/sdb and /dev/sdc. Once we installed the Device Mapper Multipathing. DM-Multipath creates a single device with a unique WWID that reroutes I/O to those four underlying devices according to the multipath configuration. So when there is a failure with any of this I/O paths, Data can be accessible using the available I/O Path.
Install the Device Mapper Multipath package.
Verify the device-mapper-multipath package has been installed or not.
[root@linux1 ~]# rpm -q device-mapper-multipath
If it is not installed, Install the Device Mapper Multipath package using yum to avoid dependencies issue. if yum is not configured, please refer the link Yum Configuration on Linux.
[root@linux1 ~]# yum -y install device-mapper-multipath
Basic Configuration of Linux Device Mapper Multipathing
Configuration file is /etc/multipath.conf file, take a backup of it. Edit the configuration file to ensure you have the following entries uncommented out. Continue reading “Add Multipath and connect to XFS system” »
Allow IP forwarding
(Note: if your testing this on the same box your doing this on it won’t work, you need at least 3 machines to test this out, virtual ones work nicely)
First we enable ipv4 forwarding or this will not work:
# echo "1" > /proc/sys/net/ipv4/ip_forward
# sysctl net.ipv4.ip_forward=1
next we add a filter that changes the packets destination ip and allows us to masquerade:
# iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.0.3:80
# iptables -t nat -A POSTROUTING -j MASQUERADE
The above filter gets added to iptables PREROUTING chain. The packets first go through the filters in the PREROUTING chain before iptables decides where they go. The above filter says all packets input into eth0 that use tcp protocol and have a destination port 80 will have their destination address changed to 18.104.22.168 port 80. The DNAT target in this case is responsible for changing the packets Destination IP address. Variations of this might include mapping to a different port on the same machine or perhaps to another interface all together, that is how one could implement a simple stateful vlan (in theory). Continue reading “Stateful Load Balancer with iptables and NAT” »