Feature #3988
when the remote probes are not successfully executed, there is no information in oned.log
| Status: | Closed | Start date: | 09/16/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% | ||
| Category: | Drivers - Monitor | |||
| Target version: | Release 4.14 | |||
| Resolution: | Pull request: |
Description
The problem is that we execute the probes with
data = `#{@run_probes_cmd}`
We are therefore losing the STDERR
Associated revisions
Feature #3988: when the remote probes are not successfully executed, there is no information in oned.log
History
#1
Updated by Jaime Melis almost 6 years ago
- Status changed from Pending to Closed