Page 1 of 1
v1.30.12 not purging
Posted: Tue Jan 31, 2017 12:14 pm
by quian
Hi I have been running iconnor ppa 1.30.12 for a few days now and I have noticed my mounted storage drives are full at 100% and new events are now (null) I have purge when full set to 95%
Re: v1.30.12 not purging
Posted: Tue Jan 31, 2017 12:29 pm
by quian
When I run zmaudit
I get the following
atabase event '/storage1/1/17/01/30/19/02/21 monitor:1 event:15474' does not exist in filesystem but too young to delete age: 69348 > MIN 86400.
Database event '/storage1/1/17/01/31/13/05/07 monitor:1 event:59705' does not exist in filesystem but too young to delete age: 4382 > MIN 86400.
Database event '/storage1/1/17/01/31/13/21/21 monitor:1 event:60404' does not exist in filesystem but too young to delete age: 3408 > MIN 86400.
Database event '/storage1/1/17/01/30/23/17/12 monitor:1 event:23513' does not exist in filesystem but too young to delete age: 54057 > MIN 86400.
Database event '/storage1/1/17/01/31/06/26/11 monitor:1 event:42319' does not exist in filesystem but too young to delete age: 28318 > MIN 86400.
Database event '/storage1/1/17/01/30/19/16/33 monitor:1 event:15883' does not exist in filesystem but too young to delete age: 68496 > MIN 86400.
Database event '/storage1/1/17/01/30/20/56/52 monitor:1 event:18709' does not exist in filesystem but too young to delete age: 62477 > MIN 86400.
Database event '/storage1/1/17/01/30/17/53/18 monitor:1 event:13540' does not exist in filesystem but too young to delete age: 73491 > MIN 86400.
Database event '/storage1/1/17/01/31/05/14/27 monitor:1 event:39171' does not exist in filesystem but too young to delete age: 32622 > MIN 86400.
Database event '/storage1/1/17/01/31/11/11/19 monitor:1 event:54765' does not exist in filesystem but too young to delete age: 11210 > MIN 86400.
Database event '/storage1/1/17/01/31/04/45/53 monitor:1 event:37929' does not exist in filesystem but too young to delete age: 34336 > MIN 86400.
Database event '/storage1/1/17/01/30/15/09/17 monitor:1 event:8897' does not exist in filesystem but too young to delete age: 83332 > MIN 86400.
Database event '/storage1/1/17/01/31/00/13/56 monitor:1 event:26023' does not exist in filesystem but too young to delete age: 50653 > MIN 86400.
Database event '/storage1/1/17/01/30/16/53/50 monitor:1 event:11861' does not exist in filesystem but too young to delete age: 77059 > MIN 86400.
Database event '/storage1/1/17/01/31/07/40/10 monitor:1 event:45533' does not exist in filesystem but too young to delete age: 23879 > MIN 86400.
Database event '/storage1/1/17/01/31/06/37/15 monitor:1 event:42817' does not exist in filesystem but too young to delete age: 27654 > MIN 86400.
Database event '/storage1/1/17/01/31/08/01/55 monitor:1 event:46473' does not exist in filesystem but too young to delete age: 22574 > MIN 86400.
Database event '/storage1/1/17/01/31/05/20/00 monitor:1 event:39420' does not exist in filesystem but too young to delete age: 32289 > MIN 86400.
Database event '/storage1/1/17/01/31/02/21/30 monitor:1 event:31604' does not exist in filesystem but too young to delete age: 42999 > MIN 86400.
Database event '/storage1/1/17/01/31/02/14/41 monitor:1 event:31300' does not exist in filesystem but too young to delete age: 43408 > MIN 86400.
Database event '/storage1/1/17/01/30/18/42/58 monitor:1 event:14949' does not exist in filesystem but too young to delete age: 70511 > MIN 86400.
Database event '/storage1/1/17/01/31/11/15/59 monitor:1 event:54970' does not exist in filesystem but too young to delete age: 10930 > MIN 86400.
Database event '/storage1/1/17/01/31/13/54/39 monitor:1 event:61853' does not exist in filesystem but too young to delete age: 1410 > MIN 86400.
Database event '1/7355' does not exist at /storage1/1/17/01/30/14/14/20 in filesystem, deleting
31/01/2017 14:22:11.079056 zmaudit[2560].INF [Deleting event 7355 from Monitor 1 2017-01-30 14:14:20]
Database event '/storage1/1/17/01/31/10/03/53 monitor:1 event:51817' does not exist in filesystem but too young to delete age: 15256 > MIN 86400.
Database event '/storage1/1/17/01/30/20/08/32 monitor:1 event:17333' does not exist in filesystem but too young to delete age: 65377 > MIN 86400.
Database event '/storage1/1/17/01/31/04/44/27 monitor:1 event:37864' does not exist in filesystem but too young to delete age: 34422 > MIN 86400.
Database event '/storage1/1/17/01/30/17/10/59 monitor:1 event:12358' does not exist in filesystem but too young to delete age: 76030 > MIN 86400.
Database event '/storage1/1/17/01/31/07/11/08 monitor:1 event:44290' does not exist in filesystem but too young to delete age: 25621 > MIN 86400.
Database event '/storage1/1/17/01/31/06/19/02 monitor:1 event:41999' does not exist in filesystem but too young to delete age: 28747 > MIN 86400.
Database event '/storage1/1/17/01/31/07/05/20 monitor:1 event:44034' does not exist in filesystem but too young to delete age: 25969 > MIN 86400.
Database event '/storage1/1/17/01/31/05/41/41 monitor:1 event:40387' does not exist in filesystem but too young to delete age: 30988 > MIN 86400.
Database event '/storage1/1/17/01/30/14/49/42 monitor:1 event:8352' does not exist in filesystem but too young to delete age: 84507 > MIN 86400.
Database event '/storage1/1/17/01/30/21/06/18 monitor:1 event:18959' does not exist in filesystem but too young to delete age: 61911 > MIN 86400.
Database event '/storage1/1/17/01/31/07/40/42 monitor:1 event:45557' does not exist in filesystem but too young to delete age: 23847 > MIN 86400.
Database event '/storage1/1/17/01/31/06/11/52 monitor:1 event:41706' does not exist in filesystem but too young to delete age: 29177 > MIN 86400.
Database event '/storage1/1/17/01/31/10/48/00 monitor:1 event:53739' does not exist in filesystem but too young to delete age: 12609 > MIN 86400.
Any ideas?
Re: v1.30.12 not purging
Posted: Tue Jan 31, 2017 10:44 pm
by Matt84
The minimum age can be found in Option > System > AUDIT_MIN_AGE.
86400 is in seconds = 1 Day
so it will not purge any events from today.
Re: v1.30.12 not purging
Posted: Wed Feb 01, 2017 5:31 am
by quian
Hi
Yes it is the default setting which I haven't changed. It looks like the purge filter doesn't work on storage areas ( my separate mounted hard drives) /storage1 (1TB) and /storage1 (1TB) they just full up and zoneminder stops running
Bleeding stuff
Re: v1.30.12 not purging
Posted: Thu Feb 02, 2017 2:02 pm
by quian
Solved and was quite an easy fix.
All I needed to do was create 2 new filters (for each hard drive)
Check screen shots below.
Re: v1.30.12 not purging
Posted: Fri Feb 24, 2017 10:38 am
by ludo_akreed
Hi All,
I have the same issue.
I'm Under centos7 (3.10.0-514.6.1.e17.x86_64) and running Zoneminder v 1.30.0.
I cannot find in the filters 'storage area'
a yum update zoneminder gives me 'No packages marked for update'
So my NAS storage (8To), isn't full used, the filter pugewhenfull clear it when my local disk reach the limits.
Can anyone help me?
Thank you,
Re: v1.30.12 not purging
Posted: Fri Feb 24, 2017 5:59 pm
by iconnor
1.30.0 does not have storageareas. Your issue will be something else.
Re: v1.30.12 not purging
Posted: Mon Feb 27, 2017 2:02 pm
by ludo_akreed
Hi,
It seems I succeed, I comment the line /dev/mapper/cl-root in the file /etc/fstab.
Web interface shows now the amount on my NAS.
BR,