BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
vamsinuthalapat
Obsidian | Level 7

SAS Environment Agent not connecting to SAS Environment Manager, getting below error while connecting starting the agent.

 

HQ Agent is running (PID:12037).
Unable to contact agent: Error sending argument: Unable to connect to 127.0.0.1:2145: java.security.cert.CertificateException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed, retried 5 times, cmd=agent:getCurrentAgentBundle

 

 

Please help me on the troubleshoot process.

1 ACCEPTED SOLUTION

Accepted Solutions
anuraagjv
SAS Employee

Try the following:

1. Stop the agent

2. Make a backup of <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/conf/agent.properties

3. Open the file and change from false to true below:

#

# Automatically accept unverified certificates

# accept.unverified.certificates=false

accept.unverified.certificates=true

4. Navigate to the <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/data directory Rename the data folder to data.old.

5. Start the agent and send the command output:

<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh start

6. Check this log file:

<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/log/agent.log

View solution in original post

5 REPLIES 5
anuraagjv
SAS Employee

Try the following:

1. Stop the agent

2. Make a backup of <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/conf/agent.properties

3. Open the file and change from false to true below:

#

# Automatically accept unverified certificates

# accept.unverified.certificates=false

accept.unverified.certificates=true

4. Navigate to the <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/data directory Rename the data folder to data.old.

5. Start the agent and send the command output:

<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh start

6. Check this log file:

<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/log/agent.log

anuraagjv
SAS Employee

Also, make sure nothing is using port 2145 and make sure no hung processes..

vamsinuthalapat
Obsidian | Level 7

Getting below message while starting the service.

 

Error executing remote method: org.hyperic.hq.agent.AgentRemoteException: Unauthorized

anuraagjv
SAS Employee

Hi @vamsinuthalapat - Can you issue the command <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh restart ,  instead of start. The restart command forces agent setup.

Please check the agent.log.  

If the log is still pointing to the listening failure of the port, then you might want to change the port from 2145 to 2144 to see if that starts the agent successfully. This will prove if something is still tying up port 2145.

 

1) Run a stop command on the SAS Environment Manager Agent (./hq-agent.sh stop)

2) Change the agent.properties for that particular agent to listen on a different port (i.e. 2145)  <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/conf/agent.properties

Change the following entries in the agent.properties file:

agent.listenPort=2145

agent.setup.agentPort=2145

 

toL

agent.listenPort=2144

agent.setup.agentPort=2144

 

3) Move the "data" directory itself from the following location <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/

4) Please issue this command and send the output: <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh restart

5) If the agent starts this time, do a "status" on the agent to see if the hq-agent is not setup:

     <SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh status

     If it is not setup, run a restart command on the hq-agent and then you should see the connections.

 

If the above does not resolve the issue, I suggest you to open a ticket with SAS Technical Support.

vamsinuthalapat
Obsidian | Level 7
Thanks a lot @anuraagjv , it worked and running as expected.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 1401 views
  • 0 likes
  • 2 in conversation