Ad Widget

Collapse

Zabbix 2.2 JMX tomcat

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • makemefeel
    Junior Member
    • May 2013
    • 6

    #1

    Zabbix 2.2 JMX tomcat

    Сервер запущен со след. параметрами:
    Code:
    JavaGateway=127.0.0.1
    JavaGatewayPort=10052
    StartJavaPollers=7
    Java gateway:
    Code:
    LISTEN_IP=0.0.0.0
    LISTEN_PORT=10052
    START_POLLERS=7
    PID_FILE="/var/run/zabbix/zabbix_java_gateway.pid"
    netstat -nltp:
    Code:
    tcp        0      0 0.0.0.0:10051           0.0.0.0:*               LISTEN      30587/zabbix_server
    tcp6       0      0 :::10052                :::*                    LISTEN      31687/java
    На удаленной машине, которую хочу мониторить, томкат со след. параметрами:
    Code:
    ps aux | grep tomcat      
    tomcat6   1848 16.1 11.5 6447716 908968 ?      SNl  04:15   5:24 /usr/lib/jvm/java-6-sun/bin/java -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties -Djava.awt.headless=true -Xms4096m -Xmx4096m -XX:PermSize=1536m -XX:MaxPermSize=1536m -XX:ReservedCodeCacheSize=64m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:SurvivorRatio=2 -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=10052 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=107.22.*.* -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -classpath /usr/share/tomcat6/bin/bootstrap.jar -Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tmp org.apache.catalina.startup.Bootstrap start
    Телнетом все и везде пускает, но заббикс выдает следующий лог:
    Code:
    2013-11-18 04:10:47.465 [Thread-0] INFO  com.zabbix.gateway.JavaGateway - Zabbix Java Gateway 2.2.0 (revision 40163) has stopped
    2013-11-18 04:10:48.354 [main] INFO  com.zabbix.gateway.JavaGateway - Zabbix Java Gateway 2.2.0 (revision 40163) has started
    2013-11-18 04:10:48.367 [main] DEBUG c.z.gateway.ConfigurationManager - starting to parse configuration parameters
    2013-11-18 04:10:48.367 [main] DEBUG c.z.gateway.ConfigurationManager - found pidFile configuration parameter with value '/var/run/zabbix/zabbix_java_gateway.pid'
    2013-11-18 04:10:48.367 [main] DEBUG c.z.gateway.ConfigurationManager - received pidFile configuration parameter, daemonizing
    2013-11-18 04:10:48.368 [main] DEBUG c.z.gateway.ConfigurationManager - found listenIP configuration parameter with value '0.0.0.0'
    2013-11-18 04:10:48.369 [main] DEBUG c.z.gateway.ConfigurationManager - found listenPort configuration parameter with value '10052'
    2013-11-18 04:10:48.369 [main] DEBUG c.z.gateway.ConfigurationManager - found startPollers configuration parameter with value '7'
    2013-11-18 04:10:48.369 [main] DEBUG c.z.gateway.ConfigurationManager - finished parsing configuration parameters
    2013-11-18 04:10:48.373 [main] INFO  com.zabbix.gateway.JavaGateway - listening on /0.0.0.0:10052
    2013-11-18 04:10:48.377 [main] DEBUG com.zabbix.gateway.JavaGateway - created a thread pool of 7 pollers
    2013-11-18 04:11:14.896 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
    2013-11-18 04:11:14.905 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
    2013-11-18 04:11:14.906 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
    2013-11-18 04:11:14.906 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 160 bytes of request data
    2013-11-18 04:11:14.907 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
            "request":"java gateway jmx",
            "conn":"107.22.*.*",
            "port":10052,
            "keys":["jmx[\"Catalina:type=GlobalRequestProcessor,name=http-8443\",bytesReceived]"]}
    2013-11-18 04:11:14.920 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - dispatched request to class com.zabbix.gateway.JMXItemChecker
    2013-11-18 04:11:14.920 [pool-1-thread-1] DEBUG com.zabbix.gateway.JMXItemChecker - connecting to JMX agent at service:jmx:rmi:///jndi/rmi://107.22.*.*:10052/jmxrmi
    2013-11-18 04:11:15.193 [pool-1-thread-1] WARN  com.zabbix.gateway.SocketProcessor - error processing request
    com.zabbix.gateway.ZabbixException: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 
            java.net.ConnectException: Connection refused
            at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:100) ~[zabbix-java-gateway-2.2.0.jar:na]
            at com.zabbix.gateway.SocketProcessor.run(SocketProcessor.java:63) ~[zabbix-java-gateway-2.2.0.jar:na]
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_45]
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_45]
            at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
    Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 
            java.net.ConnectException: Connection refused
            at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) ~[na:1.7.0_45]
            at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) ~[na:1.7.0_45]
            at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) ~[na:1.7.0_45]
            at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129) ~[na:1.7.0_45]
            at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) ~[na:1.7.0_45]
            at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2392) ~[na:1.7.0_45]
            at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308) ~[na:1.7.0_45]
            at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268) ~[na:1.7.0_45]
            at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:92) ~[zabbix-java-gateway-2.2.0.jar:na]
            ... 4 common frames omitted
    Caused by: java.net.ConnectException: Connection refused
            at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.7.0_45]
            at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) ~[na:1.7.0_45]
            at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) ~[na:1.7.0_45]
            at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) ~[na:1.7.0_45]
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.7.0_45]
            at java.net.Socket.connect(Socket.java:579) ~[na:1.7.0_45]
            at java.net.Socket.connect(Socket.java:528) ~[na:1.7.0_45]
            at java.net.Socket.<init>(Socket.java:425) ~[na:1.7.0_45]
            at java.net.Socket.<init>(Socket.java:208) ~[na:1.7.0_45]
            at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) ~[na:1.7.0_45]
            at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:147) ~[na:1.7.0_45]
            at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) ~[na:1.7.0_45]
            ... 12 common frames omitted
    2013-11-18 04:11:15.196 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"failed","error":"\"java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: \\n\\tjava.net.ConnectException: Connection refused\""}
    2013-11-18 04:11:15.197 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection
    2013-11-18 04:12:17.745 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
    2013-11-18 04:12:17.745 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
    2013-11-18 04:12:17.745 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
    2013-11-18 04:12:17.746 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 153 bytes of request data
    2013-11-18 04:12:17.746 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
            "request":"java gateway jmx",
            "conn":"107.22.*.*",
            "port":10052,
            "keys":["jmx[\"Catalina:type=ThreadPool,name=http-8080\",currentThreadCount]"]}
    В заббиксе JMX горит красным.
    в общем вопрос, почему рефьюзит? сталкивался кто-нибудь, и в какую сторону копать?
  • csf
    Senior Member
    • Nov 2007
    • 154

    #2
    Originally posted by makemefeel
    В заббиксе JMX горит красным.
    в общем вопрос, почему рефьюзит? сталкивался кто-нибудь, и в какую сторону копать?
    У меня тоже была проблема при запуске JMX-Gateway (правда на версии 2.0.8), я подробности не помню как запустил, но точно помню куда копал:

    поставьте просто, например под Win, JDK и запустите jconsole. Выполните коннект к "Ваш наблюдаемый сервер с JMX":"Порт для JMX".
    Как только у Вас пройдет этот коннект, все заработает и с Zabbix.

    Comment

    Working...