monitor windows remote desktop from linux

[Massimo Balestra]

Yes probably I found the solution.

I can run rdesktop with the option -s to run a batch that runs "shutdown
/l".

I have to set the rdesktop in order to use xvfb as xwindows server.

I can set a timeout in the command so I kill rdesktop if it does not answer
after ... 1 minute and let nagios raise an alarm.

It is a little complicated but it could work.

I have something to begin to write my custom plugin.

I will let you know and I will post the (perl) plugin if it works

Thank you to everybody.

Massimo

-----Original Message-----
From: Massimo Balestra [mailto:massimobalestra at hotmail.com] 
Sent: Tuesday, July 07, 2009 10:42 AM
To: 'John Andrunas'
Cc: 'Frost, Mark {PBG}'; nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] monitor windows remote desktop from linux


Thank you John,

I thought that, but rdesktop needs an xwindows server and, also, I did not
find any command in rdesktop that make a conencion and exits immediately.

Do you know how I could do this?

Thank you
Massimo


-----Original Message-----
From: John Andrunas [mailto:john at andrunas.net] 
Sent: Tuesday, July 07, 2009 10:28 AM
To: Massimo Balestra
Cc: Frost, Mark {PBG}; Natxo Asenjo; nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] monitor windows remote desktop from linux

It seems like you ought to be able to create a check that actually
connects to rdp, not that this is an ideal solution.

rdesktop -u <username> -d <domain> -p <password>



On Tue, Jul 7, 2009 at 10:10 AM, Massimo
Balestra<massimobalestra at hotmail.com> wrote:
> Thank you Mark.
>
> Unfortunately nothing is written in the event log that can help. The only
> error I see is about printer drivers but there are a lot of them and they
> normally does not affect the server behavior.
>
> I was hoping somebody would know better than me the RD protocol in order
to
> send some commands to the port (I have no problem to make my own nagios
> plugin) to monitor if it is working or not.
>
> Thank you again.
> Massimo
>
> -----Original Message-----
> From: Frost, Mark {PBG} [mailto:mark.frost1 at pepsi.com]
> Sent: Tuesday, July 07, 2009 10:05 AM
> To: Massimo Balestra; Natxo Asenjo; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] monitor windows remote desktop from linux
>
>
>
>>-----Original Message-----
>>From: Massimo Balestra [mailto:massimobalestra at hotmail.com]
>>Sent: Tuesday, July 07, 2009 12:52 PM
>>To: 'Natxo Asenjo'; nagios-users at lists.sourceforge.net
>>Subject: [Nagios-users] monitor windows remote desktop from linux
>>
>>Hi,
>>
>>I did some googleing for this problem but with no success. Maybe
>>somebody in
>>this list can help me to figure how to do this check.
>>
>>My nagios is running on linux and I have two windows servers used for
>>remote
>>desktop (terminal service).
>>
>>One of this servers has some problems (we will reinstall it) and
>>sometimes
>>the remote desktop stops answering and the nobody can login. To tell
> the
>>truth the whole server hangs but in this moment my concern is the
> remote
>>desktop.
>>
>>I already setup a check on the remote desktop port (using check_tcp)
> but
>>it
>>is not enough. The RD port answers to the socket connection but when I
>>try
>>to connect with the client it hangs. So the port is open but the
> service
>>is
>>frozen.
>>
>>Is there anybody who knows what to do to monitor the Windows Remote
>>Desktop?
>>
>>
>>Thank you in advance
>>Massimo
>
> Massimo,
>
> I guess if the port is still listening it wouldn't solve the issue to
> monitor the Windows service the provides Remote Desktop (although that
> seems like it would be a good idea anyway).
>
> Any chance there's a corresponding message in the Windows Event log
> indicating something bad happening with Remote Desktop?  If so, you
> could use one of several utilities (of which NSClient++ is one) to
> trigger an alert when it sees that event in the Event Log.
>
> Mark
>
>
>
----------------------------------------------------------------------------
--
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full
prize
> details at: http://p.sf.net/sfu/blackberry
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>



-- 
John


----------------------------------------------------------------------------
--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have 
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Nagios-users mailing list
Nagios-users at 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


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have 
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Nagios-users mailing list
Nagios-users at 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