homarr stopped working
homarr stopped working
Error [TRPCClientError]: no such table: user
at TRPCClientError.from (file:///app/.next/server/src/middleware.js:1718:20)
at <unknown> (file:///app/.next/server/src/middleware.js:2273:60)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
31 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Hi @heavypenalty , please add the missing details as mentioned by @Cakey Bot .
image: ghcr.io/ajnart/homarr:latest
portainer stack
#---------------------------------------------------------------------#
Homarr - A simple, yet powerful dashboard for your server. #
#---------------------------------------------------------------------#
services:
homarr:
container_name: homarr
image: ghcr.io/ajnart/homarr:latest
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- /mnt/OgreStore/docker/homarr/configs:/app/data/configs
- /mnt/OgreStore/docker/homarrr/icons:/app/public/icons
- /mnt/OgreStore/docker/homarr/data:/data
ports:
- '7575:7575'
this has been running fine until, I updated the image to the lastest version
Is
/mnt/OgreStore a local disk or a SMB / share?smb
all the other arr's are using the smb just fine
We do not fork of the same code as Sonarr / Radarr & co do.
Therefore Homarr will behave differently in most scenarios.
Please try the above fix. It's most likely a permission issue because our container is using the root.
A custom user cannot be used currently due to a known bug / issue.
I understand, was just saying that the smb is setup correctly
Sure, I don't doubt that your SMB isn't "working". It just doesn't function in combination with the permissions of the Homarr container. The above link should provide you the information you need to adjust that.
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
DrizzleError: Failed to run the query '
CREATE TABLE IF NOT EXISTS "__drizzle_migrations" (
id SERIAL PRIMARY KEY,
hash text NOT NULL,
created_at numeric
)
': database is locked
database is locked
- Either your database is corrupt (eg. damaged filesystem, drive or unclean shutdown of app or OS)
- Your filesystem is maybe readonly
- Homarr is unable to read or writeI figured it might be the read/write
but everything looks okay
#---------------------------------------------------------------------#
Homarr - A simple, yet powerful dashboard for your server. #
#---------------------------------------------------------------------#
services:
homarr:
container_name: homarr
image: ghcr.io/ajnart/homarr:latest
restart: unless-stopped
environment:
- PUID=1000
- PGID=1000
volumes: - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration - /mnt/OgreStore/docker/homarr/configs:/app/data/configs - /mnt/OgreStore/docker/homarrr/icons:/app/public/icons - /mnt/OgreStore/docker/homarr/data:/data ports: - '7575:7575' I added puid/pgid to the stack config
volumes: - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration - /mnt/OgreStore/docker/homarr/configs:/app/data/configs - /mnt/OgreStore/docker/homarrr/icons:/app/public/icons - /mnt/OgreStore/docker/homarr/data:/data ports: - '7575:7575' I added puid/pgid to the stack config
You most likely can't set
PUID and PGID because Homarr currently has issues with executing migrations & accessing data. It's an issue in our Docker image we haven't been able to fix yet. Feel free to try though.
I'd suggest that you permit the UID AND GID of Homarr r&w access to the filesystem (or SMB in this case) instead.what user is homarr running under? node?
Normally, Docker runs as
nobody. Also look what user it is inside the container (open shell in Portainer and enter id or whoami)
Not on your host system. Inside your container 🙂
that is in the container
Is root permitted on your share?
this tells me it is
And it still doesn't work when you remove the PID & UID?
Neither worked
with or without
@Meierschlumpf can you look into this?
Is drizzle maybe running on a different user somehow?
No it's running on the normal docker user, I still don't have a clue why this happens to people
so any suggestions on what to do?
I guess my next step is to try to run the container with local storage
@heavypenalty try to recreate the container, this time with a volume for the database