Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Solved
Go to solution
Redeploying ManagerNode?
Labels:
- Labels:
-
Cloudera Manager
New Contributor
Created on ‎11-11-2015 01:46 PM - edited ‎09-16-2022 02:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My ManagerNode has gotten corrupted - I can get to the CM UI, but can't SSH in (server refuseed our key) I've not changed any config, and reboot doesn't fix.
Is there anyway of re-rolling just the ManagerNode?
Cheers,
PC
1 ACCEPTED SOLUTION
Guru
Created ‎11-11-2015 02:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Paul,
It is possible to repair the instance by mounting it's EBS volume on
another instance and copying the key files from another working instance in
the cluster (since they all accept the same key). You would need to do this
manually, however - It's not something Cloudera Live can do. It has no
direct access to your account. It works by SSH credentials set up by the
instances, and then deletes these keys when it's finished.
There are several blog and forum posts detailing how to do this, e.g.
http://automagical.rationalmind.net/2015/09/28/regain-access-aws-ec2-instance-lost-access/.
It is a tricky procedure. If you don't have valuable data on this cluster,
you may also consider deleting your cluster, registering for a new access
code and starting a new cluster.
It is possible to repair the instance by mounting it's EBS volume on
another instance and copying the key files from another working instance in
the cluster (since they all accept the same key). You would need to do this
manually, however - It's not something Cloudera Live can do. It has no
direct access to your account. It works by SSH credentials set up by the
instances, and then deletes these keys when it's finished.
There are several blog and forum posts detailing how to do this, e.g.
http://automagical.rationalmind.net/2015/09/28/regain-access-aws-ec2-instance-lost-access/.
It is a tricky procedure. If you don't have valuable data on this cluster,
you may also consider deleting your cluster, registering for a new access
code and starting a new cluster.
1 REPLY 1
Guru
Created ‎11-11-2015 02:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Paul,
It is possible to repair the instance by mounting it's EBS volume on
another instance and copying the key files from another working instance in
the cluster (since they all accept the same key). You would need to do this
manually, however - It's not something Cloudera Live can do. It has no
direct access to your account. It works by SSH credentials set up by the
instances, and then deletes these keys when it's finished.
There are several blog and forum posts detailing how to do this, e.g.
http://automagical.rationalmind.net/2015/09/28/regain-access-aws-ec2-instance-lost-access/.
It is a tricky procedure. If you don't have valuable data on this cluster,
you may also consider deleting your cluster, registering for a new access
code and starting a new cluster.
It is possible to repair the instance by mounting it's EBS volume on
another instance and copying the key files from another working instance in
the cluster (since they all accept the same key). You would need to do this
manually, however - It's not something Cloudera Live can do. It has no
direct access to your account. It works by SSH credentials set up by the
instances, and then deletes these keys when it's finished.
There are several blog and forum posts detailing how to do this, e.g.
http://automagical.rationalmind.net/2015/09/28/regain-access-aws-ec2-instance-lost-access/.
It is a tricky procedure. If you don't have valuable data on this cluster,
you may also consider deleting your cluster, registering for a new access
code and starting a new cluster.
