Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test-marist-sles15-s390x-2 - NoRouteToHostException: No Route to Host failures #2869

Closed
smlambert opened this issue Dec 23, 2022 · 6 comments

Comments

@smlambert
Copy link
Contributor

[2022-12-22T19:14:12.439Z] CL1 j> 2022/12/22 19:14:11.299 Failed to connect to Monitored VM after 30 attempts in 178 seconds - giving up.  Connection Exception received is below:
[2022-12-22T19:14:12.439Z] CL1 stderr java.rmi.ConnectIOException: Exception creating connection to: 148.100.74.154; nested exception is: 
[2022-12-22T19:14:12.439Z] CL1 stderr 	java.net.NoRouteToHostException: No route to host (Host unreachable)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.rmi/sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:635)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.rmi/sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:209)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.rmi/sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:196)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:132)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.management.rmi/javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.management.rmi/javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2105)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.management.rmi/javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:321)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:229)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at net.adoptopenjdk.test.jlm.remote.ServerConnector.doConnect(ServerConnector.java:276)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at net.adoptopenjdk.test.jlm.remote.ServerConnector.getServerConnection(ServerConnector.java:101)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at net.adoptopenjdk.test.jlm.remote.ServerConnector.<init>(ServerConnector.java:63)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at net.adoptopenjdk.test.jlm.remote.MemoryProfiler.<init>(MemoryProfiler.java:67)
[2022-12-22T19:14:12.439Z] CL1 stderr 	at net.adoptopenjdk.test.jlm.remote.MemoryProfiler.main(MemoryProfiler.java:100)
[2022-12-22T19:14:12.439Z] CL1 stderr Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:

All TestJlmRemote* system test targets and NioLoad* system test targets fail (see TRSS view)

Any other details:

@steelhead31
Copy link
Contributor

Issue is that this machine cant create the jmx/rmi agent to connect too..

java -Xmx256m -Djavax.net.ssl.keyStore=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/src/test.jlm/net/adoptopenjdk/test/jlm/testkeys -Djavax.net.ssl.trustStore=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/src/test.jlm/net/adoptopenjdk/test/jlm/testkeys -Djavax.net.ssl.keyStoreType=JKS -Djavax.net.ssl.trustStoreType=JKS -Djavax.net.ssl.keyStorePassword=passphrase -Djavax.net.ssl.trustStorePassword=passphrase -Dcom.sun.management.jmxremote.password.file=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/tmp/jmxremote.password -XX:+UseCompressedOops -classpath /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/bin:/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/systemtest_prereqs/junit/junit.jar net.adoptopenjdk.test.jlm.remote.ClassProfiler server /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/results/scls_server.log /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/results/scls_server.csv auth controlRole control1 localhost 1234

@steelhead31
Copy link
Contributor

Cannot connect to port localhost:1234 , even though no firewall is running.

@sxa
Copy link
Member

sxa commented Feb 17, 2023

I'm curious - does that command line work ok elsewhere? It has localhost 1234 at the end of it but when I had a quick play yesterday localhost seemed ok - it was only access via the external interfaces IPs that were being blocked (which is what the original failure description has) so I'm somewhat surprised it fails. Are you sure that the thing listening on 1234 is started by the test automatically? Does that command work on "known good" machines?

@steelhead31
Copy link
Contributor

I dug the command out of the test run output, as thats the point it was hanging...

@sxa sxa added this to the 2023-03 (March) milestone Feb 22, 2023
@sxa sxa modified the milestones: 2023-03 (March), 2023-04 (April) Apr 3, 2023
@sxa sxa modified the milestones: 2023-04 (April), 2023-05 (May) May 16, 2023
@sxa sxa modified the milestones: 2023-05 (May), 2023-06 (June) Jun 6, 2023
@sxa sxa modified the milestones: 2023-06 (June), 2023-07 (July) Jul 7, 2023
@sxa sxa modified the milestones: 2023-11 (November), Backlog Jan 3, 2024
@sxa
Copy link
Member

sxa commented Nov 5, 2024

Marist networking related. Verify if it still exists and whether we can raise upstream with Marist.

@sxa
Copy link
Member

sxa commented Nov 5, 2024

Potential dup of #2807

@sxa sxa closed this as completed Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants