You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are following Storm-Deploy ( https://github.com/nathanmarz/storm-deploy ) to deploy storm cluster on AWS Cloud. Our cluster is being successfully deployed and the separate EC2 instances are being spawned for Nimbus, Zookeeper and Supervisors.
However we are not being able to connect to Storm UI. Further we are not able to deploy the topology in the cluster as it cannot connect to Nimbus using ssh.
Each time storm-deploy launches a new cluster, it creates a new key-pair. We are not able to locate where the pem file of the new key pair is being saved.
We have tried connecting with
authorized_keys
id_rsa
id_rsa.pub
as pem file using ssh command with Nimbus, Zookeeper and Supervisors machines. Each time we are getting the same error:
"Permission denied (public key)"
Please suggest how to login to Nimbus and submit topology.
We are following Storm-Deploy ( https://github.com/nathanmarz/storm-deploy ) to deploy storm cluster on AWS Cloud. Our cluster is being successfully deployed and the separate EC2 instances are being spawned for Nimbus, Zookeeper and Supervisors.
However we are not being able to connect to Storm UI. Further we are not able to deploy the topology in the cluster as it cannot connect to Nimbus using ssh.
Each time storm-deploy launches a new cluster, it creates a new key-pair. We are not able to locate where the pem file of the new key pair is being saved.
We have tried connecting with
as pem file using ssh command with Nimbus, Zookeeper and Supervisors machines. Each time we are getting the same error:
"Permission denied (public key)"
Please suggest how to login to Nimbus and submit topology.
Our pallet.clj file:
(defpallet
:services
{
:default {
:blobstore-provider "aws-s3"
:provider "aws-ec2"
:environment {:user {:username "storm"
:private-key-path "
/.ssh/id_rsa"/.ssh/id_rsa.pub"}:public-key-path "
:aws-user-id "XXXX-XXXX-XXXX"}
:identity "XXXXXXXXXXXX"
:credential "XXXXXXXXXX"
:jclouds.regions "us-west-2"
}
})
The text was updated successfully, but these errors were encountered: