Maybe i'm missing something obvious, but for some reason, ever since upgrading to 19.1, all events created have 0 frames, 0 score, etc and i am unable to find the cause. see screenshot. as you can see, it was working before the upgrade. should i roll back to 0.18.1?
Karl
<img src="http://www.linuxninja.net/stuff/zm-bug.jpg">
0.18.1 -> 0.19.1: modetect broken?
Re: 0.18.1 -> 0.19.1: record broken?
i should also note that all modes of recording is not working for me. looking in the events dir, seems to be missing quite a few files.
-
zoneminder
- Site Admin
- Posts: 5215
- Joined: Wed Jul 09, 2003 2:07 pm
- Location: Bristol, UK
- Contact:
Re: 0.18.1 -> 0.19.1: modetect broken?
Hi Karl,
Did you remember to update your database between 1.18,1 and 1.19.1? There are changes in the Frames table which is Event details are stored. It is detailed in the README but in essence do something like
<i>mysql zm < db/zmalter-1.18.1.sql</i>
<i>mysql zm < db/zmalter-1.19.0.sql</i>
though you may need to give a username and password etc etc. The version numbers refer to the version you are upgrading from so to go from 1.18.1 to 1.19.1 you would use 1.18.1 and 1.19.0 or however many intermediate versions there were.
Phil,
Did you remember to update your database between 1.18,1 and 1.19.1? There are changes in the Frames table which is Event details are stored. It is detailed in the README but in essence do something like
<i>mysql zm < db/zmalter-1.18.1.sql</i>
<i>mysql zm < db/zmalter-1.19.0.sql</i>
though you may need to give a username and password etc etc. The version numbers refer to the version you are upgrading from so to go from 1.18.1 to 1.19.1 you would use 1.18.1 and 1.19.0 or however many intermediate versions there were.
Phil,
Re: 0.18.1 -> 0.19.1: modetect broken?
I had pretty much the same issue, except mine was constantly in "alarm" state.
Sometime last week, everything stopped working, and I wasn't sure why, so I upgraded to 1.19.1 just for the hell of it. Eventually I found my /dev/video devices were gone (not sure why), so I had to mknod them back. I had the exact same problem described here, and noticed I forgot to do the database upgrades.
After doing the upgrades, I still had the same problem, though it only generated one event. It said "alarm" constantly, even when there is no movement or change. I messed around with the zone settings quite a bit, and eventually created a new source, and copied its zone defaults.. after that, it worked fine. The values I had where mostly 0 for everything, while the new defaults have actual values. I'm not sure if this is an upgrade issue or something else? But something to be aware of, anyways.
Sometime last week, everything stopped working, and I wasn't sure why, so I upgraded to 1.19.1 just for the hell of it. Eventually I found my /dev/video devices were gone (not sure why), so I had to mknod them back. I had the exact same problem described here, and noticed I forgot to do the database upgrades.
After doing the upgrades, I still had the same problem, though it only generated one event. It said "alarm" constantly, even when there is no movement or change. I messed around with the zone settings quite a bit, and eventually created a new source, and copied its zone defaults.. after that, it worked fine. The values I had where mostly 0 for everything, while the new defaults have actual values. I'm not sure if this is an upgrade issue or something else? But something to be aware of, anyways.
Re: 0.18.1 -> 0.19.1: modetect broken?
bah! i knew it was something obvious i missed. :)
thanks Phil!
Karl
thanks Phil!
Karl