ngrinder › ngrinder-user-kr

monitor 에러문의

classic Classic list List threaded Threaded
♦
♦
 8 messages Options
minjae
Reply | Threaded
Open this post in threaded view
♦
♦
|

monitor 에러문의

minjae
테스트 대상 서버에 monitor를 설치하고 ./run_monitor.sh 실행 시 아래와 같이 에러가 발생합니다.

17:36:42.929 [main] INFO  agent config - NGRINDER_AGENT_HOME : /root/.ngrinder_agent
17:36:42.933 [main] WARN  agent config - The agent configuration file '/root/.ngrinder_agent/agent.conf' already exists.
17:36:42.933 [main] WARN  agent config - If you want to use the '/usr/local/ngrinder-monitor/__agent.conf' file
17:36:42.933 [main] WARN  agent config - Please run agent with -o option
17:36:43.048 [main] INFO  starter - ***************************************************
17:36:43.049 [main] INFO  starter - * Start nGrinder Monitor...
17:36:43.049 [main] INFO  starter - ***************************************************
17:36:43.171 [main] INFO  o.n.monitor.agent.RegisterMXBean - Added MXBean:org.ngrinder.monitor:name=System.
17:36:43.171 [main] INFO  o.n.monitor.agent.RegisterMXBean - Default MXBean Initialized.
17:36:43.171 [main] INFO  o.n.monitor.agent.MonitorServer - Service URL:service:jmx:rmi://172.19.31.20:13243/jndi/rmi://172.19.31.20:13243/jmxrmi is initiated.
17:36:43.217 [main] ERROR starter - ERROR: Cannot bind to URL [rmi://172.19.31.20:13243/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.19.31.20; nested exception is:
        java.net.ConnectException: Connection refused (Connection refused)]
17:36:43.221 [main] ERROR starter - Error while starting Monitor
java.io.IOException: Cannot bind to URL [rmi://172.19.31.20:13243/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.19.31.20; nested exception is:
        java.net.ConnectException: Connection refused (Connection refused)]
        at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827) ~[na:1.8.0_201]
        at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432) ~[na:1.8.0_201]
        at org.ngrinder.monitor.agent.MonitorServer.start(MonitorServer.java:101) ~[ngrinder-core-3.4.3.jar:na]
        at org.ngrinder.NGrinderAgentStarter.startMonitor(NGrinderAgentStarter.java:104) [ngrinder-core-3.4.3.jar:na]
        at org.ngrinder.NGrinderAgentStarter.main(NGrinderAgentStarter.java:217) [ngrinder-core-3.4.3.jar:na]
Caused by: javax.naming.ServiceUnavailableException: null
        at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161) ~[na:1.8.0_201]
        at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228) ~[na:1.8.0_201]
        at javax.naming.InitialContext.bind(InitialContext.java:425) ~[na:1.8.0_201]
        at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644) ~[na:1.8.0_201]
        at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427) ~[na:1.8.0_201]
        ... 3 common frames omitted
Caused by: java.rmi.ConnectException: Connection refused to host: 172.19.31.20; nested exception is:
        java.net.ConnectException: Connection refused (Connection refused)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) ~[na:1.8.0_201]
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) ~[na:1.8.0_201]
        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) ~[na:1.8.0_201]
        at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:338) ~[na:1.8.0_201]
        at sun.rmi.registry.RegistryImpl_Stub.bind(RegistryImpl_Stub.java:60) ~[na:1.8.0_201]
        at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155) ~[na:1.8.0_201]
        ... 7 common frames omitted
Caused by: java.net.ConnectException: Connection refused (Connection refused)
        at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_201]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_201]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_201]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_201]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_201]
        at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_201]
        at java.net.Socket.connect(Socket.java:538) ~[na:1.8.0_201]
        at java.net.Socket.<init>(Socket.java:434) ~[na:1.8.0_201]
        at java.net.Socket.<init>(Socket.java:211) ~[na:1.8.0_201]
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) ~[na:1.8.0_201]
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148) ~[na:1.8.0_201]
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) ~[na:1.8.0_201]
        ... 12 common frames omitted
Usage: run_monitor.sh [options]
  Options:
    -ah, --agent-home
       this agent's unique home path. The default is ~/.ngrinder_agent
    -o, --overwrite-config
       overwrite overwrite the existing .ngrinder_agent/agent.conf with the
       local __agent.conf
    -s, --silent
       silent mode
    -v, --version
       show version
    -help, -?, -h
       prints this message


포트도 다 열려있는데 이와같은 에러가 발생하는 이유는 뭘까요?
감사합니다
junoyoon
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

junoyoon
Administrator
Root 권한으로 실행시켜도 같은 결과 인가요?
minjae
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

minjae
네 root 권한으로 실행했을때 발생한 결과입니다.  
junoyoon
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

junoyoon
Administrator
해당 포트를 이미 다른 프로그램이 사용하고 있지 않은가 싶은데요. 이미 monitor를 띄워 놨거나..
확인이 필요합니다.
minjae
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

minjae
monitor를 이미 띄워두거나 하지는 않았는데... 어떻게 확인을 해봐야 할까요?;;
junoyoon
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

junoyoon
Administrator

2019년 11월 14일 (목) 오전 11:14, minjae [via ngrinder] <[hidden email]>님이 작성:
monitor를 이미 띄워두거나 하지는 않았는데... 어떻게 확인을 해봐야 할까요?;;

If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/monitor-tp2551p2558.html
To start a new topic under ngrinder-user-kr, email [hidden email]
To unsubscribe from ngrinder-user-kr, click here.
NAML
minjae
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

minjae
안녕하세요. 사용중인 포트를 확인해봤습니다.
<controller>
# netstat -tulpn | grep LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1036/sshd      
tcp6       0      0 127.0.0.1:12000         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12001         :::*                    LISTEN      1173/java      
tcp6       0      0 :::16001                    :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12002         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12003         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12004         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12005         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:8005           :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12006         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12007         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12008         :::*                    LISTEN      1173/java      
tcp6       0      0 127.0.0.1:12009         :::*                    LISTEN      1173/java      
tcp6       0      0 :::8080                      :::*                    LISTEN      1173/java      
tcp6       0      0 :::22                          :::*                    LISTEN      1036/sshd

<target server (ngrinder-monitor)>
# netstat -tulpn | grep LISTEN
tcp        0      0 0.0.0.0:17373           0.0.0.0:*               LISTEN      3891/jsvc.exec  
tcp        0      0 0.0.0.0:38080           0.0.0.0:*               LISTEN      3891/jsvc.exec  
tcp        0      0 0.0.0.0:8080             0.0.0.0:*               LISTEN      3891/jsvc.exec  
tcp        0      0 0.0.0.0:22                 0.0.0.0:*               LISTEN      24348/sshd      
tcp6       0      0 :::22                          :::*                    LISTEN      24348/sshd

13243 포트는 사용중이지 않습니다....

이것 관련해서 조금 다른 문의를 드리겠습니다.
성능대상 서버에 monitor를 하면 어떤 데이터를 어떻게 보여주는지 알수있을까요?
controller에서 어떻게 보여주는지... csv데이터 값만 오는것인지...

어느정도 사용가능한지 판단후에 위 문제를 시간을 들여서라도 해결을 할지 아니면 모니터링을 사용하지 않을지 결정하려고 합니다.

조언 부탁드립니다.
감사합니다.


junoyoon
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: monitor 에러문의

junoyoon
Administrator
그냥 모니터링 사용하지 않으시는게 나을것 같습니다.

https://github.com/netdata/netdata 를 사용하셔서 로드시에 상태 보시는 것이 좋을것 같습니다.
Free forum by Nabble Edit this page