[
https://issues.apache.org/jira/browse/VCL-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510218#comment-16510218
]
Mike Jennings commented on VCL-1082:
------------------------------------
Josh,
I would not patch my comments, they should not have been in there anyway :D.
The timestamp that is being returned is the localtime of the system in
year-mon-day-hour-min-sec. This will be the same as what is returned from the
database using the NOW function. The reason to use the NOW() on the update is
that it will allow the DB to set the time consistently on that field across all
Daylight Savings time. The timestamp being returned is only in the logs
showing when the last checkin time was updated on the management node. I see
no reason in not passing back the localtime of when this happened, as it will
be the same as the database.
> monitor_vcld.pl throws incorrect lastcheckin time exception after Daylight
> Savings Time Roles Back
> --------------------------------------------------------------------------------------------------
>
> Key: VCL-1082
> URL: https://issues.apache.org/jira/browse/VCL-1082
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.5
> Reporter: Mike Jennings
> Priority: Minor
> Labels: patch
> Fix For: 2.5.1
>
> Attachments: monitoring.patch, monitoring.sql
>
>
> When Daylight Savings time rolled back one hour on Nov 5th, the
> monitor_vcld.pl program started reporting critical exceptions where the
> management node has not been checked in, in over a hour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
