On Fri, 7 Dec 2007, Osburn, Michael wrote: > Thanks for the patch. Not sure what caused the issue but when I > replaced the mon executable with the one from 1.2.0 (patch applied) > I started getting alerts upon reload. I have seen about 5 errors show > up in the logs stating
> Dec 7 13:03:23 localhost mon[13490]: no monitor found while trying > to run [http.monitor] Yes, this means it didn't find http.monitor in either the default place or the place where you told it to look. If you start mon like "./mon -d -c /path/to/mon.cf" it will dump out the list of places it's looking. The directory you're looking for is labeled "mondir" in the config file, and usually it's something like "/usr/lib/mon/mon.d". In the "-d" debug output it is incorrectly labeled "scriptdir" (which I just noticed). You can either just copy your http.monitor into the place it's looking, or better yet, just make the "mondir" path point to the "mon.d" directory that comes with mon. When mon starts up or is told to reload its configuration, it looks for every "monitor" and "alert" in your config in the "mondir" and "alertdir" paths, respectively. You can specify multiple directories separated by a colon, like "mondir = /usr/local/mystuff/mon.d:/usr/lib/mon", and you'd put your own homebrew or site-specific monitors in "/usr/local/mystuff/mon.d", where it will look first before looking in the other location. _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
