question

amit82ocp_172818 avatar image
amit82ocp_172818 asked amit82ocp_172818 answered

Unable to install OpsCenter agent

I am unable to install agent from ops center and getting below error in alert install logs.

10.128.0.2 Agent Status
{  "rack": "rack1",  "agent_status": {    "storage_cassandra": {      "updated_at": null,      "last_up": 0,      "status": "unknown"    },    "last_seen": null,    "version": null,    "condition": "NO_AGENT_DETECTED",    "install_status": {      "error-message": "The ssh-private-key value on machine-credential 'unmanaged-mc-KillrVideoCluster-1582472004071' is not a properly formatted private key. login-user="amit82ocp" become-mode="sudo" machine-credential-id="93e5eb73-4b05-45af-bea1-da2836a42a4a" machine-credential-name="unmanaged-mc-KillrVideoCluster-1582472004071" ssh-management-port="22" ssh-management-address="10.128.0.2"",      "state": "FAILED"    },    "jmx": {      "updated_at": null,      "last_up": 0,      "status": "unknown"    },    "monitored_cassandra": {      "updated_at": null,      "last_up": 0,      "status": "unknown"    },    "http": {      "failure_reason": "The agent is not responding to HTTP requests: java.net.ConnectException: Connection refused ",      "updated_at": 1582472032,      "last_up": 0,      "status": "down"


UPDATE - Follow up question:

I have install agents manually on both node however still getting error in logs as below.

Opscenter:-

2020-02-24 06:45:13,219 [KillrVideoCluster] WARN: These nodes reported this message, Nodes: ['10.128.0.3', '10.128.0.2'] Message: HTTP request https://10.128.0.3:61621/v1/connection-status? failed: java.net.ConnectException: Connection refused (MainThread)

Node1:-

ERROR [async-dispatch-6] 2020-02-24 06:46:33,688 Incorrect Keystore password for /cassandra/datastax-agent-6.7.7/ssl/agentKeyStore, failing verification.
ERROR [async-dispatch-6] 2020-02-24 06:46:33,689 Error starting Jetty server.
clojure.lang.ExceptionInfo: throw+: {:type :invalid-keystore-credentials, :message "The keystore path or credentials are invalid. Unable to launch HTTP server."} {:type :invalid-keystore-credentials, :message "The keystore path or credentials are invalid. Unable to launch HTTP server."}
    at slingshot.support$stack_trace.invoke(support.clj:201)


opscenterinstallationagent
2 comments
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Erick Ramirez avatar image Erick Ramirez ♦♦ commented ·

@amit82ocp_172818 I've deleted your "answer" post because it's not an answer. Instead, I've updated your question with the new details. Cheers!

0 Likes 0 ·
amit82ocp_172818 avatar image amit82ocp_172818 Erick Ramirez ♦♦ commented ·

Thanks, could you please suggest, where I am lacking ?

0 Likes 0 ·
amit82ocp_172818 avatar image
amit82ocp_172818 answered

First of fall thanks for all the reply on my question.

Second below is the solution due to which agent were not able to communicate with ops-center.

The agent_keyfile value was not correct due to this agent were not able to coordinate with opscenter.

Regards,
Amit


Share
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Erick Ramirez avatar image
Erick Ramirez answered Aleks Volochnev converted comment to answer

@amit82ocp_172818 As the message you posted indicates, the issue is that you have not provided a correctly formatted SSH key:

The ssh-private-key value on machine-credential 'unmanaged-mc-KillrVideoCluster-1582472004071' is not a properly formatted private key

You will need to check the key and provide it in the correct format. Cheers!

4 comments Share
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Erick Ramirez avatar image Erick Ramirez ♦♦ commented ·

@amit82ocp_172818 The error you posted clearly states that it can't start the agent because the keystore password is incorrect:

ERROR [async-dispatch-6] 2020-02-24 06:46:33,688 Incorrect Keystore password for /cassandra/datastax-agent-6.7.7/ssl/agentKeyStore, failing verification.

Please check the keystore password you've configured and try again. Cheers!

0 Likes 0 ·
amit82ocp_172818 avatar image amit82ocp_172818 Erick Ramirez ♦♦ commented ·

Kindly suggest steps to correct the keystore password


Regards,

Amit

0 Likes 0 ·
Erick Ramirez avatar image Erick Ramirez ♦♦ amit82ocp_172818 commented ·

@amit82ocp_172818 You need to do exactly that -- fix the keystore password you configured because it is wrong. You were the one who chose the keystore password when you created the certificates. Whatever you configured for the agent isn't correct so you need to fix it. Cheers!

1 Like 1 ·
Show more comments