Ad Widget

**Daniel Weber** · 19-11-2014, 17:55

No Route to Host, maybe wrong IP

Hello

I've seen your post, as i don't know your Environment completely, i can only tell what the Message tells me.

No Route to host means for me, that the Proxy or the Server, that is trying to connect to your x.x.x.x IP-Adress has no route to it.

Have you checked the route list? (Command in Linux: ip route)

Maybe the Server / Proxy misses a Default Gatway or your Network does not know where to send the packets to.

Have you tried ping the IP-Adress on the Zabbix-Server / Proxy?
Maybe is the IP-Adress wrong?

**kpetruk** · 20-11-2014, 07:48

As I mentioned in my original post: "I could telnet to that port".
I could also connect to other services on that server.

**mucknet** · 04-01-2017, 03:52

Originally posted by kpetruk

Can't connect one server through JMX. Connection to several other servers are OK.
Firewall is configured and port is correct. I could telnet to that port, but zabbix-java-agent can't connect. I could also connect to that server through RMI (standard ports).

Differences between servers:
* on problematic server installed java (build 1.6.0_17-b04). On others 1.8
* problematic server is located on different provider (Rackspace).

Did you ever find an answer to this? I'm having the same issue. zabbix_java.log is reporting "No Route To Host", however, I can telnet to my JMX port from my java gateway server just fine.

I have some additional strange behavior, which is that the IP zabbix_java.log is reporting is NOT the ip I've configured as my JMX interface in my host configuration. Instead the IP it is reporting is another interface on the server I'm trying to monitor. An interface I DO NOT use for connecting to from zabbix.

FWIW, I'm using 3.2.3 for server, agent, and java gateway.

**Pada** · 05-01-2017, 02:30

What does your server report when you run:

Code:

hostname -i

, because if it returns 127.0.0.1 and not the JMX IP you may have problems accessing it.
Also, can you access it with something like jConsole or jVisualVM? The above would cause those apps to fail too.

I wrote the following script for our environments where the `hostname -i` resulted in localhost:

Code:

ipeth0=`ip addr show eth0 | grep "inet\b" | awk '{print $2}' | cut -d/ -f1`
if [[ "127.0.0.1" == "`hostname -i`" ]]; then
  if [[ "`hostname`" == "`hostname -s`" ]]; then
    sudo sed -i "s/ `hostname`\$//" /etc/hosts
  else
    sudo sed -i "s/ `hostname`//" /etc/hosts
  fi
  sudo echo "$ipeth0 `hostname`" >> /etc/hosts
  
  if [[ "$ipeth0" != "`hostname -i`" ]]; then
    echo "Error: Failed to change 'hostname -i' to '$ipeth0'. Please correct /etc/hosts file manually."
  else
    sudo service our-java-webapp-service restart
  fi
elif [[ "$ipeth0" != "`hostname -i`" ]]; then
  echo "Error: Please correct /etc/hosts file manually."
else
  echo "Already configured to '$ipeth0'"
fi

I've also taken the zabbix_get_jmx script and modified it to work with Zabbix 3.2.3 (although I could't get zabbix_get to work) - see the attached zabbix_get_jmx.txt shell script.

And then I use it by running it on my proxy server that has the Java gateway running on port 10052 with like:

Code:

./zabbix_get_jmx localhost 10052 host.example.com 12345 'jmx["Catalina:type=GlobalRequestProcessor,name=\"http-nio-8443\"",bytesReceived]'

Perhaps also consult the Zabbix JMX wiki page: https://www.zabbix.org/wiki/ConfigureJMX

Attached Files

zabbix_get_jmx.txt (1.2 KB, 205 views)

**mucknet** · 05-01-2017, 05:45

Thanks Pada, I didn't end up using your solution exactly, but you pointed me in the right direction, and I am now successful. Instead, I found that I could use -Djava.rmi.server.hostname=app-server.sub.domain.com to specify the interface/IP I wanted it to use.

Here are my notes that I took for getting this all setup, in case they're useful to someone else:

* Java gateway sits on same server as zabbix_server - It doesn't have to, but in our case it does.

Zabbix Server Config
* Configure /opt/zabbix/etc/zabbix_server.conf
* * JavaGateway=127.0.0.1
* * JavaGateWayPort=10052
* * StartJavaPollers=4
* Configure /opt/zabbix/sbin/zabbix_java/settings.sh
* * LISTEN_PORT=10052
* Configure zabbix_java to auto start. I did that by adding it to existing zabbix_server startup script:

Code:

ZABBIX_JAVA_DIR="/opt/zabbix/sbin/zabbix_java"
 
if [ ! -x ${ZABBIX_BIN} ] ; then
        echo -n "${ZABBIX_BIN} not installed! "
        # Tell the user this has skipped
        exit 5
fi
 
start() {
        echo -n $"Starting $prog: "
        daemon $ZABBIX_BIN
        RETVAL=$?
        [ $RETVAL -eq 0 ] && touch /var/lock/subsys/zabbix_server
        echo
    runuser -l zabbix -c "$ZABBIX_JAVA_DIR/startup.sh"
}
 
stop() {
        echo -n $"Stopping $prog: "
        killproc $ZABBIX_BIN
        RETVAL=$?
        [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/zabbix_server
        echo
    runuser -l zabbix -c "$ZABBIX_JAVA_DIR/shutdown.sh"
}

Host Config (JVM and Firewall):
* If you have Multiple Interfaces on the host, you need to configure the "-Djava.rmi.server.hostname" option, otherwise you get a convoluted and useless "No Route To Host" error.
* The hostname you configure, does NOT have to be in /etc/hosts - at least our JDK 6 will use DNS to get the results. Having it in /etc/hosts isn't a bad idea though, if possible.
* Firewall Changes:
* * For JDK6, you have to allow all ports from your java gateway server (same as zabbix server in this case):
* * -A INPUT -m conntrack -i eth2 --ctstate NEW -m tcp -p tcp -s zabbixserver.sub.domain.com -j ACCEPT -m comment --comment "zabbixserver.sub.domain.com"
* * For JDK7u4, you can specify an rmi port, and just allow access to that port from your Java Gateway Server
* * -A INPUT -m conntrack -i eth2 --ctstate NEW -m tcp -p tcp --match multiport -s zabbixserver.sub.domain.com --dports 22,80,443,10050,10099,10199 -j ACCEPT -m comment --comment "zabbixserver.sub.domain.com"

* resin.conf changes - JDK 7 supports specifying RMI port - JDK6 Does not:
* This was for a resin server, but the same options should work for any java web server - tomcat, weblogic, etc
* * Also note that these settings should be considered insecure, and depending on your environment you should lock down JMX access better than this

Code:

<jvm-arg>-Dcom.sun.management.jmxremote.port=10099</jvm-arg>
      <jvm-arg>-Dcom.sun.management.jmxremote.authenticate=false</jvm-arg>
      <jvm-arg>-Dcom.sun.management.jmxremote.ssl=false</jvm-arg>
      <jvm-arg>-Djava.rmi.server.hostname=app-server.sub.domain.com</jvm-arg>
     <jvm-arg>-Dcom.sun.management.jmxremote.rmi.port=10199</jvm-arg>

Zabbix Host UI Config
* JMX Interface: Can use IP or Hostname (app-server.sub.domain.com). Hostname needs to match the hostname used in the JVM config (or more accurately they both need to resolve to the same IP address)
* Apply JMX Template to Host

Search Keywords: zabbix_java.log zabbix_java JMX resin tomcat Java Gateway jconsole No Route To Host Exception Creating connection NoRouteToHostException Host Unreachable

**vishnu.dinoct** · 08-05-2017, 18:08

com.zabbix.gateway.SocketProcessor - error processing request

Can please help me with this error??? I am dead already

WARN com.zabbix.gateway.SocketProcessor - error processing request
com.zabbix.gateway.ZabbixException: bad protocol header: 7B 22 72 65 71
at com.zabbix.gateway.BinaryProtocolSpeaker.getReques t(BinaryProtocolSpeaker.java:59) ~[zabbix-java-gateway-2.2.0.jar:na]
at com.zabbix.gateway.SocketProcessor.run(SocketProce ssor.java:51) ~[zabbix-java-gateway-2.2.0.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142) [na:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617) [na:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]

**Raghav** · 14-05-2019, 07:40

I Had the same problem. I solved it by using a ssh tunnel from the multiple hosts to the zabbix central server. Setting RMI port was not working for me and by default it takes a random port due to which zabbix_java_gateway was unable to get to the rmi port.

Ad Widget

zabbix-java-gateway java.net.NoRouteToHostException: No route to host

zabbix-java-gateway java.net.NoRouteToHostException: No route to host

Comment

Comment

Comment

Comment

Comment

Comment

Comment