Closed lucasnz closed 3 years ago
I've fixed the error while printing the error message (missing }
). However the core issue may be that your detection state is corrupted for some reason. If the error persists, try deleting /var/lib/zmeventnotification/images/*.pkl
and see if they get recreated properly.
deleting the pkl files seems to have resolved the issue. I wonder what might have caused the corruption?
Let me know if it happens often. I have a theory its because I release the exclusive locks just after detection happens and its possible that when multiple detections happen, file writes interleave.
Before you create an issue, please make sure you have read the README. If you are asking about the object detection part, I don't provide support for it unless you've tried hard enough.
Event Server version
You can get the version by doing:
6.1.25
Hooks version (if you are using Object Detection)
You can get the version by doing:
app:6.1.25, pyzm:0.3.49
Are you using MLAPI? (Y/N) No
If you are using MLAPI, please mention the version You can get the version by doing: (change path to wherever you install mlapi)
The version of ZoneMinder you are using: 1.36.4
What is the nature of your issue
match_past_detections=yes results in zmdetect.py throwing an error
Details
match_past_detections=yes results in zmdetect.py throwing an error.
Changing, match_past_detections=no works around the issue.
When the error occurs notifications are not sent. I think this occurred after a python update or maybe an ES update - I'm not 100% sure which one.
Debug Logs (if applicable)
Important: Please post DEBUG logs NOT INF logs. Instructions on how to enable debug logs are posted HERE
Thanks!