Issues during the install of ASM tunnel client

book

Article ID: 207722

calendar_today

Updated On:

Products

CA App Synthetic Monitor

Issue/Introduction

During the installation of the tunnel client, we are having an issue with the start of tunnel client.

We are observing the follow error:

Jan 18, 2021 2:45:54 PM com.ca.asm.optunnel.client.tyrus.TyrusTunnelClient start
INFO: Connecting to wss://opp1.asm.saas.broadcom.com:443/ddbdad9e-5593-11eb-a655-42010a671387
Jan 18, 2021 2:45:54 PM com.ca.asm.optunnel.client.tyrus.TunnelReconnectHandler onConnectFailure
SEVERE: Reconnecting, attempt 1
javax.websocket.DeploymentException: Connection failed.
at org.glassfish.tyrus.container.jdk.client.JdkClientContainer$1.call(JdkClientContainer.java:177)
at org.glassfish.tyrus.container.jdk.client.JdkClientContainer$1.call(JdkClientContainer.java:103)
at org.glassfish.tyrus.container.jdk.client.JdkClientContainer.openClientSocket(JdkClientContainer.java:182)
at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:645)
at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:694)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishConnect(UnixAsynchronousSocketChannelImpl.java:252)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:198)
at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
at sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:293)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
... 3 more


At our proxy, we have follow error:

2021-01-18 13:27:34 75066 10.237.111.29 39774 - 119 185 - - tcp_error 503 DENIED "Technology/Internet" "Technology/Internet" - TCP_ERR_MISS CONNECT - "Go-http-client/1.1" tcp registry.asm.broadcom.com 443 / - - tcp://registry.asm.broadcom.com:443/ 10.XX7.XX.XX3 10.XX7.XX.XX3 http.proxy XX.X4.XX1.2XX 443 registry.asm.broadcom.com "none" "none" - - - none none - - - 10.XX7.XX.XX3 "Ambiguous - Special Use" - 1 - - - - - 80 - 0

Cause

It seems like the issue was due to corrupt yum.conf.

 

Environment

Release : SAAS

Component : APP SYNTHETIC MONITOR ENVIRONMENTAL

Resolution

Please carefully review the /etc/yum.conf. The settings should look like as follows:

On RHEL / CentOS 7 / Oracle Linux
To enter proxy configuration, edit /etc/yum.conf:
proxy=http://<proxy address>:<port>
proxy_username=<username>
proxy_password=<password>

Additional Information

If the OPMS/tunnel client is set up to use a proxy, use this command to test the connection:

proxychains4 wget https://opp2.asm.saas.broadcom.com --no-check-certificate

AND

proxychains4 wget https://opp1.asm.saas.broadcom.com --no-check-certificate

If the output looks as follows this indicates issue with HTTP proxy.

[proxychains] config file found: /usr/local/etc/proxychains.conf

[proxychains] preloading /usr/local/lib/libproxychains4.so

[proxychains] DLL init: proxychains-ng 4.14-git-36-g6c029fd

--2021-01-21 13:22:44--  https://opp2.asm.saas.broadcom.com/

Resolving proxy.adgr.net (proxy.adgr.net)... 224.0.0.1

Connecting to proxy.adgr.net (proxy.adgr.net)|224.0.0.1|:80... [proxychains] Strict chain  ...  10.XXX.XX.XX4:80  ...  10.XXX.XX.XX4:80 <--denied

failed: Connection refused.