Locked out of Database

[B08Z]

We have been using baby buddy for 3 months with our triplets it's been such a useful tool. However, for some reason I had to log back in and unfortunately managed to lock my self out of the database.

I have seen that I can use manage.py but it's not available in the docker image.

Is there any advice on how to unlock the dB when running BB in a docker.

[cdubz]

The management command should be accessible even in Docker -- it can just be a little tough to get working...

Does this discussion help at all? #676 (comment)

[barakplasma]

It's likely that your db is an SQLite file in the docker container, or in a docker volume. You might be able to docker cp to back it up.

I setup litestream » B2 storage for my BB instance for backup purposes.

[B08Z]

It's likely that your db is an SQLite file in the docker container, or in a docker volume. You might be able to docker cp to back it up.

I setup litestream » B2 storage for my BB instance for backup purposes.

I'll have a look at doing this but I thought the DB was locked out even if I found it.

[B08Z]

The management command should be accessible even in Docker -- it can just be a little tough to get working...

Does this discussion help at all? #676 (comment)

Hmm, I'm not sure it does. You say the mange.py command should be available in docker could you explain how I might run it?

[cdubz]

Hmm, I'm not sure it does. You say the mange.py command should be available in docker could you explain how I might run it?

Docker is not an area where I am particularly strong but I think you should be able to shell in to the container and use it, right?

[B08Z]

Hmm, I'm not sure it does. You say the mange.py command should be available in docker could you explain how I might run it?

Docker is not an area where I am particularly strong but I think you should be able to shell in to the container and use it, right?

I can shell into the docker container but I have no idea where to run manage.py from. It doesn't seem to exist within the container.

Also I'd happily copy the DB out but can't seem to find where it's stored.

[cdubz]

Here is the old issue comment I was trying to find -- #273 (comment)

Does that help? If so we should also document this... (:

[nitsujesor]

Hi @cdubz, @B08Z,

I had the same issue and was able to resolve it with the following steps:

1. enter the Baby Buddy docker shell:

docker exec -it babybuddy sh

2. set Django/BB settings:

export \
    DJANGO_SETTINGS_MODULE="babybuddy.settings.base" \
    ALLOWED_HOSTS="${ALLOWED_HOSTS:-*}" \
    TIME_ZONE="${TZ:-UTC}" \
    DEBUG="${DEBUG:-False}" \
    SECRET_KEY="${SECRET_KEY:-$(cat /config/.secretkey)}"

3. Create new "recovery" user:

python /app/www/public/manage.py createuser --username recovery --password recovery --is-staff

4. Login to recovery user, reset login information as required.

Thanks to the efforts of the users in #273 and #676 for laying out the individual steps!

[B08Z]

Hi @cdubz, @B08Z,

I had the same issue and was able to resolve it with the following steps:

1. enter the Baby Buddy docker shell: docker exec -it babybuddy sh
2. set Django/BB settings: export \ DJANGO_SETTINGS_MODULE="babybuddy.settings.base" \ ALLOWED_HOSTS="${ALLOWED_HOSTS:-*}" \ TIME_ZONE="${TZ:-UTC}" \ DEBUG="${DEBUG:-False}" \ SECRET_KEY="${SECRET_KEY:-$(cat /config/.secretkey)}"
3. Create new "recovery" user: python /app/www/public/manage.py createuser --username recovery --password recovery --is-staff
4. Login to recovery user, reset login information as required.

Thanks to the efforts of the users in #273 and #676 for laying out the individual steps!

Thanks so much.

I just tried but get an error:

: export \ DJANGO_SETTINGS_MODULE="babybuddy.settings.base" \ ALLOWED_HOSTS="${ALLOWED_HOSTS:-*}" \ TIME_ZONE="${TZ:-UTC}" \ DEBUG="${DEBUG:-False}" \ SECRET_KEY="${SECRET_KEY:-$(cat /config/.secretkey)}"

sh: export: DJANGO_SETTINGS_MODULE: bad variable name

Sorry for poor formatting on a phone trying to feed a baby;)

[nitsujesor]

Sorry, my previous formatting was imprecise. I was able to replicate your error when copy/pasting what I had above in Step 2. Please copy/paste the block as it is in #676. I will edit my above comment to reflect this change.

export \
    DJANGO_SETTINGS_MODULE="babybuddy.settings.base" \
    ALLOWED_HOSTS="${ALLOWED_HOSTS:-*}" \
    TIME_ZONE="${TZ:-UTC}" \
    DEBUG="${DEBUG:-False}" \
    SECRET_KEY="${SECRET_KEY:-$(cat /config/.secretkey)}"

[B08Z]

So,

Once again thanks so much I am now onto the app and can view users in the database.

I have changed the password and logged back in under that user but all the data has gone.

Is this expected behaviour? I fear I might have messed up the DB when trying to get back in.

In my docker config folder I can see the sqlight DB and see that it's large as in looks like it has data?

I hope I'm getting closer.

Thanks again this app is a complete life saver with multiples.

[MrApplejuice]

You should be able to tell if there is any data in the database by clicking on any of the activities:

This is a screenshot of the sleep entries in of by Babybuddy test instance. It should be relatively straightforward to read.

[B08Z]

Thanks for coming back to me.

Attached are the screen shots from the DB admin page and also one when I run ls -la of the DB file.

I can see that the db.sqlite file has data in but as you can see from the screen shots there is nothing apearing in the app.

[MrApplejuice]

Yeah, that unfortunately looks very very empty, indeed. You could try to download the database file and view it in https://sqlitebrowser.org/ . Maybe that there is something left in there.