Senin, 16 Oktober 2017

How To Install Check Mk Agent Less than 30 second

  Tidak ada komentar
Some day i need install agent on a lot of linux server os, i need install the agent rapidly on each machine, here i share the tutorial how to install check mk agent on linux machine less thank 30 second

Installing the agent by direct download and install with following command line
Install wget and Check Mk Agent in one line command

Here the link for download the agent from github site, you can also download the check mk agent from you check mk monitoring server 

Wait untill installation finish, after finish you can testing the check mk agent installed well or not by telnet localhost on port 6556
Testing check Mk Agent

Sabtu, 30 September 2017

How to Fix Galera DB Error on restart

  Tidak ada komentar
Someday went i have success install and config MariaDb Galera MySql, my host was down, and some vm got down, went i try to restart mariadb service it's was failed, then i check the error log, and i get message like above, and did this and it was success

Edit : vi /var/lib/mysql/grastate.dat

From :

# GALERA saved state
version: 2.1
uuid:    9b22142d-a46b-11e7-9426-aa112539b203
seqno:   -1
safe_to_bootstrap: 0

To :

# GALERA saved state
version: 2.1
uuid:    9b22142d-a46b-11e7-9426-aa112539b203
seqno:   -1
safe_to_bootstrap: 1

For reference I found website that explain it more detailed :

Jumat, 29 September 2017

How to Add Your Telegram ID to your monitoring server OMD check mk

  Tidak ada komentar

Get your telegram id by typing get_id_bot in your telegram

Start the chatting and you will get id like you can see at above

Edit your check mk user name, you can find edit menu in wato, wato in javanese language is stone :D

Edit your username and fill in the telegram id with yours

Save, and apply the changes

Find your bot in your telegram

Start the conversation

if you have start, just be patient waiting for error, please don't hope for error :D

If you still confuse, you can submit your question in comment bellow 

Thank You

Kamis, 28 September 2017

How to Install and Setting Galera MariaDb Centos 6

  Tidak ada komentar


We using 3 freshly deployed VMs running a minimal install of CentOS 6.5 x86_64.
Cluster node 1 has hostname db1 and IP address
Cluster node 2 has hostname db2 and IP address
Cluster node 3 has hostname db3 and IP address

Step 1: Add MariaDB Repositories

Create a mariadb repository /etc/yum.repos.d/mariadb.repo using following content in your system.
For CentOS 6 – 64bit:
name = MariaDB
baseurl =
For CentOS 6 – 32bit:
name = MariaDB
baseurl =

Step 2 – Set SELinux in permissive mode

Before starting the setup put SELinux into permissive mode on all nodes:

sudo setenforce0

Step 3 – Install MariaDB Galera Cluster 10.0 software

If you did a CentOS 6 minimal installation then make sure you install the socat package from the EPEL repository before proceeding with installing the MariaDB Galera Cluster 10.0 software.
You can install socat package directly from EPEL with the following command (for x86_64):
sudo yum install
On CentOS 7 you can install socat package with following command.
sudo yum install socat
Install the MariaDB Galera Cluster 10.0 software by executing the following command on all nodes:
sudo yum install MariaDB-Galera-server MariaDB-client rsync galera

Step 4:  Setup MariaDB security

Start the mysql ( init script in MariaDB 10.0 is still called mysql)
sudo service mysql start
Run the mysql_secure_installation script so we can improve the security. Run the following command on all nodes:
sudo /usr/bin/mysql_secure_installation
I choose password as ‘dbpass’ and accepted all defaults (so answered yes to all questions).

Step 5 – Create MariaDB Galera Cluster users

Now, we have to create some users that must be able to access the database. The ‘sst_user’ is the user which a database node will use for authenticating to another database node in the State Transfer Snapshot (SST) phase. Run the following command on all nodes:
mysql -u root -p
mysql> DELETE FROM mysql.user WHERE user='';
mysql> GRANT ALL ON *.* TO 'root'@'%' IDENTIFIED BY 'dbpass';
mysql> GRANT USAGE ON *.* to sst_user@'%' IDENTIFIED BY 'dbpass';
mysql> GRANT ALL PRIVILEGES on *.* to sst_user@'%';
mysql> quit
You are suggested to change ‘%’ to hostname(s) or IP addresses from which those users can access the database. Because ‘%’ means that the root or sst_user is allowed to access the database from any host, So less security.

Step 6 – Create the MariaDB Galera Cluster config

First stop the mysql services on all nodes:
sudo service mysql stop
Next, We are going to create the MariaDB Galera Cluster configuration by the following command on all nodes (go through the IMPORTANT NOTE after the config and make required changes for db2, and db3):
sudo cat >> /etc/my.cnf.d/server.cnf << EOF
IMPORTANT NOTE: when executing this command on db2 and db3 do not forget to adjust the wsrep_node_address and wsrep_node_name variables. 
On Db2

On db3 :

Step 7– Initialize the first cluster node

Start MariaDB with the special ‐‐wsrep-new-cluster’ option , Do it on node db1 only so the primary node of the cluster is initialized:
sudo /etc/init.d/mysql start --wsrep-new-cluster
Check status by run the following command on node db1 only:
mysql-uroot-p-e"show status like 'wsrep%'"
Some important information in the output are the following lines:
wsrep_local_state_comment | Synced <-- cluster is synced
wsrep_incoming_addresses  | <-- node db1 is a provider
wsrep_cluster_size        | 1 <-- cluster consists of 1 node 
wsrep_ready               | ON <-- good :)

Step 8– Add the other cluster nodes

Check and confirm nodes db2 and db3 have the correct configuration in /etc/my.cnf.d/server.cnf under the [mariadb-10.0] as described in step 6.
With the correct configuration in place, all that is required to make db2 and db3 a member of the cluster is to start them like you would start any regular service. On db2 issue the following command:
sudo service mysql start
Check what has changed in the cluster status by executing the following command on db1 or db2:
mysql -u root -p -e "show status like 'wsrep%'"
And you will see that node db2 is now known as the cluster size is ‘2’ and the IP address of node db2 is listed:
| wsrep_local_state_comment | Synced                    |
| wsrep_incoming_addre sses |, |
| wsrep_cluster_size        | 2                         |
| wsrep_connected           | ON                        |
| wsrep_ready               | ON                        |
Repeat the same step for node db3. On node db3 only execute the following command
sudo service mysql start
Check what has changed in the cluster status by executing the following command on for example db1:
mysql -u root -p -e "show status like 'wsrep%'"
And you should see that node db3 is now known as the cluster size is ‘3’ and the IP address of node db3 is listed:
| wsrep_local_state_comment | Synced                                 |
| wsrep_incoming_addresses  |,, |
| wsrep_cluster_size        | 3                                      |
| wsrep_connected           | ON                                     |
| wsrep_ready               | ON                                     |

Step 9 – Verify replication

Now the cluster is running. Let’s test whether it is working. On db1 create a database ‘clustertest’ by run the following command:
mysql -u root -p -e 'CREATE DATABASE clustertest;'
mysql -u root -p -e 'CREATE TABLE clustertest.mycluster ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(50), ipaddress VARCHAR(20), PRIMARY KEY(id));'
mysql -u root -p -e 'INSERT INTO clustertest.mycluster (name, ipaddress) VALUES ("db1", "");'
Check if the database, table and data exists:
mysql -u root -p -e 'SELECT * FROM clustertest.mycluster;'
Enter password: 
| id | name | ipaddress |
| 2  | db1  |   |
Now do the check on node db2:
mysql -u root -p -e 'SELECT * FROM clustertest.mycluster;'
Enter password: 
| id | name | ipaddress |
| 2  | db1  |   |
Now do the same check on node db3:
mysql -u root -p -e 'SELECT * FROM clustertest.mycluster;'
Enter password: 
| id | name | ipaddress |
| 2  | db1  |   |
From these outputs we can confirm that everything was successfully replicated by node db1 across all other nodes.

How to setting Galera Replication mariadb cluster centos 7

  Tidak ada komentar

3 buah web server+mariadb+wordpress
  • = hostname galera1 = bootstrap / –wsrep-new-cluster
  • = hostname galera2
  • = hostname galera3
Jangan lupa disable selinux
Ganti “enforcing” dengan “disabled”
Pertama tambahkan repo mariadb
Lalu tambahkan konten ini didalamnya 
Then edit this file :
Lalu tambahkan konten dibawah ini didalamnya
Selanjutnya install mariadb galera
Selanjutnya edit file /etc/my.cnf.d/server.cnf dan uncomment juga tambahkan baris seperti dibawah
# These groups are read by MariaDB server. Use it for options that only the serv                                                      er (but not clients) should see
# See the examples of server my.cnf files in /usr/share/mysql/
# this is read by the standalone daemon and embedded servers
# this is only for the mysqld standalone daemon
# * Galera-related settings
# Mandatory settings
wsrep_cluster_address="gcomm://,,"                                                      168.72.91,,"
# Custom settings
# this is only for embedded server
# This group is only read by MariaDB servers, not by MySQL.
#If you use the same .cnf file for MySQL and MariaDB,
#you can put MariaDB-only options here
# This group is only read by MariaDB-10.0 servers.
#If you use the same .cnf file for MariaDB of different versions,
#use this group for options that older servers don't understand
Rubah wsrep_node_address script diatas pada masing2 server menjadi seperti dibawah
  • Server galera1 = wsrep_node_address=”″
  • Server galera2 = wsrep_node_address=”″
  • Server galera3 = wsrep_node_address=”″
Penjelasan dari rule diatas
  • wsrep_cluster_address : untuk mendifinisikan ipaddress server mana saja yang nanti akan masuk kedalam lingkungan grup cluster
  • wsrep_cluster_name : nama untuk grup cluster, namanya harus sama pada setiap server yang masuk kedalam wsrep_cluster_address
  • wsrep_node_address : diisikan dengan alamat ip server masing-masing node (jika anda setting di galera1 maka isikan dengan ip galera1, jika anda setting di galera2 isikan dengan ip galera2 dan seterusnya begitu)
  • wsrep_sst_method : metode yang digunakan untuk replikasi db nya
sekarang jalankan perintah ini hanya pada server galera1
/etc/init.d/mysql start --wsrep-new-cluster
Lalu coba jalankan perintah ini pada server galera1
mysql -u root -p -e "show status like 'wsrep%'"
coba lihat pada baris “wsrep_incoming_addresses” ip nya baru 1
| wsrep_incoming_addresses ||
Selanjutnya jalankan perintah ini pada server galera2 & galera3
/etc/init.d/mysql start
Lalu coba jalankan lagi perintah ini pada server galera1
mysql -u root -p -e "show status like 'wsrep%'"
Dan coba lihat kali ini pada baris “wsrep_incoming_addresses” sudah ada 3 ip
| wsrep_incoming_addresses |,, |
Oke tandanya kita sudah berhasil

Setting up the firewalld

Now when all three nodes are connected we can bring up firewalld and configure it.
# systemctl start firewalld
Open the mariadb client and galera replication ports:
# firewall-cmd --permanent --add-port=3306/tcp
# firewall-cmd --permanent --add-port=4567/tcp
Open rsync port that we use for replication
# firewall-cmd --permanent --add-port=873/tcp
Other important ports
# firewall-cmd --permanent --add-port=4444/tcp
# firewall-cmd --permanent --add-port=9200/tcp
Lastly reload the firewall
# firewall-cmd --reload
Reference :