- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: SSH public key authentication failed
Server Management - Systems Insight Manager
1753808
Members
8612
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2011 04:34 PM
02-01-2011 04:34 PM
SSH public key authentication failed
Upgraded to HPSIM V6.2 (Windows) with hotfix. If a host already known to SIM changes it's host key (for example it is rebuilt) then we get SSH public key authentication failed every time a task is run against it.
In the past, I could get rid of it by either mxagentconfig -r -n or if worse comes to worse, delete the node from SIM then redsicover it. But under 6.2 this won't work. It just will not work. I can manually use ssh and I can execute a command manually using ssh user@host cmd but running task through SIM fail with this SSH public key authentication failed error all the time.
Any ideas of how to get rid of it?
In the past, I could get rid of it by either mxagentconfig -r -n or if worse comes to worse, delete the node from SIM then redsicover it. But under 6.2 this won't work. It just will not work. I can manually use ssh and I can execute a command manually using ssh user@host cmd but running task through SIM fail with this SSH public key authentication failed error all the time.
Any ideas of how to get rid of it?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2011 12:08 AM
02-05-2011 12:08 AM
Re: SSH public key authentication failed
Some more information.
The nodes in question (there are about a dozen) are a bit different from many we have in SIM.
They are all Linux hosts - this is not unusual as we have about 3000 hosts in SIM which are linux of various versions.
They get rebuilt quite often (every couple of months) yet are production machines - I cannot go into whay this happens whereas most of the others are very static.
For security reasons, ssh via password only is mandatory.
I was allowed a test case and put the CMS ssh public keys into authorized_keys int he .ssh direcotry for the user used on all hosts for ssh access fromt he CMS. Ran the failing taks again and bingo everything just works. Remove the keys and run the task again and it still works. This seems to indicate that SIM is remembering soemthing that get fouled up when the host key changes but once it gets in once (as a task), it remembers something that lets in get in forever more unless the host key changes again.
I have tried removing all the hosts keys on the CMS via mxagentconfig -r -n and manually editing the known_hosts files with no effect. There has got to be something else.
I guess there is also the question as to whehter or not it is mandatory for the client system to have the CMS ssh public keys. The docuemntation seems to talk alot about keys but not that you MUST use them rather than passwords. Any comments on this?
The nodes in question (there are about a dozen) are a bit different from many we have in SIM.
They are all Linux hosts - this is not unusual as we have about 3000 hosts in SIM which are linux of various versions.
They get rebuilt quite often (every couple of months) yet are production machines - I cannot go into whay this happens whereas most of the others are very static.
For security reasons, ssh via password only is mandatory.
I was allowed a test case and put the CMS ssh public keys into authorized_keys int he .ssh direcotry for the user used on all hosts for ssh access fromt he CMS. Ran the failing taks again and bingo everything just works. Remove the keys and run the task again and it still works. This seems to indicate that SIM is remembering soemthing that get fouled up when the host key changes but once it gets in once (as a task), it remembers something that lets in get in forever more unless the host key changes again.
I have tried removing all the hosts keys on the CMS via mxagentconfig -r -n and manually editing the known_hosts files with no effect. There has got to be something else.
I guess there is also the question as to whehter or not it is mandatory for the client system to have the CMS ssh public keys. The docuemntation seems to talk alot about keys but not that you MUST use them rather than passwords. Any comments on this?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP