"SSH authentication or connection failure" in Linux/UNIX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2013 02:21 AM
Hi,
I have a Red Hat Linux Server in my environment. I have created a user with sudo privileges. When i am running discovery on it, it gives error "SSH authentication or connection failure". While I am able to login to this server via putty & able to run uname -a command successfully.
I have also enabled "debug_ssh = true" & "debug = true" in UNIX-Classify probe. Please find attached ssh.log file & screenshot of access given to user.
looking for a possitive reply.
Regards,
Nikhil Agarwal
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 05:14 AM
we are using Scheduled Import for importing file from mid server and pushing to target tables(we have Data Source)
we don't have any discovery inplace here....
more info check this link : Scheduled import error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 10:41 AM
I would stick with mid.ssh.use_snc=true unless you have a reason not to. At the very least, it has a separate error message for connection and auth failures.
When use_snc is true, what error message do you get?
If it's an auth failure, check credentials. Does your version have the "test credential" feature? That would be a good place to start.
If it's a connection failure check that you can get to connect to port 22 on the target from the mid server.
If all else fails, you can set mid.ssh.debug=true, recreate the failure, and look in the agent log for a tsunami of detail on what's going on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 11:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2016 11:10 AM
"TCP: Connection refused" - Sounds like a firewall issue on the server you're trying to connect to.
"scheduled import job" - Is this a probe over the mid server, or are you importing records into the instance with sftp / scp, or what?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2016 02:02 AM
we are importing records to our instance for Mid server through SFTP
Can you please check this URL : Scheduled import error