Caused by: java.sql.SQLSyntaxErrorException: (conn=15) Unknown database 'grimmory'

[jayscovill]

What Went Wrong?

This is probably just a "me doing something wrong" problem but I'm trying to stand up a fresh new instance of Grimmnory (vs migrating from Booklore by just replacing the image). Receiving the following error as it doesn't look like the 'grimmory' database is being created:

Caused by: java.sql.SQLSyntaxErrorException: (conn=15) Unknown database 'grimmory'

Trying set as root for starters.

My environment variables:

# Application
APP_USER_ID=0
APP_GROUP_ID=0
TZ=America/Toronto

# Database
DATABASE_URL=jdbc:mariadb://grimmory-mariadb:3306/grimmory
DB_USER=grimmory
DB_PASSWORD=Password

# Storage: LOCAL (default) or NETWORK (disables file operations; see Network Storage section)
DISK_TYPE=LOCAL

# MariaDB
DB_USER_ID=0
DB_GROUP_ID=0
MYSQL_ROOT_PASSWORD=Password
MYSQL_DATABASE=grimmory

docker-compose.yml

volumes:
  grimmory-data:
    name: grimmory-data
    driver: local
  grimmory-mariadb:
    name: grimmory-mariadb
    driver: local

services:
  grimmory:
    image: grimmory/grimmory:latest
    # Convenience tag:
    # image: grimmory/grimmory:<release-version>
    # Alternative: ghcr.io/grimmory-tools/grimmory:<release-version>
    # To build from source instead: comment out 'image' and uncomment below
    # build: .
    container_name: grimmory
    env_file:
      - path: ./stack.env
        required: false
    #environment:
    #  - USER_ID=${APP_USER_ID}
    #  - GROUP_ID=${APP_GROUP_ID}
    #  - TZ=${TZ}
    #  - DATABASE_URL=${DATABASE_URL}
    #  - DATABASE_USERNAME=${DB_USER}
    #  - DATABASE_PASSWORD=${DB_PASSWORD}
    depends_on:
      grimmory-mariadb:
        condition: service_healthy
    ports:
      - "6060:6060"
    volumes:
      - grimmory-data:/app/data
      - /mnt/books:/books
      - /mnt/complete/books:/bookdrop
    healthcheck:
      test: wget -q -O - http://localhost:6060/api/v1/healthcheck
      interval: 60s
      retries: 5
      start_period: 60s
      timeout: 10s
    restart: unless-stopped

  grimmory-mariadb:
    image: lscr.io/linuxserver/mariadb:11.4.5
    container_name: grimmory-mariadb
    env_file:
      - path: ./stack.env
        required: false
    #environment:
    #  - PUID=${DB_USER_ID}
    #  - PGID=${DB_GROUP_ID}
    #  - TZ=${TZ}
    #  - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
    #  - MYSQL_DATABASE=${MYSQL_DATABASE}
    #  - MYSQL_USER=${DB_USER}
    #  - MYSQL_PASSWORD=${DB_PASSWORD}
    volumes:
      - grimmory-mariadb:/config
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "mariadb-admin", "ping", "-h", "localhost"]
      interval: 5s
      timeout: 5s
      retries: 10

How Can We Reproduce This?

1. Fresh install of Grimmory

What Should Have Happened?

Database created and application started?

Screenshots or Error Messages (Optional)

No response

Any Ideas on How to Fix This? (Optional)

No response

Your Setup

• Grimmory V2.3.0

Before Submitting

• I've searched existing issues and confirmed this bug hasn't been reported yet

[balazs-szucs]

Keep the .env as it was before.

Do not change .env there is no need for that.

[jayscovill]

What specifically should be kept as before?

[russssl]

What specifically should be kept as before?

everything. just replace the image

[jayscovill]

I tried that and am having another issue which I was trying to see if this would solve. Besides, what if I was starting from scratch with no previous Booklore instance?

[balazs-szucs]

I tried that and am having another issue which I was trying to see if this would solve. Besides, what if I was starting from scratch with no previous Booklore instance?

Nothing. Those env variables or more less meaningless, BUT once they got into the DB, they must stay or be migrated. Since that hasn't happened and we are telling everybody not to change those manually, the best thing you can do it just replace the image, keep everything as-is.

[jayscovill]

If I am starting from scratch with no previous Booklore instance, shouldn't a new database be created? If not how do you run Grimmory without ever having a previous Booklore instance?

[russssl]

If I am starting from scratch with no previous Booklore instance, shouldn't a new database be created? If not how do you run Grimmory without ever having a previous Booklore instance?

if you want to create EMPTY instance then yes, new DB, do it separately if you want to preserve old booklore db. Grimmory is a successor of Booklore, so basically same setup as booklore, just make sure image in docker compose (if you use docker compose) is correct. refer to a README for the instructions.
Basically, if you want to preserve previous data, roll back the setup as it was before and just replace the image, you changed db name from booklore to grimmory, so it does not know what is that db is (it does not exist probably) so it crashes

[jayscovill]

I didn't change the name of the db. It's a fresh new installation. I am using the same name as given in a the docker-compose.yml. Just pretend I didn't say anything about having Booklore before. I am starting from scratch. In that case, wouldn't the database get created on first fun? If so, why isn't that happening in this case?

[russssl]

I didn't change the name of the db. It's a fresh new installation. I am using the same name as given in a the docker-compose.yml. Just pretend I didn't say anything about having Booklore before. I am starting from scratch. In that case, wouldn't the database get created on first fun? If so, why isn't that happening in this case?

yes it would be created on the container start. just copy docker compose, adjust volume locations if needed, create .env, populate it with data necessary and run the container. that would be it

[imajes]

Converted this to a discussion as i'm not sure it's an error - we have had no other similar reports.

@jayscovill can you paste your grimmory & mariadb docker logs please.