Viewing results

There are several ways to retrieve the output of the checks


  • Resmon can be reloaded by sending a HUP signal to the running process. Resmon runs as two processes (the second is for the web server), and only the parent process will respond to the HUP signal. Reloading can be done as follows:
    • Linux
      • /etc/init.d/resmon reload
      • killall -HUP resmon (if you are not using an init script)
    • Solaris
      • svcadm refresh resmon
    • OpenBSD
      • pkill -HUP -f resmon
  • Resmon will try to recover in the event of an error while reloading:
    • If there are errors in the configuration file, resmon will continue to use the old configuration
    • If there is a problem reloading a specific module, resmon will disable that module and continue running with the rest
    • Any error will show up in the RESMON module, which will go bad and show more details on the error.

Hooking into other systems

In addition to looking at the output manually, resmon can work with other monitoring systems:

  • Nagios
    • check_resmon_xml_part
      • located in the resmon scripts/ dir
      • Sample configuration is in the script itself
  • Reconnoiter
    • Reconnoiter has built in support for monitoring resmon
  • Circonus
    • Circonus has built in support for monitoring resmon

Auto Update script

This is currently in development and there are likely still problems with this feature

  • /opt/resmon/resmon -u
  • Updates from svn (svn up, no url specified)
  • Reloads resmon
    • If a module fails to load (or there's a config file problem), the RESMON check goes bad and the script rolls back to the revision previously checked out.
    • This requires that the RESMON check be used in the config file to work