tftp monitor 🔗 link

Couldn't quickly find a FAQ on this, didn't see anything on deadcat.net
either... I to monitor whether a TFTP server on the internal net here is
up and running. What do I need to do to make this happen?

 
Thomas

Did anyone answer this? I just got the same request and had no luck
finding an answer.
Thanks 
Ken Cooper

-----Original Message-----
From: Thomas Leavitt [mailto:user-9b8a669cb525@xymon.invalid] 
Sent: Monday, August 18, 2008 7:44 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] tftp monitor

Couldn't quickly find a FAQ on this, didn't see anything on deadcat.net
either... I to monitor whether a TFTP server on the internal net here is
up and running. What do I need to do to make this happen?

 
Thomas

02/26/09 07:03:00

Cooper, Ken wrote:

Hobbit cannot check UDP services.
See following discussions for more details:

http://www.hswn.dk/hobbiton/2007/05/msg00035.html
http://www.hswn.dk/hobbiton/2005/11/msg00338.html
http://www.hswn.dk/hobbiton/2008/02/msg00313.html

Dominique

You can write a script that downloads somethin via tftp, then set the
alerts on if the file exists or not locally.

On 2/27/09, Dominique Frise <user-78ab6673b600@xymon.invalid> wrote:

-- 

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer

I cannot find anything mentioning if Hobbit/Xymon can test how long an  HTTP or HTTPS page takes to respond and alert on that.  In other  words, if a site is in a hung state so that it still technically  "responds" but it takes 5 seconds for the page to respond how does  Hobbit/Xymon handle that?  I want to make sure that if a site that we  are monitoring takes longer than a couple of seconds to load we are  alerted,

Do any of you do a test like that and how are you doing it?

Thanks,
Jason

I was doing pretty much exactly that for my recently-ex employer.

There's a tool called 'curl' which is very good at getting web pages.  You
would do something like this in bash:

     curl -s -S -L --max-time 5 -o /tmp/page.html http://server.domain.com/
     if [ $? -ne 0 ]; then
        # something went wrong.  the return code tells the actual error
        COLOR=red
        MESSAGE="page fetch failed.  curl error $?"
     else
        COLOR=green
        MESSAGE="page fetch successful"
     fi

then use server/bin/bb to send the report to the server.  I generally saved
the html somewhere in the web server's document tree, then added a link to
the report so that Midrange Operations could click through and see the
actual page the server returned.

Curl can also tell you how long the transaction took, which you could add to
the report in a format that xymon could pick up for graphing.

Ralph Mitchell

On Fri, Feb 27, 2009 at 10:14 AM, Jason Hand <user-17f7af22f408@xymon.invalid> wrote:

----- "Dominique Frise" <user-78ab6673b600@xymon.invalid> wrote:

[...]

Hobbit cannot check UDP services.

The more correct answer is that Xymon's generic network testing features supports TCP. UDP cannot be tested generically, being connectionless.

However, Hobbit does monitor NTP (but this is done by using an NTP client).

I monitor RADIUS using an extension script (I think the one from The Shire, but I had to remove the Solaris-isms).

A similar approach can be taken for TFTP, e.g. using a tftp client to fetch a known file, and testing the return code.

We have TFTP in our environment, but I would be worried if someone really required it to be monitored (as the functionality often implemented requiring a reliable TFTP service can often be done with better tools ...).

However, if you don't come right, I may decide to implement a check myself and share it.

Regards,
Buchan

----- "Jason Hand" <user-17f7af22f408@xymon.invalid> wrote:

As far as I remember, the default http test (assuming you have provided the full url to the site you want to test) will go red if the server doesn't respond with an appropriate status code within the timeout (which defaults to 10s).

If you need custom timeouts for different hosts, then you may need something more complex than that (although you should consult the documentation, see the coverage of the --timeout option in the bbtest-net man page).

Regards,
Buchan