#SQLITE_ERROR: no such table: migrations

67 messages · Page 1 of 1 (latest)

whole nova
#

SQLITE_ERROR: no such table: migrations

I'm getting the following error when migrating from Overseerr. I haven't fully figured it out yet, but it's triggered by something in my settings.json

I created three test directories. One with both my db dir and settings.json copied from overseerr, the second was just the settings.json and the final one with just the db dir. The third one with just the db dir was the only one to start up.

I just haven't looked into what exactly triggers it.

I was able to get around it by starting a new version of seerr and copying over the sections from my old settings into the new settings a clean version of seerr created

#

old_settings.json is what I had with overseerr and new_settings.json is what I was able to get working

analog seal
#

Can you show me yoir compsoe

#

And what image you were migrating from

#

Im pretty sure its nothing to do with the migrations but a pebkac error 😅

#

But lets try and figure out

analog seal
#

And we shall see

whole nova
analog seal
whole nova
#

to migrate I simply copied the db dir and settings.json from overseerr to a new seerr directory. I used the docker-compose.yml to spin it up

analog seal
analog seal
analog seal
#

You need to follow migration guide

#

You need the permissions setup

whole nova
#

Oh the uid/gid of 1000:1000 ? I saw that and made sure that uid:gid was being used already

#

I also had the old container set to use that for the uid:gid

analog seal
#

On config folder

#

Because overseerr used a different user to create the files. So those files will not be owned by the same user

whole nova
#

Here's the main dir
drwxrwxr-x 3 1000 1000 4096 Feb 15 08:00 seerr

The contents
drwxr-xr-x 2 1000 1000 4096 Feb 15 08:00 db
-rw-rw-r-- 1 1000 1000 616 Feb 15 08:05 docker-compose.yml
-rwxrwxr-x 1 1000 1000 8260 Feb 15 08:50 settings.json

And the DB directory
-rw-r--r-- 1 1000 1000 548864 Feb 15 08:10 db.sqlite3
-rw-r--r-- 1 1000 1000 32768 Feb 15 08:10 db.sqlite3-shm
-rw-r--r-- 1 1000 1000 4140632 Feb 15 08:10 db.sqlite3-wal

#

I did read that part and did validate things

analog seal
#

Is this the overseerr directory?

whole nova
#

That's the seerr directory

#

what's odd is I can copy over the db directory and things work. I only get the error when I copy over the settings.json

#

I did get things working.

analog seal
#

Its designed to be regenerated anyways

#

Incase a weird edge case happens

whole nova
#

I manually copied over the services from my old config into the new config. Seerr still asked me to do the setup process, but it had everything filled out already - likely caused I copied that stuff over

#

Once I got the main screen, post setup, it has everything there, so the db stuff worked fine as well

analog seal
#

You can delete it

#

And youll get a setup page

#

Your data remains in db 😉

whole nova
#

kind of a nuance, but figured I would create something here since I didn't see anyone else have a similar issue.

analog seal
#

But you can always edit the settings.json

#

Its designed to do that. You can just copy paste like radarr vblocks

#

From overseerr one

#

Into seerr too

whole nova
#

yea, I understand that stuff.

#

I've worked with sql and json before.

#

migration scripts are a giant pain

#

Either way, nice job. I'm excited to try our seerr! I'm happy to have a working version now!

#

Thanks for looking into this with me

#

Holy crap, I'm an idiot...

# 
      - ${DOCKER_CONFIG_PARENT_DIR}:/app/config```
analog seal
#

Instead of /overseerr right?

whole nova
#

${DOCKER_CONFIG_PARENT_DIR} does NOT map to the seerr directory

#

yea, I missed adding a child directory

analog seal
#

Hahaha 😅

#

Happens

whole nova
#

wth

#

life is pain

analog seal
#

Ive done worse. Wasted like 4hrs due to typos

whole nova
#

ha ha. Been there

#

so yea, it was a perms issue because THAT directory was NOT 1000:1000

#

You were right the whole time 😉

whole nova
#

Wanted to add one more thing here... Doing things the way I did also screwed up the api authed stuff. I couldn't login with Plex accounts and a few other things wouldn't work.

#

Ended up scrapping my settings.json and pulled over the overseerr version unmodified. That fixed everything.