Ive just done a clean install of 1.19.5. I did have a previous version 1.19.4 installed but i subsequently deleted both the user and db from that version. Zoneminder appears to start up and start capturing correctly, and i can even watch a stream from the camera's. When it detects motion and tries to record it i get this error message:
Nov 19 18:50:13 cctv zma-m1[2932]: ERR [Can't insert frames: You have an error in your SQL syntax near '' at line 1]
and doesnt record any images onto disk.
Ive done a quick forum search and havnt come across the same error, any idea whats going on?
1.19.5 mysql problems
As an update, i went back to using 1.19.4 for a while, but the option to only trigger on x number of frames is something I really need. I followed exactly the same install procedure, and no install errors were displayed. Everything works fine until zma goes into an alarmed state, then the above sql error comes up. A record of an event is listed on the web front end, but viewing it shows no frames have been recorded. I have no idea about mysql and how it works, do I need to edit some file to get this to work?
Running on Fedora Core 2
Running on Fedora Core 2
-
zoneminder
- Site Admin
- Posts: 5215
- Joined: Wed Jul 09, 2003 2:07 pm
- Location: Bristol, UK
- Contact:
ok these are the steps I used to proceed.
./configure --etc (no errors)
perl zmconfig.pl (completed without problems)
mysql ... (mysql setup appeared to go without problems)
perl zmconfig.pl -noi (completed without problems)
make (no errors)
make install (no errors)
web interface now works, showing correct version etc.
Did 'add monitor', used the following settings:
Monitor
Name: Drive
Function: Modect
Section length: 600
Frame Skip: 0
Run mode: Continuous
Trigger: n/a
Source type: local
Source
Device number: 0
Device channel: 0
Device format: 0
capture palette: rgb24
capture width: 352
capture height: 288
orientation: normal
Timestamp
all default
Buffers
Image buffer size: 500
Warmup frames: 100
Pre event image buffer: 250
Post event image buffer: 250
Alarm frame count: 2
Misc
Event prefix: Drive
Max fps: 25
ftp report interval: 1000
reference image blend: 10
--
I also added another 2 monitors, with the same settings. Everything goes green in the web interface to indicate everything is working.
A few informational screenshots.
Apparently working console
everything looks fine here.
Monitor window
This is what happens when an alarm is triggered and zm tries to record the event to the db
Server logging
This is a snapshot of the output of /var/log/messages when zm enters an alarm state and the error occurs.
And just to re-iterate, if I follow this same install procedure with 1.19.4 everything mysql wise works perfectly, so I can only assume this is to do with a new feature in this version.
./configure --etc (no errors)
perl zmconfig.pl (completed without problems)
mysql ... (mysql setup appeared to go without problems)
perl zmconfig.pl -noi (completed without problems)
make (no errors)
make install (no errors)
web interface now works, showing correct version etc.
Did 'add monitor', used the following settings:
Monitor
Name: Drive
Function: Modect
Section length: 600
Frame Skip: 0
Run mode: Continuous
Trigger: n/a
Source type: local
Source
Device number: 0
Device channel: 0
Device format: 0
capture palette: rgb24
capture width: 352
capture height: 288
orientation: normal
Timestamp
all default
Buffers
Image buffer size: 500
Warmup frames: 100
Pre event image buffer: 250
Post event image buffer: 250
Alarm frame count: 2
Misc
Event prefix: Drive
Max fps: 25
ftp report interval: 1000
reference image blend: 10
--
I also added another 2 monitors, with the same settings. Everything goes green in the web interface to indicate everything is working.
A few informational screenshots.
Apparently working console
everything looks fine here.
Monitor window
This is what happens when an alarm is triggered and zm tries to record the event to the db
Server logging
This is a snapshot of the output of /var/log/messages when zm enters an alarm state and the error occurs.
And just to re-iterate, if I follow this same install procedure with 1.19.4 everything mysql wise works perfectly, so I can only assume this is to do with a new feature in this version.