Maximum number of events ?

Rorohiko · Post by **Rorohiko** » Mon Aug 01, 2005 4:16 am

Hi all.
I have 5 cameras dumping onto a 160Gb HD. 1 Particular camera reached 31999 events and is now choking.
Symptoms are....
Source drops to yellow from green.
Event list, events are usually stamped e.g Event-149110. New events for this camera are now named "New Event" and usually have a duration of 0.00 with a frames and Alarm Frames being blank.

The other four cameras are working fine.
I did an --auto-repair on my database incase that was it.
There is still a good 25gb of HD left so I don't think its a space issue.

Was wondering if I reached a numerical limit e.g. the 32768 number is not far away.

The box is FC3 running zm 1.21.3

From messages

Jul 30 14:40:31 Security-1 zma_m2[4673]: INF [Camera_2: 850 - Gone into alarm state]
Jul 30 14:40:31 Security-1 zma_m2[4673]: ERR [Can't make events/2/149144: Too many links]
Jul 30 14:40:31 Security-1 zma_m2[4673]: ERR [Can't open events/2/149144/001-capture.jpg: No such file or directory]
Jul 30 14:40:31 Security-1 zma_m2[4729]: INF [Debug Level = 0, Debug Log = <none>]
Jul 30 14:40:31 Security-1 zma_m2[4729]: INF [Warming up]

I'm a bit new on Linux so go easy on me please .

Any help is much appreciated.

regards.

Marc

Post by **cordel** » Mon Aug 01, 2005 5:35 am

A few questions just to figure out how this happened.
Is the 1.21.3 a fresh install or upgraded?
Are you using source or RPM?
If you are using the RPM try to export from one of the camera's and see if it clears up.
If it don't clear up I'll need more info so that I can correct it.

What you have sounds like a link is pointed to a link that inturn is points back to the first link (a link loop if you will). I have included a bit of code inthe latest RPM that checks and corrects some of the links and this occures only on exporting events though.

If you trace the path for the events for that camera you should find that there is a link loop type case and if you get it corrected it will solve your problem.
Regards,
Cordel

Post by **zoneminder** » Mon Aug 01, 2005 4:52 pm

I suspect this may be that you have reached the maximum number of inodes allowed per directory in your filesystem. This is configurable when you build the filesystem but I don't know if you can use tune2fs after the fact to allow for more, smaller, files.

32k events is a lot, are they motion based or time based?

Phil

Rorohiko · Post by **Rorohiko** » Tue Aug 02, 2005 8:45 am

Hi Phil & Cordel

The 1.21.3 was an upgrade from 21.2 using source.
This trouble being 1 reason for the upgrade.

Events are all motion based, not time.
I have 2 other cameras both on the verge of 32k events and am watching closly.

I run a Theatre, Theater for you Mr Cordel.
This particular camera monitors offstage/onstage access while covering me, the venue technicians office. Its a very busy area and yes for the vouyers things do happen.
The inventor of the Tutu deserves a place in heaven.......((yum) is not only an updater)

Have I hit a brick wall with the inodes number ?
Thanks for the the tune2fs tip. I need some time to look further on this.

In the meantime can you sugest a filter thats not too radical in its approach ?

Best regards from New Zealand.
Marc

Post by **zoneminder** » Tue Aug 02, 2005 2:34 pm

What do you want to filter on, time or type/size of event?

Phil

hrabe · Post by **hrabe** » Thu Aug 04, 2005 1:08 pm

32k files is limit for the ext2(3) filesystems. The better is use xfs filesystem for events. I have more than 65k events per camera without problem.
Martin

Post by **cordel** » Thu Aug 04, 2005 3:45 pm

Rorohiko, Just wondering if you got this sorted out.
Regards,
Cordel