Unable to monitor CoreOS by rsp or by robot.
Case opened at CA Support
Case Number & Title: 00336013: Robot installation on CoreOS
Description & Error Message: I tried to install robot on CoreOS
Robot install was not OK.
Excerpt from nimldr.log
Mar 15 15:59:48:198 nimldr: Could not figure out what Linux version you are running!
Mar 15 15:59:48:198 nimldr: Please report the following system information to support@nimsoft.com
Mar 15 15:59:48:198 nimldr: sysname: Linux
Mar 15 15:59:48:198 nimldr: node : NLEPOSL003
Mar 15 15:59:48:198 nimldr: release: 4.2.2-coreos-r2
Mar 15 15:59:48:198 nimldr: version: #2 SMP Tue Feb 2 13:27:19 UTC 2016
Mar 15 15:59:48:198 nimldr: machine: x86_64
I also tried to use rsp but when discovering the CoreOS server I get failed.
Excerpt of rsp.log:
Mar 15 14:39:29:810 [3464] rsp: thrDiscoverHost: Called with hostname=NLEPOSL003
Mar 15 14:39:29:810 [3464] rsp: thrDiscoverHost: Detecting the IP address for the specified host
Mar 15 14:39:30:826 [3464] rsp: thrDiscoverHost: Discovering OS
Mar 15 14:39:30:826 [3464] rsp: Connection failed for host NLEPOSL003: kex error : did not find one of algos diffie-hellman-
group1-sha1 in list curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 for kex algos
Mar 15 14:39:30:826 [3464] rsp: thrDiscoverHost: Connection attempt with NLEPOSL003 failed.
So, is it possible to monitor a CoreOS server with nimbus?
Edvin Vrancx