Is this a new install or an upgrade--if it is an upgrade, was it working before without ai_dump?
Full ALPR Database System for Blue Iris!
- Thread starter algertc
- Start date
New install. running in docker tesktop on Win11. Initially had the same issue as svalvasori, after a few full deletes and reinstalls i got that error straightened out only to have this new error pop up.
Thanks for the help. Yes i did run that and that fixed my initial error of: ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification
Im guessing its a DB error on my end but after multiple full delete's, and deleting the folders and re installing its the same issue.
Can you issue the same db command but -f migrations.sql instead?
Also, cut and paste this into BI on alert settings, just in case it's something simple
{"ai_dump":&JSON, "Image":"&ALERT_JPEG", "camera":"&CAM", "ALERT_PATH":"&ALERT_PATH", "ALERT_CLIP":"&ALERT_CLIP", "timestamp":"&ALERT_TIME"}
Also, cut and paste this into BI on alert settings, just in case it's something simple
{"ai_dump":&JSON, "Image":"&ALERT_JPEG", "camera":"&CAM", "ALERT_PATH":"&ALERT_PATH", "ALERT_CLIP":"&ALERT_CLIP", "timestamp":"&ALERT_TIME"}
Pasted the string into alert settings. below is the output of the DB command. Still no bueno.
root@65dd36601b9b:/# psql -d postgres -U postgres -f /migrations.sql
psql:/migrations.sql:1: NOTICE: extension "pg_trgm" already exists, skipping
CREATE EXTENSION
psql:/migrations.sql:2: NOTICE: extension "fuzzystrmatch" already exists, skipping
CREATE EXTENSION
psql:/migrations.sql:6: NOTICE: column "priority" of relation "plate_notifications" already exists, skipping
ALTER TABLE
psql:/migrations.sql:19: NOTICE: column "camera_name" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "image_path" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "thumbnail_path" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "bi_path" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "plate_annotation" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "crop_coordinates" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "ocr_annotation" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "confidence" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "bi_zone" of relation "plate_reads" already exists, skipping
psql:/migrations.sql:19: NOTICE: column "validated" of relation "plate_reads" already exists, skipping
ALTER TABLE
psql:/migrations.sql:23: NOTICE: column "ignore" of relation "known_plates" already exists, skipping
ALTER TABLE
psql:/migrations.sql:27: NOTICE: column "occurrence_count" of relation "plates" already exists, skipping
psql:/migrations.sql:27: NOTICE: column "occurrence_count" of relation "plates" already exists, skipping
ALTER TABLE
DO
CREATE FUNCTION
DO
psql:/migrations.sql:74: NOTICE: relation "devmgmt" already exists, skipping
CREATE TABLE
INSERT 0 0
psql:/migrations.sql:80: NOTICE: column "training_last_record" of relation "devmgmt" already exists, skippingALTER TABLE
root@65dd36601b9b:
What version of BI are you running? and what does your ALPRDB logs show (command line icon on the gui, bottom left)
BI 5.9.9.36
4/1/2025, 1:44:58 PM [INFO] POST /api/plate-reads
4/1/2025, 1:44:58 PM [INFO] Received plate read data: [object Object]
4/1/2025, 1:44:58 PM [INFO] Database connection established
4/1/2025, 1:44:59 PM [INFO] [FileStorage] Successfully saved image
4/1/2025, 1:44:59 PM [ERROR] Error processing request: error: null value in column "plate_number" of relation "plate_reads" violates not-null constraint
Yeah, strange. Did you check the md5 of schema and migrations? Probably not the issue since it's complaining that the columns exist.
Have you tried deleting your database container and then doing a docker compose pull? and if it doesn't come up, do the database schema, migration, and see if that helps with a clean start?
Or maybe just do this:
dropdb -U postgres postgres
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
Or maybe just do this:
dropdb -U postgres postgres
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
Last edited:
that just eneded up deleting the DB and not rebuilding anything. I had to do a clean install after that. and still same issue.
after dropdb, you might have to createdb -U postgres postgres
before the schema, but either way, reinstall (fresh pull) would have accomplished the same.
before the schema, but either way, reinstall (fresh pull) would have accomplished the same.
Just an update. Finally figured it out and got the database working. I had to change my AI alert settings.
in the to confirm field I had to remove DayPlate,NightPlate and replace with *
the to cancel field to: DoNotCancel
then changed custom models from license-plate,alpr to: objects:0,alpr and now its feeding plates through.
in the to confirm field I had to remove DayPlate,NightPlate and replace with *
the to cancel field to: DoNotCancel
then changed custom models from license-plate,alpr to: objects:0,alpr and now its feeding plates through.
Somewhere in the notes for the ALPR Database, it should be mentioned that having a working LPR camera (correctly zoomed and focused, and configured for day and night capture) with the correct AI settings for detecting and recognizing plates in BI is the prerequisite.
I wouldn't mind like seeing this large monolithic thread split into separate topics such as installation issues, update issues, new release announcements, feature requests, etc.
