Ticket #177 (closed defect: done)
duplicate entry error in unified log
| Reported by: | jdalbey | Owned by: | jdalbey |
|---|---|---|---|
| Priority: | Medium | Milestone: | Sep 2019 Training |
| Component: | Unified Logger | Version: | |
| Severity: | Minor | Keywords: | |
| Cc: |
Description
In the unified log below, note after the error loading json that the CAD log entries are repeated (with a timestamp of 0:00). It's as though the lastLineNum global variable in cad_watcher.py was reset to zero somehow.
0:01:16, CAD log, Incident #206, sam: SEND OUT FOR PIZZA 0:01:31, CAD log, Incident #202, sam: NOW IS THE TIME 0:04:56, CMS Activated.,N I-5 25.82 Yale OC, 'LET'S GO FLY:A KITE.::::' 0:05:46, CAD log, Incident #206, sam: SEND OUT FOR PIZZA 0:05:46, CAD log, Incident #202, sam: NOW IS THE TIME 0:05:46, CAD log, Incident #206, sam: FOR ALL GOOD MEN 0:05:52, CAD log, Incident #202, sam: TO COME TO THE AID OF THEIR COUNTRY. 0:08:27, CMS Deactivated., N I-5 25.82 Yale OC 0:08:52, CAD log, Incident #202, sam: WE SHOVEL SAUSAGE Error loading json for elapsed time 0:00:00, CAD log, Incident #206, sam: SEND OUT FOR PIZZA 0:00:00, CAD log, Incident #202, sam: NOW IS THE TIME 0:00:00, CAD log, Incident #206, sam: FOR ALL GOOD MEN 0:00:00, CAD log, Incident #202, sam: TO COME TO THE AID OF THEIR COUNTRY. 0:00:00, CAD log, Incident #202, sam: WE SHOVEL SAUSAGE 0:37:34, CAD log, Incident #202, sam: NOW IS THE TIME again
So far I've been unable to reproduce this error.
Change History
comment:2 Changed 7 years ago by jdalbey
- Status changed from new to closed
- Resolution set to done
Unable to reproduce, but I'm guessing that it occurs when cad_watcher tries to read the comments log at the exact time CADserver is writing the file. I enhanced cad_watcher with more elaborate error handling to check for missing file and empty file. Assume an empty file is a read sync issue and don't do anything, whereas a missing file means a "reset" and start the log over. Committed in r467.

Here's another example, showing it's not related to json error. It just happened randomly at 13:10 when nothing else was going on.