Full ALPR Database System for Blue Iris!

algertc said:
I think this is because you have such large databases and it's maxing out the memory or the max query size. It worked fine for me. I tried to set it up to do it in batches and have an image building now for that. Not sure if this way will work, but if someone could try it again and share what happens, that would be very helpful.
Click to expand...
So far it looks to be working for me
 
  • Like
Reactions: algertc
algertc said:
This is exactly what happened. Sorry about that! I pushed an image to test myself on another computer and didn't push the code to github.



This is correct. The reason I update it is just for completeness. You do not need to have it in order to update.


I just pushed it and merged some other things too. Fully on new image storage now and the database got so much faster. Changes were made to the compose file and the migrations file. You will also need to create a new directory called "storage" in the same place as your config and auth folders. This is where the JPEGs will be stored from now on. You will notice a little yellow question mark in the bottom corner with a temporary explanation. There are links to tools that will automatically convert your existing data in that page.
Click to expand...

Upgraded and migrated the images. Everything works perfectly now on my end. The database is indeed incredibly fast! I expected the image handling rewrite to take much longer. Fantastic work, Charlie! Thank you very much!
 
  • Like
Reactions: algertc
algertc said:
Ok this happened to me too but only when accessing from the same machine and only on one computer and not others. I’m very confused what’s happening.
Click to expand...
I have two Blue Iris servers sending plates to the ALPR Dashboard. Every time I try to update the API key on any of the BI server the API key changes.
 
I tried the latest update and am getting error. I replaced the docker-compose.yml, migrations.sql and schema.sql and pulled new docker image and get this error:

/Docker/ALPR$ sudo docker compose up -d
[+] Running 2/3
✔ Network alpr_default Created 0.3s
✔ Container alpr-db-1 Created 0.3s
⠋ Container alpr-app-1 Creating 0.1s
Error response from daemon: failed to populate volume: error while mounting volume '/var/lib/docker/volumes/alpr_app-plate_images/_data': failed to mount local volume: mount /home/paul/Docker/ALPR/storage:/var/lib/docker/volumes/alpr_app-plate_images/_data, flags: 0x1000: no such file or directory

not sure what Im missing
 
prsmith777 said:
I tried the latest update and am getting error. I replaced the docker-compose.yml, migrations.sql and schema.sql and pulled new docker image and get this error:

/Docker/ALPR$ sudo docker compose up -d
[+] Running 2/3
✔ Network alpr_default Created 0.3s
✔ Container alpr-db-1 Created 0.3s
⠋ Container alpr-app-1 Creating 0.1s
Error response from daemon: failed to populate volume: error while mounting volume '/var/lib/docker/volumes/alpr_app-plate_images/_data': failed to mount local volume: mount /home/paul/Docker/ALPR/storage:/var/lib/docker/volumes/alpr_app-plate_images/_data, flags: 0x1000: no such file or directory

not sure what Im missing
Click to expand...

did you make a local "storage" directory in your docker-compose directory?
 
  • Like
Reactions: prsmith777 and algertc
olympia said:
Upgraded and migrated the images. Everything works perfectly now on my end. The database is indeed incredibly fast! I expected the image handling rewrite to take much longer. Fantastic work, Charlie! Thank you very much!
Click to expand...

Hmm, the upgrade and database migration went smoothly—everything's running fast, and all my previous records are intact. However, I haven’t had any new plate detections recorded since then.
I even tried a fresh installation to see if the issue was related to the migration, but the problem persists. The database remains empty, and no new records are being created at all.
Has anyone else encountered this, or is it just me again? :)
 
  • Like
Reactions: Skinny1
olympia said:
Hmm, the upgrade and database migration went smoothly—everything's running fast, and all my previous records are intact. However, I haven’t had any new plate detections recorded since then.
I even tried a fresh installation to see if the issue was related to the migration, but the problem persists. The database remains empty, and no new records are being created at all.
Has anyone else encountered this, or is it just me again? :)
Click to expand...
Check if your API key changed
 
  • Like
Reactions: Skinny1
MikeLud1 said:
Are you also having issues with the API key constantly change.
Click to expand...

I'm experiencing the same issue now. I keep getting disconnected almost every few seconds, and the API key changes randomly and frequently. Actually API key changes are so frequent, that it is unusable now.
 
Last edited:
  • Like
Reactions: Skinny1
algertc said:
Ok this happened to me too but only when accessing from the same machine and only on one computer and not others. I’m very confused what’s happening.
Click to expand...
To add to the confusion I have BI and docker running on two separate machines and I haven’t had any issues with the api key.
 
  • Like
Reactions: Skinny1
You must log in or register to reply here.
Top Bottom