Cisco Bug: CSCvt08641 - Timezone reconfiguration may stop poller jobs from rescheduling and fail login with "negative time"
Jun 26, 2020
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: Prime Infrastructure's poller jobs may stop, which will affect the monitoring of devices managed by Prime Infrastructure, causing symptoms like dashlets of monitoring policies showing no data after 22:59, until the NCS services are stopped and restarted. System Jobs seem to not be affected by this issue. If the user changes the timezone to GMT or UTC, this issue does not occur. Conditions: This issue was observed under this scenario: 1. Install an instance of Prime Infrastructure 3.7 2. Go to the Prime Infrastructure CLI and enter these commands: conf t clock timezone Europe/Dublin exit wr mem 3. Restart NCS ncs stop ncs start 4. The timezone will be changed, wait until the time reaches 22:59 that day. 5. All poller jobs will stop at that time; the next start date will be shown as 22:59 in all jobs. Monitoring and other functions will be severely affected, and collecting information from devices may stop from that time until Prime Infrastructure restarts. If a login to Prime Infrastructure's web GUI happens shortly after 22:59, the user may see the following message in a blank screen in the browser: "message":" Assertion botch: negative time" After this, the user willl need to refresh the page until they can login in to Prime Infrastructure's web GUI.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases