5.2.1. JournalNode process

This host-level alert is triggered if the individual JournalNode process cannot be established to be up and listening on the network for the configured critical threshold, given in seconds. It uses the Nagios check_tcp plug-in. Potential causes
  • The JournalNode process is down or not responding.

  • The JournalNode is not down but is not listening to the correct network port/address.

  • The Nagios server cannot connect to the JournalNode. Possible remedies
  • Check if the JournalNode process is dead.

  • Use ping to check the network connection between the Nagios server and the JournalNode host.

loading table of contents...