On Fri, Sep 27, 2019 at 1:42 AM Radosław Korzeniewski < rados...@korzeniewski.net> wrote:
> Hello, > > czw., 26 wrz 2019 o 18:57 David Brodbeck <brodb...@math.ucsb.edu> > napisał(a): > >> I deliberately have this set up because I want to know if the director >> crashes. Does mean I have to put up with one of those messages every ten >> minutes though. ;) >> > > To check if a Director is working you should just use a proper probe. > Checking if any service is running by spraying around random bits is > insane, IMHO. When you check if HTTP server is working you just perform a > proper HTTP GET request and expect a 200 response, right? > It doesn't actually spray random bits, just checks to see if it can connect to the TCP port, then immediately disconnects. It's a basic check to see if the director process has crashed or locked up. I set this up because it used to do that pretty regularly, but fortunately the more recent versions have been pretty stable. I was actually a little surprised that bacula considers it an error (as opposed to, say, a debug-level message) when a connection is made without sending any commands; most other daemons I'm familiar with ignore that sort of thing. BTW, regardless of what I do the central IT department here runs vulnerability scans on my subnet every so often, so this is going to happen from time to time anyway. HTTP is a little different because it's an open protocol. Bacula's protocol is proprietary and AFAIK not intended for random "unofficial" clients to connect to, so writing a more "correct" test would be tricky. I guess I could write some kind of script with bconsole, but that's heavier and has its own pitfalls. -- David Brodbeck System Administrator, Department of Mathematics University of California, Santa Barbara
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
