@@ -65,3 +65,7 @@ Fix the cause of the mount error and the node should mark itself as elegible aga
...
@@ -65,3 +65,7 @@ Fix the cause of the mount error and the node should mark itself as elegible aga
These probes are configured in [monit-remote-probes](https://gitlab.cern.ch/monitoring/monit-remote-probes/-/blob/master/linuxsoft/probes.yaml),
These probes are configured in [monit-remote-probes](https://gitlab.cern.ch/monitoring/monit-remote-probes/-/blob/master/linuxsoft/probes.yaml),
they were created in [LOS-904](https://its.cern.ch/jira/browse/LOS-904). The [dashboard](https://monit-grafana.cern.ch/d/w57luRvnz/remote-probes-overview?orgId=1&var-producer=linuxsoft&var-module=All&var-instance=All) will show you the current status.
they were created in [LOS-904](https://its.cern.ch/jira/browse/LOS-904). The [dashboard](https://monit-grafana.cern.ch/d/w57luRvnz/remote-probes-overview?orgId=1&var-producer=linuxsoft&var-module=All&var-instance=All) will show you the current status.
At the moment (Apr. 2022) there's no good way to get logs of failures to help with the debugging. You can find logs of the
most recent probes at http://monit-remote.cern.ch/blackbox, but they're not kept around for long. Another thing you can do
is manually trigger a probe by visiting http://monit-remote.cern.ch/blackbox/probe?module=linuxsoft/http_ipv4_koji&target=http%3A%2F%2Fkoji22.cern.ch&debug=true. You can change the module and target parameters of that URL to trigger different probes.
These magical URLs were given to us by Borja Garrido and they may stop working at any time as they're not an "official" service interface.
