Closed dannytsang closed 2 months ago
This means that the workers container either hasn't been restarted or hasn't been updated. Try restarting the worker container first, if it didn't work, try re-pulling its latest version and restart it one more time. That should run the migrations and mitigate the errors.
I tried restarting the worker, then stopped, removed the image and re-pulled it but I'm afraid it still has the same error.
The worker log is showing the below. Is it stuck at starting search index work?
Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-9.7.1.tgz.
(node:35) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
> @hoarder/workers@0.1.0 start:prod /app/apps/workers
> tsx index.ts
2024-08-18T20:18:27.633Z info: Workers version: 0.15.0
2024-08-18T20:18:27.641Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222
2024-08-18T20:18:27.655Z info: [Crawler] Successfully resolved IP address, new address: http://172.18.0.57:9222/
2024-08-18T20:18:29.380Z info: Starting crawler worker ...
2024-08-18T20:18:29.381Z info: Starting inference worker ...
2024-08-18T20:18:29.381Z info: Starting search indexing worker ...
I also noticed I was originally using the nightly build because I didn't specify a tag for the work image. Now (and you can see above) I'm using the release tag.
I also noticed I was originally using the nightly build because I didn't specify a tag for the work image. Now (and you can see above) I'm using the release tag.
That's your problem. You're using nightly
(latest) for web, but release
tag for workers. Hoarder assumes that both containers are using the same version. It's not safe to go back in versions, so you'll need to use nightly (latest
) for workers for now, and then after the next release, you can go back to the release
tag.
The next release will simplify the whole thing by merging the two containers in one :)
I also noticed I was originally using the nightly build because I didn't specify a tag for the work image. Now (and you can see above) I'm using the release tag.
That's your problem. You're using
nightly
(latest) for web, butrelease
tag for workers. Hoarder assumes that both containers are using the same version. It's not safe to go back in versions, so you'll need to use nightly (latest
) for workers for now, and then after the next release, you can go back to therelease
tag.
I've just started so no big data loss. I stopped hoarder, removed the db files in the data volume, added the release tag and started it up from scratch. I then restarted the worker that's laready on the release version and all is good now.
Thank you for your very quick response @MohamedBassem and look forward to the next version.
I'm getting the following error when I go to Admin section and spams the docker logs:
It's probably my problem because I'm running all the services as docker rather than using compose on Unraid. I can see there's db.db and queue.db created in the data volume which I've mapped to both wed and works container.
Full docker log:
My docker templates (redacted secrets) for hoarder: Web:
Worker: