Bug #373
Not monitoring host using one_im_sh
| Status: | Closed | Start date: | 10/23/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | - | |||
| Target version: | Release 2.0.1 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
Problem:
I had a problem with one_im_sh (located in $ONE_LOCATION/lib/mads) because it was not monitoring the host, after some debugging I found that it was freezing each time oned was trying to execute the monitoring action.
Solve:
I was able to find that the problem of this error was that in line 68 of the file one_im_sh.rb it is this:
[...] monitor_exe = LocalCommand.run(cmd_string, host, log_method(id)) [...]
so I just modified this line with this:
[...] monitor_exe = LocalCommand.run(cmd_string, log_lambda) [...]
Erasing the host parameter and giving for the log_lambda, because the other was also giving a warning for a deprecated method.
Associated revisions
bug #373: Fix bad LocalCommand.run call
bug #373: Fix bad LocalCommand.run call
(cherry picked from commit 0b42b5efe898d73e313ff1e1dca7232607600986)
History
#1
Updated by Ruben S. Montero over 10 years ago
- Target version set to Release 2.0.1
#2
Updated by Tino Vázquez over 10 years ago
- Status changed from New to 3
- Assignee set to Tino Vázquez
- % Done changed from 0 to 100
- Resolution set to fixed
This has been fixed in the one-2.0 branch, and will be included in the upcoming 2.0.1 release.
Thanks Enrique for the feedback.
#3
Updated by Ruben S. Montero almost 10 years ago
- Status changed from 3 to Closed