ZoneMinder Forums

Thanks Both... reading around, I found a thread stating that there are three clocks that need to be in sync.. the main system clock, a PHP clock and SQL clock, so in order to check them I started with the PHP clock. (thread: https://forums.zoneminder.com/viewtopic.php?p=130331#p130331 ) I cobbled ...

Here are some capture examples, Type 1 please look at the images in the capture - one from daytime, 14:00, then a few from midnight. Screenshot 2024-09-14 at 00-13-45 ZM - Frames - 1787227.png The time delta is interesting, as it shows ~10 hours between the daylight image and the row of night time ...

Well, ZM captures seem to be slowly sorting themselves out now I ave some space in the HDD.... I now have captures listed in the last hour! The images are still really odd, I'll write a separate post in a couple of days once I understand what it is and isn't doing. Still need to reduce the size of ...

Ok,

$ sudo service zoneminder stop
$ sudo service zoneminder start

seems to have made ZM pay attention to the log level settings I just chanegd.

But still my SQL database is massive and needs deleting and starting afresh.

So, I set all logging to "none", and still my Ubuntu Sysylog file is outputting lots of ZM info: Sep 13 13:58:32 hal zmc_m6[2220]: INF [zmc_m6] [Cars: 804600 - Capturing at 16.05 fps, capturing bandwidth 145914bytes/sec Analysing at 16.05 fps] Sep 13 13:58:34 hal zmc_m1[2207]: INF [zmc_m1] [Garage ...

Getting a lot of ZM errors in syslog, turns out it was ZM making my syslog files so big too, on top of the size of SQL database: Example: $ tail -f /var/log/syslog Sep 13 13:47:18 hal zmfilter_2[21476]: WAR [DiskSpace: Event does not exist at /mnt/cctv/4/2024-09-11/1770075:ZoneMinder::Event ...

Hi all, My Ubuntu server stopped working as the HDD filled up. In fixing this I found that a main offender was Zoneminder's SQL file at: /var/lib/mysql/zm , but also the syslogs were huge. /var/lib/mysql$ sudo du 45249176 ./zm 4016 ./mysql 600 ./sys 8 ./performance_schema Please can someone help me ...

Thanks, I ran the audit. In the results there were quite a few lines like these, path not found, and no end time: 7 Notes => Motion: All Orientation => ROTATE_270 SaveJPEGs => 3 Scheme => Medium StartDateTime => 2024-09-04 23:06:01 StateId => 1 StorageId => 2 Width => 1080] 09/06/24 11:35:59.802367 ...

Ah thanks for that, it gave me a clue: $ sudo zmaudit.pl 09/06/24 11:15:47.552534 zmaudit[646954].INF [main:199] [Auditing All Storage Areas] DBD::mysql::st execute failed: The table 'Logs' is full at /usr/share/perl5/ZoneMinder/Logger.pm line 627. 09/06/24 11:15:47.553761 zmaudit[646954].ERR ...

Can anyone suggest a way to reset the captures database and delete the old images?

Or any other ideas please?

Today's update... Now when from the console, I click into hourly/daily/weekly captures, I get this error, or slight variations of it: zm-error1.jpg As text: SQL-ERR '00000 ', statement was 'SELECT E.*, M.Name AS Monitor FROM `Events` AS E INNER JOIN Monitors AS M ON E.MonitorId = M.Id WHERE ( E ...

I just did sudo service zoneminder stop and the load really dropped, compare htop to the previous screenshot: Screenshot from 2024-09-03 17-16-02.png Will keep on poking around until any good ideas come up. I want to get this working well ASAP base on our neighbour being robbed the other day. Thanks ...

I've tried to look at the ZM Log, but just get:

Loading, please wait...

Hi all, ZM has been up and running for a few days now. It's giving me some strange captures. Looking at captures in the console, the dates displayed are wrong, the latest date shown is yesterday, for recordings taken today. I've checked the server system date, time zone and time, this is all correct ...

Ah, thanks!

I did find the server system clock was set to UTC, I have set it now to Europe/London...

Thanks for that.

Cheers, Scott