On Tue, 06 Jan 2009, Mirza Dedic wrote: > Hello, > > I have a Nagios system running (3.0.X) along with Nagios Plug-ins; while I am > able to get Nagios to monitor all the things I need on a Win32 box (using > NSClient++ & Check_NT); I am having difficulty getting check_by_ssh to work > for me. > > I have previously never used check_by_ssh; I am also fairly new to the linux > OS. My OS is Ubuntu and many of the servers I want to monitor are RHEL4 or > Fedora. > > I know that to get check_by_ssh to work, I need to create a private/public > certificate on the client/server; anyone shed some light on how to create > this? > > Do I create the key on my Nagios box? Under the same user that was used when > compiling Nagios? > > For the remote host (monitored linux server); what do I need to do? Create > the same user-id? How do I apply the certificate from my Nagios Host to the > monitored Host so that my shell scripts can connect to the Host B without a > password prompt? > > Please if you could, shed some light for a beginner. > > Also, our environment is using Kerberos, all the servers use SSH/Kerberos, > this way when users are created in Active Directory they are replicated > across the linux servers (is this why I can?t find authorized_keys file?)
This doc's not bad. You'll want to create a key for the user Nagios runs as on the Nagios box. The user on the other end doesn't matter so much, as long as the Nagios user's key is authorized to log in on the other side as that user. http://www.sshkeychain.org/mirrors/SSH-with-Keys-HOWTO/ ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
