12-31-1969 19:00:00 Dates??

jondecker76 · Post by **jondecker76** » Mon Oct 04, 2010 4:15 am

Every now and then i get an event (caused by a lost/reacquired signal) that has a date of 12/31/1969.

What can I do to fix the date of these signals?

Post by **knight-of-ni** » Mon Oct 04, 2010 8:45 pm

I simply wrote a filter that deletes these automatically.

1of2 · Post by **1of2** » Tue Oct 05, 2010 1:14 am

Is your camera on a different machine ?

I had the same problem but it was showing 1970, so I assume it was a bug in the timing calculations within ZM.

After moving the camera to a local machine it was always correct.

jondecker76 · Post by **jondecker76** » Tue Oct 05, 2010 1:23 am

all I use are IP cameras, so the local/remote machine question really doesn't apply.

I'm still trying to find a way to consistently reproduce it

Post by **knight-of-ni** » Tue Oct 05, 2010 1:58 pm

Back when I initially installed 1.24.2, I noticed that on a daily basis I would get events in my database with absurd values... a date of 1969 with a length of something like 1 million seconds. This would completely hose up the timeline as it would be solid red.

Two of my IP cameras are indoors, which I turn off when I come home from work (I like to keep an eye on my dogs when I am away

). I noticed that the likelihood of getting one of these erroneous events would increase when my camera was off or otherwise experiencing a communications problem.

My hunch is that this issue only happens with recording devices that are not attached locally to the zonemidner machine, but this is simply a guess.

To work around this I opened up the Filters window and created a filter that would delete any event which had a duration longer than 6000 seconds (arbitrary) and (just in case) had a duration of less than zero. I have not had one of these events since then.

Fast forward ~1 year to today. I am running the latest copy of Zoneminder found in the SVN repository and have noticed that a lot of the issues with 1.24.2 have been resolved (the forward/reverse buttons now work correctly, yea!). Has the issue with the erroneous events been resolved? I don't know as I have left the filter in there as it is not hurting anything, but for the more adventurous it may be worth a shot to compile the latest build and see if it works better for you.