- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- "Unable to open connection to agent" error
Operating System - OpenVMS
1753779
Members
7859
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-01-2004 10:59 PM
04-01-2004 10:59 PM
"Unable to open connection to agent" error
Hi there
Can anyone help me with the following error message that I recieve from one of my system while trying to connect to the other one.
"error contacting agent node_name
"error opening connectin on port 5601
cps_client_handshake:error reading version from server
"no bytes read from remote process while reading header
"unable to open connection to agent
"agent update failed"
Regards
Can anyone help me with the following error message that I recieve from one of my system while trying to connect to the other one.
"error contacting agent node_name
"error opening connectin on port 5601
cps_client_handshake:error reading version from server
"no bytes read from remote process while reading header
"unable to open connection to agent
"agent update failed"
Regards
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2004 01:19 AM
04-02-2004 01:19 AM
Re: "Unable to open connection to agent" error
I suppose:
Application on node1 tryes to send a message on Node2, port 5601.
Possible causes:
* Can Node2 be accessed from node1?
* Does port 5601 on Node2 actually REACT?
If the connection is TCP-based, you can check this by doing this from node1:
$ TELNET node2 5601
If this returns DIRECTLY with an error, check port 5601 on node2.
If you have defined a service on node2 on port 5601, check these:
* Has the service been enabled?
* Is access allowed from node1?
* Has the user actually has been defined in UAF for NETWORK ACCESS and has sufficient quota and privilige. Another problem I found once was that the account was expired....
* Check accounting for this user (/PROCESS_TYPE=NETWORK/USER=). It may give you a clue on what's wrong.
* Check this user's SYS$LOGIN (found in UAF). There should be a log file (unless you specified NOLOG on the service. If so, aenable logging!). If the logfile does not exists, check access!
* the file you specified must exist in SYS$LOGIN of that user, but you can specify another location. However: beware that any logical (explicitly mentioned as well as implied) MUST be defined /SYSTEM (at least).
* there shouldn't be any SET TERM/INQ in the SSYS$MANAGER:SYLOGIn.COM and LOGIN.COM of this user. This _could_ crash the service procedure.
If it's a UDP based service, checks apply as well, but I'm not sure if ou could use telnet for checking.
If a program on node2 is to listen to this port, there shlouldn't be a service defined at all on that port. Check logs of that program.
Willem
Application on node1 tryes to send a message on Node2, port 5601.
Possible causes:
* Can Node2 be accessed from node1?
* Does port 5601 on Node2 actually REACT?
If the connection is TCP-based, you can check this by doing this from node1:
$ TELNET node2 5601
If this returns DIRECTLY with an error, check port 5601 on node2.
If you have defined a service on node2 on port 5601, check these:
* Has the service been enabled?
* Is access allowed from node1?
* Has the user actually has been defined in UAF for NETWORK ACCESS and has sufficient quota and privilige. Another problem I found once was that the account was expired....
* Check accounting for this user (/PROCESS_TYPE=NETWORK/USER=
* Check this user's SYS$LOGIN (found in UAF). There should be a log file (unless you specified NOLOG on the service. If so, aenable logging!). If the logfile does not exists, check access!
* the file you specified must exist in SYS$LOGIN of that user, but you can specify another location. However: beware that any logical (explicitly mentioned as well as implied) MUST be defined /SYSTEM (at least).
* there shouldn't be any SET TERM/INQ in the SSYS$MANAGER:SYLOGIn.COM and LOGIN.COM of this user. This _could_ crash the service procedure.
If it's a UDP based service, checks apply as well, but I'm not sure if ou could use telnet for checking.
If a program on node2 is to listen to this port, there shlouldn't be a service defined at all on that port. Check logs of that program.
Willem
Willem Grooters
OpenVMS Developer & System Manager
OpenVMS Developer & System Manager
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP