• State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    167
  • Views views
    200
  • Users 0 members are here
Related
Options

Unable to launch the SA client, Remote host terminated the handshake

Neha P

I have started exploring server automation very recently so I am very new to SA.

I was able to successfully install and use SA for many days.

BUt recently my Test SA server was down for few days. And I brought it up today. But now I am unable to access SA client.

When I try to launch my SA client, its popping up an error which says "Unable to launch the sa client, remote host terminated the handshake"

When I tried /opsware-saas startsync it exited with errors

and the logs in ../appdata/SA/ 

I found this in one of the logs, SA client was unable to access after this

Should I regenerate the certificate and import it or is there any other method for resolving this issue.

Please help me out with this issue.

  • 0   in reply to Sharma realtors Solution

    I recommend that you first try a restart of all SA services on the core:

       # /etc/init.d/opsware-sas restart

    You can also verify that your services are up using:

       # /etc/init.d/opsware-sas health

  • 0 in reply to boneimre

    Hi boneimre,

    I have already tried those.

    I'm getting errors because of opswgw-agws.

    I get the below errors when i run /etc/init.d/opsware-sas health

    -------------- sshd --------------
    >>> Verify status...
    Verify "sshd" is running: FAILURE (process not running)

    -------------- apxproxy --------------
    >>> Verify status...
    Verify local "apxproxy" is listening on port 1027: FAILURE (Connection refused)
    Verify "apxproxy" running: FAILURE (process not running)

    -------------- spoke --------------
    >>> Verify status...
    Verify local "spoke" is listening on port 8020: FAILURE (Connection refused)
    >>> Verify functionality...
    "spoke_test_user" not specified - using "detuser".
    "spoke_test_passwd" must be set for user "detuser" for this test to run.
    Skipping test...

    -------------- agentcache --------------
    >>> Verify status...
    Verify "agentcache" running: FAILURE (pidfile does not exist)

    -------------- occ.server --------------
    >>> Verify prerequsites...
    Verify hostname "occ" is resolvable: SUCCESS
    >>> Verify status...
    Verify "occ.server" is running: FAILURE (process not running)

    -------------- httpsProxy --------------
    >>> Verify status...
    Verify "httpsProxy" is running: FAILURE (process not running)
    Verify local "httpsProxy" is listening on port 80: FAILURE (Connection refused)

    -------------- opsware-agent --------------
    >>> Verify status...
    Verify "opsware-agent" running: SUCCESS

    -------------- smartboot --------------
    >>> Verify status...
    Verify "smartboot" is mounted: FAILED
    Failed to perform "health" operation on Opsware SAS components.

    But sshd is running on my system.

    Now i am starting the services individually including hub, httpsproxy, occ.server etc. But still i am not able to solve the issue

Resources

Support
Documentation
Learning Services
CyberRes Academy
Partner Programs
Contact us
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Conduct
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.