Showing results for 
Show  only  | Search instead for 
Did you mean: 

Server's host key not cached on target servers

When running the inventory from a beacon, in a particular subnet assigned to it, I'm getting the following error.


Is there a way to automate the storage of the key in the targets, other than connecting manually in ssh on each of them?



(3) Replies
By Community Manager Community Manager
Community Manager

The "The server's host key is not cached in the registry" message is part of normal output for this process and wouldn't normally indicate a problem.

What is abnormal is the connection being unexpectedly closed. The output doesn't give much indication of why that would be occurring and I don't have any particularly insightful guesses as to what is likely to cause it.  I wonder (wildly guessing) if the SSH server has some sort of timeout set up that is breaking the connection after a time.

A troubleshooting step you could try may be to manually run something like the following on the beacon to see if basic SSH connections are working:

"C:\Program Files (x86)\Flexera Software\Inventory Beacon\RemoteExecution\plink.exe" -batch -ln flexerauser_linux "echo success"


(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
Thanks I will try this

Sadly we have no access to the beacon, so this cannot be tried