ok. after another careful reading of the man page including the line: ssh — Monitor SSH service. Shortcut for: service=ssh tcp i went to have a look at "service" where "Availability" says: windows simple enough, if im running debian, i can hardly be using windows checks for my ssh. right? or should it work anyways? in which case, do i need a specific restricted ssh user for bigsis? can i just slap the user with into the uxmon-asroot file? btw: i tried ssh 127.0.0.1 from command line and it works fine. thanks for any tips or hints as to how to monitor the ssh (not the process as i got that working fine, but the actually WORKING of sshd), t. Peter Varlien wrote: > Please note that you guys are testing two very different things here. > > The "procs" test checks that there is at least one sshd process running (and > also provides a performance graph of how many sshd processes are running > over time). It doesn't show that the ssh service is actually WORKING. > > The "ssh" test actually tries to connect to the ssh port at the address > specified. I suspect that this could be Paul's problem: maybe BigSister is > attempting to connect to the localhost address (127.0.0.1), but sshd is not > configured to listen to that address. Another possibility is access > controlls, i.e. hosts.allow or hosts.deny, that don't allow the host to > accept connections from itself. Thinking about it, the latter is more likely > to be the problem than the former. > > Hope this helps, > > Peter > -- > ---------------------------------------------------------------------------- > Peter Varlien Telephone: +47 7288 0572 > Fritz Aabakkens vei 17 Mobile phone: +47 917 69 384 > N-7072 Heimdal Telefax/Voice mail: +47 904 10 648 > Norway EMail: suppressed > World Wide Web: http://home.online.no/~varlien/ > ---------------------------------------------------------------------------- > > > ----- Original Message ----- > From: "tomasz abramowicz" <suppressed> > To: <suppressed> > Sent: Monday, June 05, 2006 2:32 PM > Subject: Re: [Bigsister-general] Strange SSH check failure on Debian Sarge > > >> that works for me as well. >> >> however, i was taking a look at the "new-style checks" >> which i presume are the more reliable or "correctly made" checks >> [ http://www.joerg.cc/html/bigsis/rn02re32.html ] >> >> >> where the first line states: >> >> ssh — Monitor SSH service. Shortcut for: service=ssh tcp >> >> which also gives me a pretty little column for itself instead of falling >> under "procs" >> and lots of other nifty things.. >> >> >> t. >> >> Software Forums wrote: >>> I run Fedora Core 3 and the line that works for me is: >>> >>> localhost proc=sshd procs >>> >>> Costa >>> >>> -----Original Message----- >>> From: suppressed >>> [mailto:suppressed Behalf Of >>> tomasz abramowicz >>> Sent: 05 June 2006 14:14 >>> To: Paul Lathrop >>> Cc: suppressed >>> Subject: Re: [Bigsister-general] Strange SSH check failure on Debian >>> Sarge >>> >>> >>> i got the same problem, >>> in the same enviorment. >>> >>> can anyone point me in the right direction? >>> >>> thanks, >>> t. >>> >>> Paul Lathrop wrote: >>>> Hi all, >>>> >>>> I am rolling out a test deployment of Big Sister, and I've run into a >>>> perplexing problem. For some reason, the ssh check is red on one of my >>>> servers. the definition for the check in uxmon-net is: >>>> >>>> localhost ssh >>>> >>>> which works on 11 other systems. However, on this system I get a >>>> failure. The text of the failure is: >>>> >>>> ssh CONNECT FAILED (-1s) >>>> >>>> I know ssh is working because that is how I log into the server. Can >>>> anyone point me in the right direction? >>>> >>>> Thanks, >>>> Paul _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.