- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus Enterprise Software
- >
- Agent failed to communicate
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 07:38 AM
12-03-2024 07:38 AM
Hi Experts,
Agent installation is successful however it is not communicating to CMP. I’m seeing following error from the VM.
java.net.SocketException: Connection reset
at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(Unknown Source)
at java.base/sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:356)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:994)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Unknown Source)
[nioEventLoopGroup-2-2] ERROR com.morpheus.agent.websocket.StompClient - Failed to connect websocket: Connection reset
[nioEventLoopGroup-2-3] INFO com.morpheus.agent.websocket.WebSocketClientHandler - WebSocket Client disconnected!
Any advise?
Thanks.
BR
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 05:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 08:41 PM
12-04-2024 08:41 PM
Re: Agent failed to communicate
@rboyd Thanks for the comments. We requested end-user to have a look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 09:50 AM
12-03-2024 09:50 AM
Re: Agent failed to communicate
@Ollie_Phillips Thanks for the advise and help us to narrow down the issue. we will work with Load balancer support to check further on this.
Thank you again.
BR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 09:27 AM
12-03-2024 09:27 AM
Re: Agent failed to communicate
@Ollie_Phillips Thanks for suggestion. This is 3 Node HA. We did not enable 443 port for Nodes. we allowed 443 only for Load Balancer.
error seems changed to following.
ERROR com.morpheus.agent.websocket.StompClient - Failed to connect websocket: connection timed out after 30000 ms: /x.x.x.x:443
We will test it once port allowed. can we add all 3 nodes to VM agent config file? Otherwise, if configured node goes down, will the agent stop communicate with CMP?
Any specific configuration need to be enabled on netscaler load balancer to resolve this issue?
Thank you very much for your cmts ![]()
BR.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 09:46 AM
12-03-2024 09:46 AM
Re: Agent failed to communicate
Hi, my suggestion to target a node was for testing only. AFAIK can not use multiple nodes in the Agent rb file. The LB should be made to proxy the connection in a HA solution, fall back is single node for connection but you’ve spotted the risks with that already.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 09:47 AM
12-03-2024 09:47 AM
Re: Agent failed to communicate
Meant to add, i’ve no specific knowledge re Netscaler LB config I can share.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2025 10:23 AM
01-23-2025 10:23 AM
Re: Agent failed to communicate
Just an update, web socket enabled in the LB and that solved the issues. Thanks helping to narrow down the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 08:42 AM
12-03-2024 08:42 AM
Re: Agent failed to communicate
Is this a HA load balanced solution? Agent wants a websocket connection and some load balancers can’t proxy/support it.
You can test by changing cloud settings appliance URL to a node in the appliance and the updating the agent on the VM you expect to connect.
It will bypass the LB
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]