Advertisement
I have a new CentOS server I’m trying to scan using SSH. Spiceworks recognizes port 22 is open. When I manually indicate it is a Unix computer and enter the SSH credentials it indicates successful connection. On the CentOS server I can see Spiceworks succesfully logging in. But the scan always fails.<\/p>\n
What gives? The one thing I can think of is that a server with the same host name was setup last week for some initial testing. Would Spiceworks have a key cached that I need to reset somehow?<\/p>","upvoteCount":2,"answerCount":8,"datePublished":"2015-04-14T16:53:56.000Z","author":{"@type":"Person","name":"joshuapich8950","url":"https://community.spiceworks.com/u/joshuapich8950"},"acceptedAnswer":{"@type":"Answer","text":"
I ended up recreating the VM with a slightly different name. Initial scan worked perfectly.<\/p>","upvoteCount":0,"datePublished":"2015-04-20T11:55:40.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/7","author":{"@type":"Person","name":"joshuapich8950","url":"https://community.spiceworks.com/u/joshuapich8950"}},"suggestedAnswer":[{"@type":"Answer","text":"
I have a new CentOS server I’m trying to scan using SSH. Spiceworks recognizes port 22 is open. When I manually indicate it is a Unix computer and enter the SSH credentials it indicates successful connection. On the CentOS server I can see Spiceworks succesfully logging in. But the scan always fails.<\/p>\n
What gives? The one thing I can think of is that a server with the same host name was setup last week for some initial testing. Would Spiceworks have a key cached that I need to reset somehow?<\/p>","upvoteCount":2,"datePublished":"2015-04-14T16:53:56.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/1","author":{"@type":"Person","name":"joshuapich8950","url":"https://community.spiceworks.com/u/joshuapich8950"}},{"@type":"Answer","text":"
Delete the device and let SW rediscover it. Also add your ssh credentials in as usable credentials for a scan.<\/p>","upvoteCount":0,"datePublished":"2015-04-14T18:22:10.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/2","author":{"@type":"Person","name":"bradt2","url":"https://community.spiceworks.com/u/bradt2"}},{"@type":"Answer","text":"
Tried, that, no difference. It gets picked up again, but scanning fails.<\/p>","upvoteCount":0,"datePublished":"2015-04-15T11:39:22.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/3","author":{"@type":"Person","name":"joshuapich8950","url":"https://community.spiceworks.com/u/joshuapich8950"}},{"@type":"Answer","text":"
Is SW using your root user’s access? If so, I’m not sure what’s up. If not, does the user SW is using have a shell?<\/p>","upvoteCount":0,"datePublished":"2015-04-15T14:08:45.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/4","author":{"@type":"Person","name":"bradt2","url":"https://community.spiceworks.com/u/bradt2"}},{"@type":"Answer","text":"
Yes, using root at the moment.<\/p>","upvoteCount":0,"datePublished":"2015-04-15T14:10:18.000Z","url":"https://community.spiceworks.com/t/inventory-scan-fails-on-centos-device/395866/5","author":{"@type":"Person","name":"joshuapich8950","url":"https://community.spiceworks.com/u/joshuapich8950"}},{"@type":"Answer","text":"
Take a look at these 2 articles, they may help get this fixed:<\/p>\n
https://community.spiceworks.com/help/Resolving_Unknown_Devices#Linux<\/a><\/p>\n