Full ALPR Database System for Blue Iris!

[smallik]

The log indicates that you are successfully calling the DB API when BI alerts on a plate. And it looks like the image is saved successfully, but then the rest of the plate read data doesn't save correctly. Can you post the complete text of your post/payload from the "On Alert" that makes the http/API call?

This is it: { "plate_number":"&PLATE", "Image":"&ALERT_JPEG", "camera":"&CAM", "ALERT_PATH": "&ALERT_PATH", "ALERT_CLIP": "&ALERT_CLIP", "timestamp":"&ALERT_TIME" }

 

[VideoDad]

That all looks correct. I'll have to defer to Charlie or Mike, or someone that knows why the database might be failing on the insertion of a new plate.

 

[smallik]

That all looks correct. I'll have to defer to Charlie or Mike, or someone that knows why the database might be failing on the insertion of a new plate.

Very much appreciated.

 

[hopalong]

It still seems like the migration didn't run which sets up the schema properly?

 

[smallik]

It still seems like the migration didn't run which sets up the schema properly?

Any possible actions to correct this?

 

[Vettester]

Try entering 192.168.68.111:3000/update into a browser and follow the migration process.

Edit: This assumes you have downloaded the migration file and put into the same folder as your docker compose file.

 

[hopalong]

Any possible actions to correct this?

You have to get into the db console and run a few commands.

You would need to download and mount migrations.sql on the same way as schema.sql, then open postgres docker console and run:

psql -U postgres -d postgres -f /migrations.sql

 

[smallik]

You have to get into the db console and run a few commands.

You would need to download and mount migrations.sql on the same way as schema.sql, then open postgres docker console and run:

psql -U postgres -d postgres -f /migrations.sql

OK, I need you to slow down as this is a steep learning curve for me. I did the 192.168.68.111:3000/update migration process and that was successful. Then went to "GitHub - algertc/ALPR-Database: Fully-Featured Automated License Plate Recognition Database for Blue Iris + CodeProject AI Server" and downloaded all the files including "migrations.sql" and of course "schema.sql". They're in my download folder. Now I need some guidance on the "mount migrations.sql on the same way as schema.sql" part and then where/how to "open postgres docker console and run: psql -U postgres -d postgres -f /migrations.sql". I appreciate your patience.

 

[hopalong]

OK, I need you to slow down as this is a steep learning curve for me. I did the 192.168.68.111:3000/update migration process and that was successful. Then went to "GitHub - algertc/ALPR-Database: Fully-Featured Automated License Plate Recognition Database for Blue Iris + CodeProject AI Server" and downloaded all the files including "migrations.sql" and of course "schema.sql". They're in my download folder. Now I need some guidance on the "mount migrations.sql on the same way as schema.sql" part and then where/how to "open postgres docker console and run: psql -U postgres -d postgres -f /migrations.sql". I appreciate your patience.

If you did the update via the link you should be good.

 

[smallik]

If you did the update via the link you should be good.

Still seeing this in the log-

 

[smallik]

Just another data point. Do these Docker screen shots look normal to those who have their ALPR Database setups working?

 

[Vettester]

Expand your containers so we can see what it looks like. It should look something like this:

 

[smallik]

Expand your containers so we can see what it looks like. It should look something like this:

View attachment 216585

Looks like this-

 

[Vettester]

Looks like this-

Hmmm.... it looks like your containers are running. If you click on where it says app-1 and db-1 it should open up a window with six diagnostic tabs. I would look through the logs and stats tabs to see if there is anything that stands out and gives you an indication of what could be wrong.