Skip to content

When using CMD poller, Failure and Recovery dates may have incorrect values #5727

@xmacan

Description

@xmacan

If cmd poller is used, status_rec_date and staus_fail_date are around 1970-01-01 (@bmfmancini has 1969, I guess it is timezone/summer time).

New device, snmp works well, device is online:
+---------------------+---------------------+--------------------------------+--------+--------------------+------------------------+ | status_fail_date | status_rec_date | status_last_error | status | status_event_count | snmp_sysUpTimeInstance | +---------------------+---------------------+--------------------------------+--------+--------------------+------------------------+ | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | | 0 | 0 | 0 |

I change snmp port to simulate down state:
| 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | Device did not respond to SNMP | 3 | 1 | 2271887200 |

after few minutes:
| 1970-01-01 01:33:44 | 0000-00-00 00:00:00 | Device did not respond to SNMP | 1 | 1 | 2271887200 |

after recovering:
| 1970-01-01 01:32:50 | 2024-04-14 18:50:00 | Device did not respond to SNMP | 3 | 0 | 2271923200 |

after next poller cycle:
| 1970-01-01 01:32:50 | 1970-01-01 01:33:44 | Device did not respond to SNMP | 3 | 0 | 2271929200 |

@bmfmancini confirmed it. With spine works fine

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUndesired behaviourconfirmedBug is confirm by dev teamresolvedA fixed issue

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions