Monitoring | Записки системного администратора

Архивы рубрики ‘Monitoring’

Настройка мониторинга MySQL в Cacti средствами Percona Monitoring Plugins

Январь 3rd, 2016

Evgeniy Kamenev

1.Копируем скрипт ss_get_mysql_stats.php в папку <path_to_Cacti>/scripts/

# cp  percona-monitoring-plugins-1.1.5/cacti/scripts/ss_get_mysql_stats.php /usr/share/cacti/scripts/

1	# cp percona-monitoring-plugins-1.1.5/cacti/scripts/ss_get_mysql_stats.php /usr/share/cacti/scripts/

# chmod +x /usr/share/cacti/scripts/ss_get_mysql_stats.php

1	# chmod +x /usr/share/cacti/scripts/ss_get_mysql_stats.php

2.Разрешаем на клиенте MySQL-подключение с Cacti-сервера

# nano /etc/my.cnf

1	# nano /etc/my.cnf

#bind_address = 127.0.0.1
bind_address = 0.0.0.0

1 2	#bind_address = 127.0.0.1 bind_address = 0.0.0.0

# service mysql restart

1	# service mysql restart

# netstat -nlpt | grep mysql

1	# netstat -nlpt \| grep mysql

tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      20359/mysqld

1	tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 20359/mysqld

Настройка firewall

# iptables -N mysql

1	# iptables -N mysql

# iptables -A INPUT -p tcp --dport 3306 -j mysql

1	# iptables -A INPUT -p tcp --dport 3306 -j mysql

# iptables -A mysql -s <IP-address-Cacti-server> -j ACCEPT

1	# iptables -A mysql -s <IP-address-Cacti-server> -j ACCEPT

# iptables -A mysql -j LOG --log-prefix "input mysql: "

1	# iptables -A mysql -j LOG --log-prefix "input mysql: "

# iptables -A mysql -j DROP

1	# iptables -A mysql -j DROP

Или просто (подразумевается,что политика по умолчанию для цепочки INPUT установлена в DROP)

# iptables -A INPUT -p tcp --dport 3306 -s <IP-address-Cacti-server> -j ACCEPT

1	# iptables -A INPUT -p tcp --dport 3306 -s <IP-address-Cacti-server> -j ACCEPT

Создаем пользователя с необходимыми правами, который будет подключаться с Cacti-сервера

mysql>  GRANT SUPER, PROCESS ON *.* TO 'cactipercona'@'%' IDENTIFIED BY "secret";

1	mysql> GRANT SUPER, PROCESS ON . TO 'cactipercona'@'%' IDENTIFIED BY "secret";

mysql> flush privileges;

1	mysql> flush privileges;

3.Тестируем mysql-подключение […]

Опубликовано в рубрике Centos, Monitoring

Метки: Cacti, mysql, Percona, Percona Monitoring Plugins

Комментарии отключены

Настройка мониторинга Linux-хоста в Cacti средствами Percona Monitoring Plugins

Декабрь 31st, 2015

Evgeniy Kamenev

Шаблон для мониторинга Linux-хоста использует ssh-подключение к хосту. 1.Необходимо произвести настройки согласно пунктам 1-6 из этой статьи https://kamaok.org.ua/?p=1409 2.Импортирование шаблона У меня используется spine вместо cmd.php и частота запуска определена как 60 секунд (вместо дефолтных 300 секунд).Поэтому перед импортированием шаблона от Percona, в котором также используется 300 секунд, необходимо изменить частоту запуска на 60 […]

Опубликовано в рубрике Centos, Monitoring

Метки: Cacti, linux, monitoring, Percona, Percona Monitoring Plugins

Комментарии отключены

Настройка мониторинга Nginx, Memcached, Redis в Cacti средствами Percona Monitoring Plugins

Декабрь 31st, 2015

Evgeniy Kamenev

Мониторинг Nginx 1.Узнаем под каким пользователем запускается poller

# grep -ri cacti /etc/cron*

1	# grep -ri cacti /etc/cron*

/etc/cron.d/cacti:* * * * *     cacti   /usr/bin/php /usr/share/cacti/poller.php > /dev/null 2>&1

1	/etc/cron.d/cacti:* * * * * cacti /usr/bin/php /usr/share/cacti/poller.php > /dev/null 2>&1

В данном случае под пользователем cacti 2. Создаем пару SSH-ключей без пароля и сохраняем ключи в /etc/cacti

# ssh-keygen

1	# ssh-keygen

Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): /etc/cacti/id_rsa
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /etc/cacti/id_rsa.
Your public key has been saved in /etc/cacti/id_rsa.pub.

Generating public/private rsa key pair.

Enter file in which to save the key (/root/.ssh/id_rsa): /etc/cacti/id_rsa

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /etc/cacti/id_rsa.

Your public key has been saved in /etc/cacti/id_rsa.pub.

3.Выставляем корректного владельца на ключи – пользователя cacti

# chown cacti /etc/cacti/id_rsa*

1	# chown cacti /etc/cacti/id_rsa*

# ls -al /etc/cacti/ | grep id

1	# ls -al /etc/cacti/ \| grep id

-rw-------   1 cacti root   1679 Dec 29 22:52 id_rsa
-rw-r--r--   1 cacti root    406 Dec 29 22:52 id_rsa.pub

1 2	-rw------- 1 cacti root 1679 Dec 29 22:52 id_rsa -rw-r--r-- 1 cacti root 406 Dec 29 22:52 id_rsa.pub

4.Создаем пользователя,например, cacti на клиенте(192.168.1.100), с которого будет сниматься статитика

# ssh -p 2220 root@192.168.1.100 adduser cacti

1	# ssh -p 2220 root@192.168.1.100 adduser cacti

[…]

Опубликовано в рубрике Centos, Monitoring

Метки: Cacti, memcached, Nginx, Percona, Percona Monitoring Plugins, redis

Комментарии отключены

Настройка мониторинга дисковой подсистемы в Cacti

Декабрь 29th, 2015

Evgeniy Kamenev

1.Загружаем и распаковываем архив Cacti_Net-SNMP_DevIO_v3.1

# unzip Cacti_Net-SNMP_DevIO_v3.1.zip

1	# unzip Cacti_Net-SNMP_DevIO_v3.1.zip

2.Копируем файл net-snmp_devio.xml на Cacti сервер в каталог resource/snmp_queries/

# cp net-snmp_devio.xml /usr/share/cacti/resource/snmp_queries/

1	# cp net-snmp_devio.xml /usr/share/cacti/resource/snmp_queries/

3.Импортируем по очереди шаблоны

Console->Import Templates

1	Console->Import Templates

net-snmp_devIO-BytesRW_graph_TMPL.xml

1	net-snmp_devIO-BytesRW_graph_TMPL.xml

net-snmp_devIO-LoadAVG_graph_TMPL.xml

1	net-snmp_devIO-LoadAVG_graph_TMPL.xml

net-snmp_devIO-ReadsWrites_graph_TMPL.xml

1	net-snmp_devIO-ReadsWrites_graph_TMPL.xml

И самым последним импортируем шаблон

net-snmp_devIO-Data_query.xml

1	net-snmp_devIO-Data_query.xml

4.Добавляем новый Data Queries

Console->Devices->ServerName->Associated Data Queries->ucd/net – Get Device I/O и Re-Indexed Method->Index count Changed->Add

1	Console->Devices->ServerName->Associated Data Queries->ucd/net – Get Device I/O и Re-Indexed Method->Index count Changed->Add

5.Создаем графики

Console->Devices->ServerName->Create Graphs for this Host->Data Query->

1	Console->Devices->ServerName->Create Graphs for this Host->Data Query->

выбираем устройства(диски),например, vda, sda(либо разделы sda1, sda2 и т.д.)->graph type-> Bytes Read/Written Аналогично […]

Опубликовано в рубрике Monitoring, Monitoring

Комментарии отключены

Настройка мониторинга PHP-FPM в Cacti

Декабрь 28th, 2015

Evgeniy Kamenev

Есть три сайта, каждый из которых использует свой PHP-FPM-пул

kamaok.us - /etc/php-fpm.d/kamaok.conf
joomla.us - /etc/php-fpm.d/joomla.conf
wordpress.us - /etc/php-fpm.d/wordpress.conf

kamaok.us - /etc/php-fpm.d/kamaok.conf

joomla.us - /etc/php-fpm.d/joomla.conf

wordpress.us - /etc/php-fpm.d/wordpress.conf

И дефолтный сайт

default.us - /etc/php-fpm.d/www.conf

1	default.us - /etc/php-fpm.d/www.conf

1.Настройка PHP-FPM для снятия статистки Включаем отображение статуса для каждого php-fpm-пула

# nano /etc/php-fpm.d/kamaok.conf

1	# nano /etc/php-fpm.d/kamaok.conf

pm.status_path = /status-kamaok
ping.path = /ping-kamaok

1 2	pm.status_path = /status-kamaok ping.path = /ping-kamaok

# nano /etc/php-fpm.d/joomla.conf

1	# nano /etc/php-fpm.d/joomla.conf

pm.status_path = /status-joomla
ping.path = /ping-joomla

1 2	pm.status_path = /status-joomla ping.path = /ping-joomla

# nano /etc/php-fpm.d/wordpress.conf

1	# nano /etc/php-fpm.d/wordpress.conf

pm.status_path = /status-wordpress
ping.path = /ping-wordpress

1 2	pm.status_path = /status-wordpress ping.path = /ping-wordpress

# nano /etc/php-fpm.d/www.conf

1	# nano /etc/php-fpm.d/www.conf

pm.status_path = /status
ping.path = /ping

1 2	pm.status_path = /status ping.path = /ping

# php5-fpm –t

1	# php5-fpm –t

# service php-fpm reload

1	# service php-fpm reload

2.Настройка Nginx для отображения PHP-FPM-статистики Настраиваем все пулы в дефолтном Nginx хосте

# nano /etc/nginx/conf.d/default.conf

1	# nano /etc/nginx/conf.d/default.conf

location ~ ^/(status-kamaok|ping-kamaok)$ {
    fastcgi_pass   unix:/var/run/php5-fpm.kamaok.sock;
    fastcgi_index index.php;
    fastcgi_param  SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
    access_log   off;
    allow 127.0.0.1;
    allow 192.168.1.0/24;
    allow <IP-address-Cacti-server>; 
    deny all;
}

location ~ ^/(status-wordpress|ping-wordpress)$ {
    fastcgi_pass   unix:/var/run/php5-fpm.wordpress.sock;
    fastcgi_index index.php;
    fastcgi_param  SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
    access_log   off;
    allow 127.0.0.1;
    allow 192.168.1.0/24;
    allow <IP-address-Cacti-server>; 
    deny all;
}

location ~ ^/(status-joomla|ping-joomla)$ {
    fastcgi_pass   unix:/var/run/php5-fpm.joomla.sock;
    fastcgi_index index.php;
    fastcgi_param  SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
    access_log   off;
    allow 127.0.0.1;
    allow 192.168.1.0/24;
   allow <IP-address-Cacti-server>; 
    deny all;
}

location ~ ^/(status|ping)$ {
    fastcgi_pass   unix:/var/run/php5-fpm.sock;
    fastcgi_index index.php;
    fastcgi_param  SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
    access_log   off;
    allow 127.0.0.1;
    allow 192.168.1.0/24;
    allow <IP-address-Cacti-server>; 
    deny all;
}

location ~ ^/(status-kamaok|ping-kamaok)$ {

fastcgi_pass unix:/var/run/php5-fpm.kamaok.sock;

fastcgi_index index.php;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

include fastcgi_params;

access_log off;

allow 127.0.0.1;

allow 192.168.1.0/24;

allow <IP-address-Cacti-server>;

deny all;

}

location ~ ^/(status-wordpress|ping-wordpress)$ {

fastcgi_pass unix:/var/run/php5-fpm.wordpress.sock;

fastcgi_index index.php;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

include fastcgi_params;

access_log off;

allow 127.0.0.1;

allow 192.168.1.0/24;

allow <IP-address-Cacti-server>;

deny all;

}

location ~ ^/(status-joomla|ping-joomla)$ {

fastcgi_pass unix:/var/run/php5-fpm.joomla.sock;

fastcgi_index index.php;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

include fastcgi_params;

access_log off;

allow 127.0.0.1;

allow 192.168.1.0/24;

allow <IP-address-Cacti-server>;

deny all;

}

location ~ ^/(status|ping)$ {

fastcgi_pass unix:/var/run/php5-fpm.sock;

fastcgi_index index.php;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

include fastcgi_params;

access_log off;

allow 127.0.0.1;

allow 192.168.1.0/24;

allow <IP-address-Cacti-server>;

deny all;

}

# nginx –t

1	# nginx –t

# service nginx reload

1	# service nginx reload

Локально с […]

Опубликовано в рубрике Centos, Monitoring

Метки: Cacti, PHP-FPM

Комментарии отключены

Настройка мониторинга Nginx в Cacti

Декабрь 28th, 2015

Evgeniy Kamenev

1.Проверяем наличие поддержки http_stub_status модуля.

# nginx -V 2>&1 | grep -o http_stub_status_module

1	# nginx -V 2>&1 \| grep -o http_stub_status_module

http_stub_status_module

1	http_stub_status_module

2.Настраиваем хост по умолчанию на отображение статистики Nginx.

# nano /etc/nginx/conf.d/default.conf

1	# nano /etc/nginx/conf.d/default.conf

location /nginx_status {
        stub_status on;
        access_log   off;
        allow 127.0.0.1;
        allow 192.168.1.0/24;
        allow <IP_address_Cacti_server>; 
        deny all;
        }

location /nginx_status {

stub_status on;

access_log off;

allow 127.0.0.1;

allow 192.168.1.0/24;

allow <IP_address_Cacti_server>;

deny all;

}

# nginx –t

1	# nginx –t

# service nginx reload

1	# service nginx reload

Проверяем вывод Nginx-статистики

# lynx http://<ip-address-client>/nginx_status

1	# lynx http://<ip-address-client>/nginx_status

Active connections: 1
server accepts handled requests
 3 3 10
Reading: 0 Writing: 1 Waiting: 0

Active connections: 1

server accepts handled requests

3 3 10

Reading: 0 Writing: 1 Waiting: 0

3.Скачиваем необходимые скрипты/шаблоны и копируем скрипты get_nginx_clients_status, get_nginx_socket_status в папку scripts на сервере Cacti. Отсюда качаем необходимые скрипты/шаблоны http://forums.cacti.net/about26458.html Либо с моего сайта cacti-nginx.tar Выставляем корректные права на скрипты […]

Опубликовано в рубрике Centos, Monitoring

Метки: Cacti, Nginx

Комментарии отключены

Тестирование скорости чтения-записи жесткого диска в Linux

Июнь 26th, 2014

Evgeniy Kamenev

Установка необходимых утилит Centos:

# yum install hdparm seeker

1	# yum install hdparm seeker

Запись

# dd if=/dev/sda3 of=/tmp/test.file bs=1M count=1000 conv=fdatasync

1	# dd if=/dev/sda3 of=/tmp/test.file bs=1M count=1000 conv=fdatasync

1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 34.508 seconds, 30.4 MB/s

1000+0 records in

1000+0 records out

1048576000 bytes (1.0 GB) copied, 34.508 seconds, 30.4 MB/s

# dd if=/dev/sdb3 of=/tmp/test.file bs=1M count=1000 conv=fdatasync

1	# dd if=/dev/sdb3 of=/tmp/test.file bs=1M count=1000 conv=fdatasync

1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 35.5427 seconds, 29.5 MB/s

1000+0 records in

1000+0 records out

1048576000 bytes (1.0 GB) copied, 35.5427 seconds, 29.5 MB/s

# dd if=/dev/zero of=/tmp/test.file bs=1M count=1000 conv=fdatasync

1	# dd if=/dev/zero of=/tmp/test.file bs=1M count=1000 conv=fdatasync

Используем ключ conv=fdatasync, чтобы данные синхронизировались с диском и не оставались в памяти т.к. наличие данных в буферах памяти не дает реальной скорости записи. Чтение dd Очищаем кеш и измеряем реальную скорость чтения с диска

# sysctl -w vm.drop_caches=3

1	# sysctl -w vm.drop_caches=3

# dd if=/tmp/test.file of=/dev/null bs=1M count=1000

1	# dd if=/tmp/test.file of=/dev/null bs=1M count=1000

Hdparm Ключ

-t

-t

( Timing buffered disk) […]

Опубликовано в рубрике Centos, Monitoring, Monitoring Tools, Other

Метки: dd, hdparm, seeker

Комментарии отключены

Установка и настройка smartmontools для мониторинга состояния жесткого диска

Май 12th, 2014

Evgeniy Kamenev

1.Установка smartmontools

# yum install smartmontools

1	# yum install smartmontools

2.Настройка smartd-демона

# cp /etc/smartd.conf /etc/smartd.conf~

1	# cp /etc/smartd.conf /etc/smartd.conf~

# nano /etc/smartd.conf

1	# nano /etc/smartd.conf

DEVICESCAN -H -m your@email

1	DEVICESCAN -H -m your@email

# /etc/init.d/smartd start

1	# /etc/init.d/smartd start

# chkconfig --level 2345 smartd on

1	# chkconfig --level 2345 smartd on

3. Работа с smartctl-утилитой Просмотр,какие диски у нас есть

# ls -la /dev/ | grep sd

1	# ls -la /dev/ \| grep sd

Проверка состояния здоровья винчестеров

# smartctl -H /dev/sda

1	# smartctl -H /dev/sda

# smartctl -H /dev/sdb

1	# smartctl -H /dev/sdb

Информация о диске, а также просмотр,включен ли SMART

# smartctl -i /dev/sda

1	# smartctl -i /dev/sda

Если отключен SMART, то включаем его

# smartctl -s on /dev/sda

1	# smartctl -s on /dev/sda

Если нужно выключить SMART

# smartctl -s off /dev/sda

1	# smartctl -s off /dev/sda

По умолчанию smartd будет проверять состояние дисков каждые […]

Опубликовано в рубрике Centos, Monitoring

Метки: S.M.A.R.T, smartctl, smartd, smartmontools

Комментарии отключены

Установка и настройка Monit на Centos

Февраль 5th, 2014

Evgeniy Kamenev

1.Установка и настройка Monit

# yum install monit

1	# yum install monit

# cp /etc/monit.conf /etc/monit.conf~

1	# cp /etc/monit.conf /etc/monit.conf~

# nano /etc/monit.d/logging

1	# nano /etc/monit.d/logging

set logfile /var/log/monit.log

1	set logfile /var/log/monit.log

# cat /etc/monit.conf | grep -v "#"

1	# cat /etc/monit.conf \| grep -v "#"

set daemon  60 with start delay 240
set logfile /var/log/monit.log
set idfile /var/.monit.id
set statefile /var/.monit.state
set mailserver localhost
set eventqueue
set alert root@localhost not {instance}
set httpd port 2812 and
allow localhost
allow 192.168.1.0/24
allow monit:password
check system lb02.kamaok.org.ua

if loadavg (1min) > 6 then alert
if loadavg (5min) > 3 then alert
if memory usage > 75% then alert
if cpu usage (user) > 70% then alert
if cpu usage (system) > 30% then alert
if cpu usage (wait) > 20% then alert

check file messages with path /var/log/messages
    if match 'OOM killed process' then alert
    if match 'temperature above threshold' then alert
    if match 'table full, dropping packet' then alert
    if match 'OOM killed process' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"
    if match 'temperature above threshold' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"
    if match 'table full, dropping packet' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"

set daemon 60
include /etc/monit.d/*

set daemon 60 with start delay 240

set logfile /var/log/monit.log

set idfile /var/.monit.id

set statefile /var/.monit.state

set mailserver localhost

set eventqueue

set alert root@localhost not {instance}

set httpd port 2812 and

allow localhost

allow 192.168.1.0/24

allow monit:password

check system lb02.kamaok.org.ua

if loadavg (1min) > 6 then alert

if loadavg (5min) > 3 then alert

if memory usage > 75% then alert

if cpu usage (user) > 70% then alert

if cpu usage (system) > 30% then alert

if cpu usage (wait) > 20% then alert

check file messages with path /var/log/messages

if match 'OOM killed process' then alert

if match 'temperature above threshold' then alert

if match 'table full, dropping packet' then alert

if match 'OOM killed process' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"

if match 'temperature above threshold' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"

if match 'table full, dropping packet' for 2 cycles then exec "/bin/bash -c '/usr/bin/monit unmonitor messages && /bin/sleep 3600 && /usr/bin/monit monitor messages'"

set daemon 60

include /etc/monit.d/*

# nano /etc/monit.d/services.conf

1	# nano /etc/monit.d/services.conf

# Мониторинг самого Monit-сервера

#check process httpd with pidfile /var/run/httpd/httpd.pid
#start program = "/etc/init.d/httpd start"  
#stop program  = "/etc/init.d/httpd stop"
#if failed host 127.0.0.1 port 80 protocol http then alert
#if 5 restarts within 5 cycles then timeout

#check process exim with pidfile /var/run/exim.pid
#start program = "/etc/init.d/exim start"  
#stop program  = "/etc/init.d/exim stop"
#if 5 restarts within 5 cycles then timeout

check process nginx with pidfile /var/run/nginx.pid
start program = "/etc/init.d/nginx start"
stop program  = "/etc/init.d/nginx stop"
if failed host 192.168.1.60 port 80 protocol http then alert
if 3 restarts within 3 cycles then timeout

check process named with pidfile /var/run/named.pid
start program = "/etc/init.d/named start"  
stop program  = "/etc/init.d/named stop"
if 5 restarts within 5 cycles then timeout

check process fail2ban with pidfile /var/run/fail2ban/fail2ban.pid
start program = "/etc/init.d/fail2ban start"  
stop program  = "/etc/init.d/fail2ban stop"
if 5 restarts within 5 cycles then timeout

#check process proftpd with pidfile /var/run/proftpd.pid
#start program = "/etc/init.d/proftpd start"
#stop program  = "/etc/init.d/proftpd stop"
#if failed port 21 protocol ftp then restart
#if 5 restarts within 5 cycles then timeout

check process dkim-milter with pidfile /var/run/dkim-milter/dkim-milter.pid
start program = "/etc/init.d/dkim-milter start"
stop program  = "/etc/init.d/dkim-milter stop"
if failed host 127.0.0.1 port 8891  then restart
if 5 restarts within 5 cycles then timeout

check process memcached with pidfile /var/run/memcached/memcached.pid
start program = "/etc/init.d/memcached start"
stop program  = "/etc/init.d/memcached stop"
if failed host 127.0.0.1 port 11211  then restart
if 3 restarts within 5 cycles then timeout

check process redis-server with pidfile /var/run/redis/redis.pid
start program = "/etc/init.d/redis start"
stop program  = "/etc/init.d/redis stop"
if failed host 127.0.0.1 port 6379  then restart
if 3 restarts within 5 cycles then timeout

check process rsyslog with pidfile /var/run/syslogd.pid
start program = "/etc/init.d/rsyslog start"
stop program  = "/etc/init.d/rsyslog stop"
if 3 restarts within 5 cycles then timeout

check process php-fpm with pidfile /var/run/php-fpm/php-fpm.pid
start program = "/etc/init.d/php-fpm start"
stop program  = "/etc/init.d/php-fpm stop"
if failed unixsocket /var/run/php5-fpm.sock then restart
#if failed host 127.0.0.1 port 9000 then restart
if 3 restarts within 5 cycles then timeout

check process atop with pidfile /var/run/atop.pid
start program = "/etc/init.d/atop start"
stop program  = "/etc/init.d/atop stop"
if 3 restarts within 5 cycles then timeout

check process munin-node with pidfile /var/run/munin/munin-node.pid
start program = "/etc/init.d/munin-node start"
stop program  = "/etc/init.d/munin-node stop"
if failed host 127.0.0.1 port 4949  then restart
if 3 restarts within 5 cycles then timeout

check process openvpn with pidfile /var/run/openvpn/openvpn.pid
start program = "/etc/init.d/openvpn start"
stop program  = "/etc/init.d/openvpn stop"
if failed host 192.168.1.60 port 1194  then restart
if 3 restarts within 5 cycles then timeout

check process keepalived with pidfile /var/run/keepalived.pid
start program = "/etc/init.d/keepalived start"  #with timeout 60 seconds
stop program  = "/etc/init.d/keepalived stop"

check process sshd with pidfile /var/run/sshd.pid
start program = "/etc/init.d/sshd start"  
stop program  = "/etc/init.d/sshd stop"
if failed port 22 protocol ssh then restart
if 5 restarts within 5 cycles then timeout

check process dovecot with pidfile /var/run/dovecot/master.pid
start program = "/etc/init.d/dovecot start"  
stop program  = "/etc/init.d/dovecot stop"
if 3 restarts within 3 cycles then timeout

check process ntpd with pidfile /var/run/ntpd.pid
start program = "/etc/init.d/ntpd start"  
stop program  = "/etc/init.d/ntpd stop"
if failed host 127.0.0.1 port 123 type udp then alert
if 5 restarts within 5 cycles then timeout

check process crond with pidfile /var/run/crond.pid
start program = "/etc/init.d/crond start"  
stop program  = "/etc/init.d/crond stop"

check process postfix with pidfile /var/spool/postfix/pid/master.pid
start program = "/etc/init.d/postfix start"
stop  program = "/etc/init.d/postfix stop"
if failed port 25 protocol smtp then restart
if 5 restarts within 5 cycles then timeout

check process mmm_agentd with pidfile /var/run/mysql-mmm/mmm_agentd.pid
start program = "/etc/init.d/mysql-mmm-agent start"
stop  program = "/etc/init.d/mysql-mmm-agent stop"
if 5 restarts within 5 cycles then timeout

check process mysql with pidfile /var/lib/mysql/lb02.kamaok.org.ua.pid
start program = "/etc/init.d/mysql start"
stop program = "/etc/init.d/mysql stop"
if 5 restarts within 5 cycles then timeout



#Подключения оповещения при недоступности определенных портов на различных удаленных серверах

check host lb01.kamaok.org.ua  with address 192.168.1.61
if failed icmp type echo count 5 with timeout 10 seconds then alert
if failed port 22 protocol ssh then alert
if failed port 4949  then alert
if failed port 80 then alert
if failed port 11211  then alert
if failed port 25  then alert
if failed port 143  then alert
if failed port 11211  then alert

check host app01.kamaok.org.ua  with address 192.168.1.63
if failed icmp type echo count 5 with timeout 10 seconds then alert
if failed port 22 protocol ssh then alert
if failed port 4949  then alert
if failed port 9989  then alert
if failed port 80 protocol HTTP then alert
if failed port 11211  then alert
if failed port 25  then alert
if failed port 8080  then alert

check host app02.kamaok.org.ua  with address 192.168.1.64
if failed icmp type echo count 5 with timeout 10 seconds then alert
if failed port 22 protocol ssh then alert
if failed port 4949  then alert
if failed port 9989  then alert
if failed port 80 protocol HTTP then alert
if failed port 11211  then alert
if failed port 25  then alert
if failed port 8080  then alert

alert root@localhost

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

# Мониторинг самого Monit-сервера

#check process httpd with pidfile /var/run/httpd/httpd.pid

#start program = "/etc/init.d/httpd start"

#stop program = "/etc/init.d/httpd stop"

#if failed host 127.0.0.1 port 80 protocol http then alert

#if 5 restarts within 5 cycles then timeout

#check process exim with pidfile /var/run/exim.pid

#start program = "/etc/init.d/exim start"

#stop program = "/etc/init.d/exim stop"

#if 5 restarts within 5 cycles then timeout

check process nginx with pidfile /var/run/nginx.pid

start program = "/etc/init.d/nginx start"

stop program = "/etc/init.d/nginx stop"

if failed host 192.168.1.60 port 80 protocol http then alert

if 3 restarts within 3 cycles then timeout

check process named with pidfile /var/run/named.pid

start program = "/etc/init.d/named start"

stop program = "/etc/init.d/named stop"

if 5 restarts within 5 cycles then timeout

check process fail2ban with pidfile /var/run/fail2ban/fail2ban.pid

start program = "/etc/init.d/fail2ban start"

stop program = "/etc/init.d/fail2ban stop"

if 5 restarts within 5 cycles then timeout

#check process proftpd with pidfile /var/run/proftpd.pid

#start program = "/etc/init.d/proftpd start"

#stop program = "/etc/init.d/proftpd stop"

#if failed port 21 protocol ftp then restart

#if 5 restarts within 5 cycles then timeout

check process dkim-milter with pidfile /var/run/dkim-milter/dkim-milter.pid

start program = "/etc/init.d/dkim-milter start"

stop program = "/etc/init.d/dkim-milter stop"

if failed host 127.0.0.1 port 8891 then restart

if 5 restarts within 5 cycles then timeout

check process memcached with pidfile /var/run/memcached/memcached.pid

start program = "/etc/init.d/memcached start"

stop program = "/etc/init.d/memcached stop"

if failed host 127.0.0.1 port 11211 then restart

if 3 restarts within 5 cycles then timeout

check process redis-server with pidfile /var/run/redis/redis.pid

start program = "/etc/init.d/redis start"

stop program = "/etc/init.d/redis stop"

if failed host 127.0.0.1 port 6379 then restart

if 3 restarts within 5 cycles then timeout

check process rsyslog with pidfile /var/run/syslogd.pid

start program = "/etc/init.d/rsyslog start"

stop program = "/etc/init.d/rsyslog stop"

if 3 restarts within 5 cycles then timeout

check process php-fpm with pidfile /var/run/php-fpm/php-fpm.pid

start program = "/etc/init.d/php-fpm start"

stop program = "/etc/init.d/php-fpm stop"

if failed unixsocket /var/run/php5-fpm.sock then restart

#if failed host 127.0.0.1 port 9000 then restart

if 3 restarts within 5 cycles then timeout

check process atop with pidfile /var/run/atop.pid

start program = "/etc/init.d/atop start"

stop program = "/etc/init.d/atop stop"

if 3 restarts within 5 cycles then timeout

check process munin-node with pidfile /var/run/munin/munin-node.pid

start program = "/etc/init.d/munin-node start"

stop program = "/etc/init.d/munin-node stop"

if failed host 127.0.0.1 port 4949 then restart

if 3 restarts within 5 cycles then timeout

check process openvpn with pidfile /var/run/openvpn/openvpn.pid

start program = "/etc/init.d/openvpn start"

stop program = "/etc/init.d/openvpn stop"

if failed host 192.168.1.60 port 1194 then restart

if 3 restarts within 5 cycles then timeout

check process keepalived with pidfile /var/run/keepalived.pid

start program = "/etc/init.d/keepalived start" #with timeout 60 seconds

stop program = "/etc/init.d/keepalived stop"

check process sshd with pidfile /var/run/sshd.pid

start program = "/etc/init.d/sshd start"

stop program = "/etc/init.d/sshd stop"

if failed port 22 protocol ssh then restart

if 5 restarts within 5 cycles then timeout

check process dovecot with pidfile /var/run/dovecot/master.pid

start program = "/etc/init.d/dovecot start"

stop program = "/etc/init.d/dovecot stop"

if 3 restarts within 3 cycles then timeout

check process ntpd with pidfile /var/run/ntpd.pid

start program = "/etc/init.d/ntpd start"

stop program = "/etc/init.d/ntpd stop"

if failed host 127.0.0.1 port 123 type udp then alert

if 5 restarts within 5 cycles then timeout

check process crond with pidfile /var/run/crond.pid

start program = "/etc/init.d/crond start"

stop program = "/etc/init.d/crond stop"

check process postfix with pidfile /var/spool/postfix/pid/master.pid

start program = "/etc/init.d/postfix start"

stop program = "/etc/init.d/postfix stop"

if failed port 25 protocol smtp then restart

if 5 restarts within 5 cycles then timeout

check process mmm_agentd with pidfile /var/run/mysql-mmm/mmm_agentd.pid

start program = "/etc/init.d/mysql-mmm-agent start"

stop program = "/etc/init.d/mysql-mmm-agent stop"

if 5 restarts within 5 cycles then timeout

check process mysql with pidfile /var/lib/mysql/lb02.kamaok.org.ua.pid

start program = "/etc/init.d/mysql start"

stop program = "/etc/init.d/mysql stop"

if 5 restarts within 5 cycles then timeout

#Подключения оповещения при недоступности определенных портов на различных удаленных серверах

check host lb01.kamaok.org.ua with address 192.168.1.61

if failed icmp type echo count 5 with timeout 10 seconds then alert

if failed port 22 protocol ssh then alert

if failed port 4949 then alert

if failed port 80 then alert

if failed port 11211 then alert

if failed port 25 then alert

if failed port 143 then alert

if failed port 11211 then alert

check host app01.kamaok.org.ua with address 192.168.1.63

if failed icmp type echo count 5 with timeout 10 seconds then alert

if failed port 22 protocol ssh then alert

if failed port 4949 then alert

if failed port 9989 then alert

if failed port 80 protocol HTTP then alert

if failed port 11211 then alert

if failed port 25 then alert

if failed port 8080 then alert

check host app02.kamaok.org.ua with address 192.168.1.64

if failed icmp type echo count 5 with timeout 10 seconds then alert

if failed port 22 protocol ssh then alert

if failed port 4949 then alert

if failed port 9989 then alert

if failed port 80 protocol HTTP then alert

if failed port 11211 then alert

if failed port 25 then alert

if failed port 8080 then alert

alert root@localhost

2.Проверка синтаксиса, запуск Monit-сервера, добавление в автозагрузку, просмотр логов Monit.

# monit –t

1	# monit –t

# /etc/init.d/monit start

1	# /etc/init.d/monit start

# chkconfig --level 2345 monit on

1	# chkconfig --level 2345 monit on

# tail -f /var/log/monit.log

1	# tail -f /var/log/monit.log

3.Доступ к Web-интерфейсу Monit

http://<IP-address Monit-server>:2812

1	http://<IP-address Monit-server>:2812

с логином и паролем согласно настройкам в /etc/monit.conf (monit password) Источник: http://mmonit.com/wiki/Monit/ConfigurationExamples#ssh http://habrahabr.ru/company/centosadmin/blog/266971/

Опубликовано в рубрике Centos, Monitoring

Метки: monit

Комментарии отключены

Установка и настройка Munin на Centos

Февраль 2nd, 2014

Evgeniy Kamenev

1.Установка и настройка Munin

# yum install munin munin-node

1	# yum install munin munin-node

# cp /etc/munin/munin.conf /etc/munin/munin.conf~

1	# cp /etc/munin/munin.conf /etc/munin/munin.conf~

# nano /etc/httpd/conf.d/munin.conf

1	# nano /etc/httpd/conf.d/munin.conf

Alias /munin /var/www/html/munin

# Если нужно ограничить доступ к статистике по паролю
<Directory /var/www/html/munin>
AuthUserFile /etc/munin/munin-htpasswd
AuthName "Munin"
AuthType Basic
Require valid-user
</Directory>

Alias /munin /var/www/html/munin

# Если нужно ограничить доступ к статистике по паролю

AuthUserFile /etc/munin/munin-htpasswd

AuthName "Munin"

AuthType Basic

Require valid-user

</Directory>

# htpasswd /etc/munin/munin-htpasswd munin

1	# htpasswd /etc/munin/munin-htpasswd munin

Конфигурационный файл Munin-сервера /etc/munin/munin.conf

# cat /etc/munin/munin.conf | grep -v '#' | grep -v '^$'

1	# cat /etc/munin/munin.conf \| grep -v '#' \| grep -v '^$'

dbdir   /var/lib/munin
htmldir /var/www/html/munin
logdir /var/log/munin
rundir  /var/run/munin
tmpldir /etc/munin/templates
staticdir /etc/munin/static
includedir /etc/munin/conf.d
graph_period second
graph_strategy cron
cgiurl_graph /munin-cgi/munin-cgi-graph
html_strategy cron

#определяем клиентов, с которых снимаем статистику
# 127.0.0.1 – Munin-сервер также снимает статистику с себя.

[lb01.kamaok.org.ua]
address 127.0.0.1
use_node_name yes

[lb02.kamaok.org.ua]
address 192.168.1.62
use_node_name yes

[app01.kamaok.org.ua]
address 192.168.1.63
use_node_name yes

[app02.kamaok.org.ua]
address 192.168.1.64
use_node_name yes

dbdir /var/lib/munin

htmldir /var/www/html/munin

logdir /var/log/munin

rundir /var/run/munin

tmpldir /etc/munin/templates

staticdir /etc/munin/static

includedir /etc/munin/conf.d

graph_period second

graph_strategy cron

cgiurl_graph /munin-cgi/munin-cgi-graph

html_strategy cron

#определяем клиентов, с которых снимаем статистику

# 127.0.0.1 – Munin-сервер также снимает статистику с себя.

[lb01.kamaok.org.ua]

address 127.0.0.1

use_node_name yes

[lb02.kamaok.org.ua]

address 192.168.1.62

use_node_name yes

[app01.kamaok.org.ua]

address 192.168.1.63

use_node_name yes

[app02.kamaok.org.ua]

address 192.168.1.64

use_node_name yes

Логи для munin-сервера смотрим в

# tail -f /var/log/munin/munin-update.log

1	# tail -f /var/log/munin/munin-update.log

Проверяем наличие задания в крон,которое автоматически добавляется при установке munin-сервера

# cat /etc/cron.d/munin

1	# cat /etc/cron.d/munin

MAILTO=root
*/5 * * * *     munin test -x /usr/bin/munin-cron && /usr/bin/munin-cron

1 2	MAILTO=root /5 * * * munin test -x /usr/bin/munin-cron && /usr/bin/munin-cron

Проверка работы munin-сервера

# su -m munin  -c /usr/bin/munin-cron

1	# su -m munin -c /usr/bin/munin-cron

2.На клиентах, с которых будет сниматься статистика

# yum install munin-node

1	# yum install munin-node

# cat /etc/munin/munin-node.conf | grep -v '#' | grep -v '^$'

1	# cat /etc/munin/munin-node.conf \| grep -v '#' \| grep -v '^$'

log_level 4
log_file /var/log/munin-node/munin-node.log
pid_file /var/run/munin/munin-node.pid
background 1
setsid 1
user root
group root
ignore_file DEADJOE$
ignore_file \.bak$
ignore_file %$
ignore_file \.dpkg-(tmp|new|old|dist)$
ignore_file \.rpm(save|new)$
ignore_file \.pod$
allow ^127\.0\.0\.1$
allow ^::1$
allow ^192\.168\.1\.61$ # Ip-adress Munin-мастера, на котором смотрим всю статистику
host *
port 4949

log_level 4

log_file /var/log/munin-node/munin-node.log

pid_file /var/run/munin/munin-node.pid

background 1

setsid 1

user root

group root

ignore_file DEADJOE$

ignore_file \.bak$

ignore_file %$

ignore_file \.dpkg-(tmp|new|old|dist)$

ignore_file \.rpm(save|new)$

ignore_file \.pod$

allow ^127\.0\.0\.1$

allow ^::1$

allow ^192\.168\.1\.61$ # Ip-adress Munin-мастера, на котором смотрим всю статистику

host *

port 4949

# /etc/init.d/munin-node start

1	# /etc/init.d/munin-node start

# chkconfig --level 2345 munin-node on

1	# chkconfig --level 2345 munin-node on

[…]

Опубликовано в рубрике Centos, Monitoring

Метки: munin

Комментарии отключены

Архивы рубрики ‘Monitoring’

Настройка мониторинга MySQL в Cacti средствами Percona Monitoring Plugins

Настройка мониторинга Linux-хоста в Cacti средствами Percona Monitoring Plugins

Настройка мониторинга Nginx, Memcached, Redis в Cacti средствами Percona Monitoring Plugins

Настройка мониторинга дисковой подсистемы в Cacti

Настройка мониторинга PHP-FPM в Cacti

Настройка мониторинга Nginx в Cacti

Тестирование скорости чтения-записи жесткого диска в Linux

Установка и настройка smartmontools для мониторинга состояния жесткого диска

Установка и настройка Monit на Centos

Установка и настройка Munin на Centos

Страницы

Свежие записи

Архивы

Рубрики

Админ-панель