From: Dmitriy Shcherbakov <dimka_list@vzljot.ru> To: community@altlinux.ru Subject: [Comm] nagios Date: Thu, 28 Apr 2005 10:09:10 +0400 Message-ID: <42707E06.8030506@vzljot.ru> (raw) Добрый день! Все никак не могу взять в толк где я ошибся... Настроил nagius на простую check_ping проверку серверов и свитчей. В результате такая картина: свитчи и сервера, у которых один сетевой интерфейс, нормально светятся как UP, а маршрутизаторы все в дауне. Причем если запустить руками: # /usr/lib/nagios/plugins/check_ping -H 192.168.0.250 -w 100,20% -c 500,60% -p 5 PING OK - Packet loss = 0%, RTA = 0.17 ms то все, как видите, нормально. # rpm -qa|grep nagios nagios-www-common-1.2-alt1 nagios-plugins-perl-1.3.1-alt5.1 nagios-plugins-1.3.1-alt5.1.1 nagios-plugins-network-1.3.1-alt5.1.1 nagios-default-1.2-alt1 nagios-default-www-1.2-alt1 nagios-common-1.2-alt1 nagios-plugins-extra-1.3.1-alt5.1.1 для упомянутого сервера: ***host.cfg: ... define host{ use generic-host ; Name of host template to use host_name master alias kserver address 192.169.0.250 check_command check-host-alive max_check_attempts 10 notification_interval 300 notification_period 24x7 notification_options d,u,r parents switch_ATC } ... ***services.cfg ... define service{ use generic-service ; Name of service template to use host_name master service_description PING is_volatile 0 check_period 24x7 max_check_attempts 3 normal_check_interval 5 retry_check_interval 1 contact_groups linux-admins notification_interval 240 notification_period 24x7 notification_options c,r check_command check_ping!100.0,20%!500.0,60% } ... ***checkcommands.cfg ... define command{ command_name check_ping command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5 } ... Где я прокололся? Заранее спасибо, Дмитрий
next reply other threads:[~2005-04-28 6:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-28 6:09 Dmitriy Shcherbakov [this message] 2005-04-28 6:10 ` Alexey Bayguzov 2005-04-28 6:55 ` Dmitriy Shcherbakov 2005-04-28 7:28 ` Alexey Bayguzov 2005-04-28 9:19 ` Dmitriy Shcherbakov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=42707E06.8030506@vzljot.ru \ --to=dimka_list@vzljot.ru \ --cc=community@altlinux.ru \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git