Ad Widget

Collapse

[113] No route to host

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Incher
    Member
    • Sep 2012
    • 38

    #1

    [113] No route to host

    Здравствуйте, собственно, суть вопроса:
    имеется физический хост с Esxi 5.0, на нем крутится несколько виртуалок, часть из них уже прикручена к заббиксу и активно мониторится, но с одной возникла проблема: при попытке подключиться к системе мониторинга в веб-морде получаю ошибку -
    Get value from agent failed: cannot connect to [[192.168.199.212]:10050]: [113] No route to host

    Заббикс-сервер имеет локальный адрес 192.168.199.202 (но физически находится на другой железке) и успешно пингуется с этой виртуалки, так же как и виртуалка свободно пингуется с сервера.
    В логах агента были ошибки вида:
    Code:
    7887:20130425:170352.508 No active checks on server: host [VM_SITE_AM] not found
    но после очередного рестарта агента в логи больше ничего не сыпется.
    В логах Заббикс-сервера сначала были такие сообщения:
    Code:
    cannot send list of active checks to [192.168.199.212]: host [VM_SITE_AM] not found
    Zabbix agent item [system.cpu.intr] on host [VM_SITE_AM] failed: first network error, wait for 20 seconds
      1432:20130425:170741.259 Zabbix agent item [system.cpu.intr] on host [VM_SITE_AM] failed: another network error, wait for 20 seconds
      1432:20130425:170814.330 Zabbix agent item [system.localtime] on host [VM_SITE_AM] failed: another network error, wait for 20 seconds
      1432:20130425:170834.357 Zabbix agent item [system.cpu.load[percpu,avg5]] on host [VM_SITE_AM] failed: another network error, wait for 20 seconds
      1432:20130425:170854.381 Zabbix agent item [system.swap.size[,pfree]] on host [VM_SITE_AM] failed: another network error, wait for 20 seconds
      1432:20130425:170914.400 Zabbix agent item [vm.memory.size[available]] on host [VM_SITE_AM] failed: another network error, wait for 20 seconds
      1432:20130425:170934.443 temporarily disabling Zabbix agent checks on host [VM_SITE_AM]: host unavailable
    но после рестарта агента в логе сервера сообщения с этого хоста тоже прекратились.

    Привожу конфиг агента:
    Code:
    # This is a config file for the Zabbix agent daemon (Unix)
    # To get more information about Zabbix, visit http://www.zabbix.com
    
    ############ GENERAL PARAMETERS #################
    
    ### Option: PidFile
    #	Name of PID file.
    #
    # Mandatory: no
    # Default:
    # PidFile=/tmp/zabbix_agentd.pid
    
    ### Option: LogFile
    #	Name of log file.
    #	If not set, syslog is used.
    #
    # Mandatory: no
    # Default:
    # LogFile=
    
    LogFile=/tmp/zabbix_agentd.log
    
    ### Option: LogFileSize
    #	Maximum size of log file in MB.
    #	0 - disable automatic log rotation.
    #
    # Mandatory: no
    # Range: 0-1024
    # Default:
    # LogFileSize=1
    
    ### Option: DebugLevel
    #	Specifies debug level
    #	0 - no debug
    #	1 - critical information
    #	2 - error information
    #	3 - warnings
    #	4 - for debugging (produces lots of information)
    #
    # Mandatory: no
    # Range: 0-4
    # Default:
    # DebugLevel=3
    
    ### Option: SourceIP
    #	Source IP address for outgoing connections.
    #
    # Mandatory: no
    # Default:
     SourceIP=192.168.199.212
    
    ### Option: EnableRemoteCommands
    #	Whether remote commands from Zabbix server are allowed.
    #	0 - not allowed
    #	1 - allowed
    #
    # Mandatory: no
    # Default:
    # EnableRemoteCommands=0
    
    ### Option: LogRemoteCommands
    #	Enable logging of executed shell commands as warnings.
    #	0 - disabled
    #	1 - enabled
    #
    # Mandatory: no
    # Default:
    # LogRemoteCommands=0
    
    ##### Passive checks related
    
    ### Option: Server
    #	List of comma delimited IP addresses (or hostnames) of Zabbix servers.
    #	Incoming connections will be accepted only from the hosts listed here.
    #	No spaces allowed.
    #	If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.
    #
    # Mandatory: no
    # Default:
    # Server=
    
    Server=192.168.199.202
    
    ### Option: ListenPort
    #	Agent will listen on this port for connections from the server.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    # ListenPort=10050
    
    ### Option: ListenIP
    #	List of comma delimited IP addresses that the agent should listen on.
    #	First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
    #
    # Mandatory: no
    # Default:
    # ListenIP=0.0.0.0
    
    ### Option: StartAgents
    #	Number of pre-forked instances of zabbix_agentd that process passive checks.
    #	If set to 0, disables passive checks and the agent will not listen on any TCP port.
    #
    # Mandatory: no
    # Range: 0-100
    # Default:
    # StartAgents=3
    
    ##### Active checks related
    
    ### Option: ServerActive
    #	List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks.
    #	If port is not specified, default port is used.
    #	IPv6 addresses must be enclosed in square brackets if port for that host is specified.
    #	If port is not specified, square brackets for IPv6 addresses are optional.
    #	If this parameter is not specified, active checks are disabled.
    #	Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
    #
    # Mandatory: no
    # Default:
    # ServerActive=
    
    ServerActive=192.168.199.202
    
    ### Option: Hostname
    #	Unique, case sensitive hostname.
    #	Required for active checks and must match hostname as configured on the server.
    #	Value is acquired from HostnameItem if undefined.
    #
    # Mandatory: no
    # Default:
    # Hostname=
    
    Hostname=VM_SITE_AM
    
    ### Option: HostnameItem
    #	Item used for generating Hostname if it is undefined.
    #	Ignored if Hostname is defined.
    #
    # Mandatory: no
    # Default:
    # HostnameItem=system.hostname
    
    ### Option: RefreshActiveChecks
    #	How often list of active checks is refreshed, in seconds.
    #
    # Mandatory: no
    # Range: 60-3600
    # Default:
    # RefreshActiveChecks=120
    
    ### Option: BufferSend
    #	Do not keep data longer than N seconds in buffer.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # BufferSend=5
    
    ### Option: BufferSize
    #	Maximum number of values in a memory buffer. The agent will send
    #	all collected data to Zabbix Server or Proxy if the buffer is full.
    #
    # Mandatory: no
    # Range: 2-65535
    # Default:
    # BufferSize=100
    
    ### Option: MaxLinesPerSecond
    #	Maximum number of new lines the agent will send per second to Zabbix Server
    #	or Proxy processing 'log' and 'logrt' active checks.
    #	The provided value will be overridden by the parameter 'maxlines',
    #	provided in 'log' or 'logrt' item keys.
    #
    # Mandatory: no
    # Range: 1-1000
    # Default:
    # MaxLinesPerSecond=100
    
    ### Option: AllowRoot
    #	Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent
    #       will try to switch to user 'zabbix' instead. Has no effect if started under a regular user.
    #	0 - do not allow
    #	1 - allow
    #
    # Mandatory: no
    # Default:
    # AllowRoot=0
    
    ############ ADVANCED PARAMETERS #################
    
    ### Option: Alias
    #	Sets an alias for parameter. It can be useful to substitute long and complex parameter name with a smaller and simpler one.
    #
    # Mandatory: no
    # Range:
    # Default:
    
    ### Option: Timeout
    #	Spend no more than Timeout seconds on processing
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
     Timeout=30
    
    ### Option: Include
    #	You may include individual files or all files in a directory in the configuration file.
    #	Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
    #
    # Mandatory: no
    # Default:
    # Include=
    
    # Include=/usr/local/etc/zabbix_agentd.userparams.conf
    # Include=/usr/local/etc/zabbix_agentd.conf.d/
    
    ####### USER-DEFINED MONITORED PARAMETERS #######
    
    ### Option: UnsafeUserParameters
    #	Allow all characters to be passed in arguments to user-defined parameters.
    #	0 - do not allow
    #	1 - allow
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # UnsafeUserParameters=0
    
    ### Option: UserParameter
    #	User-defined parameter to monitor. There can be several user-defined parameters.
    #	Format: UserParameter=<key>,<shell command>
    #	See 'zabbix_agentd' directory for examples.
    #
    # Mandatory: no
    # Default:
    # UserParameter=
    Помогите, пожалуйста, разобраться.
  • dima_dm
    Senior Member
    • Dec 2009
    • 2697

    #2
    Хост это Linux? Настройки SELinux проверяли?
    /usr/sbin/setenforce -h
    /usr/sbin/setenforce: SELinux is disabled
    Другой способ проверки
    netstat -Z
    SELinux is not enabled on this machine.

    Comment

    • Incher
      Member
      • Sep 2012
      • 38

      #3
      Да, все машины под CentOS, netstat -Z возвращает
      SELinux is not enabled on this machine.
      И еще, когда подключаюсь по ssh к виртуалке, то попадаю не в shell centos'а, а в Bitrix Virtual Appliance-консоль (чтоб вернуться в shell просит нажать Ctrl+C)... В мое ведение этот сервер попал недавно, да и про Bitrix я ничего еще не знаю, вероятно причина как-то связана с этим, но я не знаю, как это можно обойти.

      Comment

      • dima_dm
        Senior Member
        • Dec 2009
        • 2697

        #4
        Настройки firewall iptables на хосте посмотрите.

        Comment

        • neogan
          Senior Member
          Zabbix Certified Trainer
          Zabbix Certified SpecialistZabbix Certified Professional
          • Sep 2011
          • 118

          #5
          + проверьте порт через telnet

          Comment

          • Incher
            Member
            • Sep 2012
            • 38

            #6
            Originally posted by dima_dm
            Настройки firewall iptables на хосте посмотрите.
            iptables на хосте не включен, telnet не запущен

            Comment

            • dima_dm
              Senior Member
              • Dec 2009
              • 2697

              #7
              Originally posted by Incher
              telnet не запущен
              Речь про запуск с Zabbix_server команды
              telnet 192.168.199.212 10050

              Comment

              • Incher
                Member
                • Sep 2012
                • 38

                #8
                Originally posted by dima_dm
                Речь про запуск с Zabbix_server команды
                telnet 192.168.199.212 10050
                Запуск команды возвращает
                Code:
                Trying 192.168.199.212...
                telnet: connect to address 192.168.199.212: No route to host

                Comment

                • Zerocool56
                  Member
                  • Mar 2013
                  • 68

                  #9
                  Межсетевые экраны есть какие-либо ещё между узлами?

                  Comment

                  • dima_dm
                    Senior Member
                    • Dec 2009
                    • 2697

                    #10
                    Originally posted by Incher
                    Запуск команды возвращает
                    Code:
                    Trying 192.168.199.212...
                    telnet: connect to address 192.168.199.212: No route to host
                    Ищите проблемы на машине с Zabbix_server. Например с Firewall.

                    Comment

                    • Incher
                      Member
                      • Sep 2012
                      • 38

                      #11
                      Originally posted by dima_dm
                      Ищите проблемы на машине с Zabbix_server. Например с Firewall.
                      Хм... firewall'а на zabbix_server'е нет, и с него успешно пингуется 192.168.199.212

                      Comment

                      • dima_dm
                        Senior Member
                        • Dec 2009
                        • 2697

                        #12
                        Originally posted by Incher
                        Хм... firewall'а на zabbix_server'е нет, и с него успешно пингуется 192.168.199.212
                        Скорее всего No route to host это информация из ICMP пакета, осталось сняв дампы трафика во время telnet 192.168.199.212 10050, найти хост в сети, который этот пакет формирует, там и искать проблему.

                        Comment

                        • Incher
                          Member
                          • Sep 2012
                          • 38

                          #13
                          Originally posted by dima_dm
                          Скорее всего no route to host это информация из icmp пакета, осталось сняв дампы трафика во время telnet 192.168.199.212 10050, найти хост в сети, который этот пакет формирует, там и искать проблему.
                          Спасибо, попробую.

                          Comment

                          Working...