Reporting CGIs incorrectly calculate start or end time for periods spanning changes to daylight time
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Nagios |
Fix Released
|
Unknown
|
|||
| nagios3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: nagios3
I've discovered a Daylight Savings Time bug within the avail, histogram, summary and trends CGIs.
To reproduce, run a custom report timeperiod for a duration which spans migration into or out of DST. As an example using NZST either 1st Apr to 30th Apr or 1st Sep to 30th Sep. Note the start and end time, either the start or end time will be an hour out from what one would expect.
Please see the attached patch to fix. The problem arises from using the generated tm_isdst flag from calling localtime(
This bug is present in intrepid, jaunty and will be present in karmic too. It is also present the latest stable upstream (3.1.2). I've seperately raised this issue on the nagios-devel mailing list.
Related branches
| Mark Goldfinch (4-launchpad-g-org-nz) wrote | #1 |
| Chuck Short (zulcss) wrote | #2 |
| Changed in nagios3 (Ubuntu): | |
| status: | New → Triaged |
| Chuck Short (zulcss) wrote | #3 |
| Changed in nagios: | |
| status: | Unknown → New |
| Changed in nagios: | |
| status: | New → Fix Released |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in nagios3 (Ubuntu): | |
| status: | Triaged → Fix Released |
Thanks for the bug report I have reported the issue in the nagios bug tracker. We will see what they have to say.
Regards
chuck