You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/30 21:13:00 UTC

[jira] [Commented] (VCL-1082) monitor_vcld.pl throws incorrect lastcheckin time exception after Daylight Savings Time Roles Back

    [ https://issues.apache.org/jira/browse/VCL-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756557#comment-16756557 ] 

ASF subversion and git services commented on VCL-1082:
------------------------------------------------------

Commit c212dfd9c30b906e7b61afadce8c9e13639a2d66 in vcl's branch refs/heads/develop from Josh Thompson
[ https://gitbox.apache.org/repos/asf?p=vcl.git;h=c212dfd ]

VCL-1082 - monitor_vcld.pl throws incorrect lastcheckin time exception after Daylight Savings Time Roles Back

vcl.sql: changed definition of managementnode.lastcheckin from datetime to timestamp

update-vcl.sql: added alter table statement to change managementnode.lastcheckin from datetime to timestamp


> 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)