Bài đăng

Đang hiển thị bài đăng từ Tháng 5, 2015

How To Install & Configure Zimbra High Availability (HA)

Hình ảnh
In the previous articles, i’ve been explain how to install and configure Zimbra on CentOS 6 or CentOS 7 , how to install and configure online failover/failback on CentOS 6 using Heartbeat and how to install and configure data replication on CentOS 6 using DRBD . All above guidance could be combined to get Zimbra High Availability. For online failover/failback, you could using Heartbeat. For data replication, you could using DRBD. Heartbeat + DRBD will produce High Availability (HA). The following is guidance to configure Zimbra HA Step by step to configure Zimbra HA For the Linux systems, i am using CentOS 6 64 Bit. For easy understanding, this is my information system # Server 1 Hostname : node1 Domain : imanudin.net IP Address : 192.168.80.91 # Server 2 Hostname : node2 Domain : imanudin.net IP Address : 192.168.80.92 # Alias IP Hostname : mail Domain : imanudin.net IP Address : 192.168.80.93 Alias IP will be used for access clients/users. This alias

Testing Data Replication/Synchronize on DRBD

After configuration DRBD in the previous article , we must test first for ensure whether DRBD has been working properly or not. This is some testing to ensure DRBD has been worked # TESTING ON NODE1 – Create folder tmp in /mnt folder 1. mkdir /mnt/tmp – Mount DRBD devices into tmp folder who has been created 1. mount /dev/drbd0 /mnt/tmp – Create file/folder into tmp folder 1. touch /mnt/tmp/created-on-node1.txt – Please check whether file created-on-node1.txt has been there 1. ls /mnt/tmp/ – For testing/check on node2, umount DRBD devices and demoting into secondary 1. umount /dev/drbd0 2. drbdadm secondary r0 – Make sure DRBD has been demoted into Secondary 1. service drbd status # TESTING ON NODE2 – Create folder tmp in /mnt folder 1. mkdir /mnt/tmp – Promoting DRBD into Primary 1. drbdadm primary r0 – Mount DRBD devices into tmp folder who has been created 1.

How To Configure Data Replication/Synchronize on CentOS 6 Using DRBD

Hình ảnh
This article will explain how to configure data replication/synchronize using DRBD application. According this article :  http://drbd.linbit.com/ DRBD® refers to block devices designed as a building block to form high availability (HA) clusters. This is done by mirroring a whole block device via an assigned network. DRBD can be understood as network based raid-1. For configure DRBD, we should have at least 2 machines and have 2 harddrive on each machines. One harddrive will be configured as OS system and one harddrive will be configured as harddrive for replication with other harddrive on other machine In this guidance, i am build 2 systems for replication. The systems using CentOS 6 64 Bit. For easy understanding, this is my information system # Server 1 Hostname : node1 Domain : imanudin.net IP Address : 192.168.80.91 # Server 2 Hostname : node2 Domain : imanudin.net IP Address : 192.168.80.92 # Second Harddrive 1 GB on each machines for testing Purpos

How To Configure Online Failover/Failback on CentOS 6 Using Heartbeat

This article will explain how to configuration failover/failback using Heartbeat application. According this article :  http://linux-ha.org/wiki/Heartbeat Heartbeat is a daemon that provides cluster infrastructure (communication and membership) services to its clients. This allows clients to know about the presence (or disappearance!) of peer processes on other machines and to easily exchange messages with them. In this guidance, i am build 2 system for online failover. The systems using CentOS 6 64 Bit. For easy understanding, this is my information system # Server 1 Hostname : node1 Domain : imanudin.net IP Address : 192.168.80.91 # Server 2 Hostname : node2 Domain : imanudin.net IP Address : 192.168.80.92 # Alias IP for online failover testing IP Address : 192.168.80.93 # Configure Network First, we must configure network on CentOS. Assuming name of your network interface is eth0. Do the following configuration on all nodes (node1 and node2) and adjust

How To Install Zimbra 8.5.0 on CentOS 7 Part 2

Hình ảnh
After previously preparation for install Zimbra has been finished , we can install Zimbra right now. First, we can download Zimbra Binary from this link  http://www.zimbra.com/downloads/zimbra-collaboration-open-source or if you are in Indonesia region, you can download on follows link  http://mirror.linux.or.id/zimbra/binary/ . view source print ? cd /opt/ wget -c  http://files2.zimbra.com/downloads/8.5.0_GA/zcs-8.5.0_GA_3042.RHEL7_64.20140828204420.tgz After finished download, extract Zimbra, cd to folder result of extract and install Zimbra 1. tar -zxvf zcs-8.5.0_GA_3042.RHEL7_64.20140828204420.tgz 2. cd zcs-8.5.0_GA_3042.RHEL7_64.20140828204420 3. sh install .sh type Y if asking license agreement Do you agree with the terms of the software license agreement? [N] Y Select the packages to install like follows Install zimbra-ldap [Y] Y Install zimbra-logger [Y] Y Install zimbra-mta [Y] Y Install zimbra-dnscache [Y] N Install zimbra-snmp [Y] Y

How To Install Zimbra 8.5.0 on CentOS 7 Part 1

Hình ảnh
Usually, i am always using SUSE Linux Enterprise Server as operating system for Zimbra Mail Server. But, starting from Zimbra 9.x.x, SLES has been deprecated (end of life) and may be will not supported by Zimbra. Therefore, i attempt to using CentOS as operating system for Zimbra. For easy understanding, this is my information system Domain : imanudin.net Hostname : mail IP Address : 192.168.26.11 # Configure Network First, we must configure network on CentOS. Assuming name of your network interface is eth0 vi /etc/sysconfig/network-scripts/ifcfg-eth0   DEVICE=eth0 ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.26.11 NETMASK=255.255.255.0 DNS1=192.168.26.11 GATEWAY=192.168.26.2 DNS2=192.168.26.2 USERCTL=no Restart network service and setup for automatic boot 1. service network restart 2. chkconfig network on # Configure Disable Selinux & Firewall Open file /etc/sysconfig/selinux and change SELINUX=enforcing become SELINUX=d

How To Configure SPF (Sender Policy Framework) Records for Email Server

Hình ảnh
For increase reputation of email server, we could adding SPF records on public DNS. What is SPF record? as information from this link :  https://support.google.com/a/answer/33786?hl=en , an SPF record is a type of Domain Name Service (DNS) record that identifies which mail servers are permitted to send email on behalf of your domain. The purpose of an SPF record is to prevent spammers from sending messages with forged From addresses at your domain. Recipients can refer to the SPF record to determine whether a message purporting to be from your domain comes from an authorized mail server. How to configure SPF records? On this section, i will configure SPF records on my public DNS using cPanel. Fill of spf records is using TXT records like the following example :   imanudin.net     IN     TXT     "v=spf1 a mx ip4:115.124.78.180 include:mail.imanudin.net -all" OR "v=spf1 mx ip4:115.124.78.180 ~all" Information : Domain imanudin.net could be sent f

[Nginx] Compare rewrite last break

syntax rewrite regex replacement [ flag ] last – completes processing of current rewrite directives and restarts the process (including rewriting) with a search for a match on the URI from all available locations. break – completes processing of current rewrite directives and non-rewrite processing continues within the current location block only. redirect – returns temporary redirect with code 302; it is used if the substituting line begins with http:// (デフォルト) permanent – returns permanent redirect with code 301 break last /etc/nginx/conf.d/default.conf root   /usr/share/nginx/html; rewrite_log on;   location /rewrite {      rewrite ^/rewrite  /foo;      rewrite ^/foo      /bar;      add_header H-rewrite dummy; }   location /last {      rewrite ^/last     /foo last;      rewrite ^/foo      /bar last;      add_header H-last dummy; }   location /break {      rewrite ^/break    /foo break;      rewrite ^/foo      /bar break;    

[Resolved] Nginx FastCGI sent in stderr

Hình ảnh
Fix error: [error] 5331#0: *1 FastCGI sent in stderr: "Unable to open primary script: /scripts/index.php (No such file or directory)" while reading response header from upstream, client: aaa.bbb.ccc.ddd, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000" Open /etc/nginx/conf.d/default.conf Add fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; to location ~ \.php$