[Spacewalk-list] RE: Spacewalk Monitoring Strangeness

Jeff Moody jeff.moody at evscorporation.com
Tue Aug 11 18:02:36 UTC 2009


For reference, I resolved the issue.
I had missed the instructions at https://rhn.redhat.com/rhn/help/reference/rhn370/en/s1-mon-rhnmd.jsp and had not explicitly added the Satellite server in the authorized_keys - I thought (erroneously) that the scout push would do that for me.

Added the keys, ensured the permissions were correct, and monitoring is working.

----

Jeff Moody
Senior Systems Engineer
 
EVS Corporation
5050 Poplar Avenue ,Suite 1600
Memphis, Tennessee 38157
(901) 259-2387 - 24x7 Helpdesk

(901) 881-0919 - Office
(901) 497-1444 - Cell
jeff.moody at evscorporation.com


-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jeff Moody
Sent: Tuesday, August 11, 2009 10:31 AM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk Monitoring Strangeness

My apologies if this is a simple issue where I am merely missing a critical line in documentation...however, I am pretty new to the Spacewalk/Satellite platforms.

My main focus of setting up Spacewalk is getting the Spacewalk monitoring working to monitor some deeper statistics on our servers than our current monitoring solution supports.

That being said, I have a VMWare VM running CentOS 5.3 x86 and Spacewalk 0.6.

I have installed the RHNMD on a handful of servers (including the spacewalk server itself) and the RHNMD service daemon is running.
Monitoring Scout Config (https://localhost/network/monitoring/scout/index.pxt) reports that it is fully updated after scheduling a push.

Despite this, all of the "linux" command group probes are reporting the following error:
Status:	UNKNOWN, The RHN Monitoring Daemon (RHNMD) is not responding: Permission denied (publickey,keyboard-interactive). Please make sure the daemon is running and the host is accessible from the monitoring scout. Command was: /usr/bin/ssh -l nocpulse -p 4545 -i /var/lib/nocpulse/.ssh/nocpulse-identity -o StrictHostKeyChecking=no -o BatchMode=yes 127.0.0.1 /bin/sh -s


Is there some magical missing step to getting the nocpulse user trusted (even on the local host) so that these probes work?

Thanks a lot for your assistance.

----

Jeff Moody
Senior Systems Engineer
 
EVS Corporation
5050 Poplar Avenue ,Suite 1600
Memphis, Tennessee 38157
(901) 259-2387 - 24x7 Helpdesk

(901) 881-0919 - Office
(901) 497-1444 - Cell
jeff.moody at evscorporation.com


_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list




More information about the Spacewalk-list mailing list