Replies: 3 comments
-
|
That looks like |
Beta Was this translation helpful? Give feedback.
-
Thanks genius for your response, I didn't see that guide, maybe I got confused with many guides for many versions for many changes of parameters, really a nightmare, even I spend a whole day using "value mariadb" and the logs says that I was using mariadb without logging anything to database nor a error logged, the log just says using mariadb. On my first try I use %{dbeventid} but the logs says "mystrftime_long: {dbeventid} is not supported. Use eventid." thats why I've change to eventid without knowing from a guide that is a (cam id + date/time). Yes, I want dbeventid but the log says that is not supported as copied before and I can't put the value of dbeventid in the database If I use %{dbeventid} in insert I got: I will test to update tables (movie_end) using eventid to check if there is a consistence in the value. |
Beta Was this translation helpful? Give feedback.
-
|
Resolved moving everything related to DB to my own php scripts and not using DB support from Motion. |
Beta Was this translation helpful? Give feedback.
-
Did you read the guide?
Yes
What is the base version number of Motion being used?
4.5.x
What was the install method?
Built from source code
What is base architecture?
x86
What is the distro being used?
Debian
Disto version number
11
Camera type(s) being used?
Network camera with HTTP
Describe the issue/problem and steps to reproduce
Been using motion for years in small devices, now I setup a linux PC with motion to watch my cams, everything works ok but the %{eventid} in queries, got values likes: 10320230601072616, 10420230601072804, 10320230601150847, the field is defined as BIGInt, primary key with auto increment, all fields are populated, except %f in sql_start but its ok because I readed that the name of the file is not know at that moment and %n that is always null, but I need the primary key value to update movie_end time when the event ends, I just download the git source and the problem is the same.
Table definition:
create table events (event_id BIGINT PRIMARY KEY AUTO_INCREMENT, camera_id INTEGER NOT NULL, filename VARCHAR(255), file_type INTEGER, time_stamp DATETIME NOT NULL, frame INTEGER, motion_event INTEGER, movie_end DATETIME, comments varchar(120), temp BIGINT);Queries:
Table content (full path manually removed from filename, comments and temp defined to trace this problem):
Motion log output at log_level 8
Beta Was this translation helpful? Give feedback.
All reactions