starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-26 00:16:03 +03:00

[GH-ISSUE #1175] Workers / Queue Stuck #771

New issue

Closed

opened 2026-03-02 11:52:37 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 11:52:37 +03:00

Owner

Originally created by @patach on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1175

Describe the Bug

Queue completely stuck indexing and inference, very little notes on logs.

Currently using nightly version that split assets DIR and DB locations. Current logs say this:

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service init-db-migration: starting

Running db migration script

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-db-migration successfully started

s6-rc: info: service svc-web: starting

s6-rc: info: service svc-web successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

▲ Next.js 14.2.25

Local: http://localhost:3000

Network: http://0.0.0.0:3000

✓ Starting...

✓ Ready in 152ms

Nothing else after that.

Is there also a way to reset these jobs? Accidentally tripled up to them when I tried getting them to work.

Steps to Reproduce

N/A

Expected Behaviour

Expected logs to show workers attempting and succeeding or failing at tasks, including inference and indexing.

Screenshots or Additional Context

No response

Device Details

No response

Exact Hoarder Version

latest (most recent nightly)

Have you checked the troubleshooting guide?

I have checked the troubleshooting guide and I haven't found a solution to my problem

Originally created by @patach on GitHub (Mar 30, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1175 ### Describe the Bug Queue completely stuck indexing and inference, very little notes on logs. Currently using nightly version that split assets DIR and DB locations. Current logs say this: > s6-rc: info: service s6rc-oneshot-runner: starting > > s6-rc: info: service s6rc-oneshot-runner successfully started > > s6-rc: info: service fix-attrs: starting > > s6-rc: info: service init-db-migration: starting > > Running db migration script > > s6-rc: info: service fix-attrs successfully started > > s6-rc: info: service legacy-cont-init: starting > > s6-rc: info: service legacy-cont-init successfully started > > s6-rc: info: service init-db-migration successfully started > > s6-rc: info: service svc-web: starting > > s6-rc: info: service svc-web successfully started > > s6-rc: info: service legacy-services: starting > > s6-rc: info: service legacy-services successfully started > > ▲ Next.js 14.2.25 > > - Local: http://localhost:3000 > > - Network: http://0.0.0.0:3000 > > ✓ Starting... > > ✓ Ready in 152ms Nothing else after that. ![Image](https://github.com/user-attachments/assets/f5df8f85-dee6-44b3-8d2b-c9d15f10692a) Is there also a way to reset these jobs? Accidentally tripled up to them when I tried getting them to work. ### Steps to Reproduce N/A ### Expected Behaviour Expected logs to show workers attempting and succeeding or failing at tasks, including inference and indexing. ### Screenshots or Additional Context _No response_ ### Device Details _No response_ ### Exact Hoarder Version latest (most recent nightly) ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem

kerem

2026-03-02 11:52:37 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Mar 30, 2025):

it seems that the worker binary is not even starting. So even if you rest the jobs, the new ones will get stuck. Are you by any chance in a country with restricted internet access? The worker binary on startup downloads some adblocker lists from github for example. If github is not accessible from within the container, it might cause such stuckness. You can try 'CRAWLER_ENABLE_ADBLOCKER=false'.

@MohamedBassem commented on GitHub (Mar 30, 2025): it seems that the worker binary is not even starting. So even if you rest the jobs, the new ones will get stuck. Are you by any chance in a country with restricted internet access? The worker binary on startup downloads some adblocker lists from github for example. If github is not accessible from within the container, it might cause such stuckness. You can try 'CRAWLER_ENABLE_ADBLOCKER=false'.

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@patach commented on GitHub (Mar 30, 2025):

I live in the United States and shouldn't currently have any restricted internet access. Putting CRAWLER_ENABLE_ADBLOCKER=false into the .env didn't make any difference, unfortunately.

hoarder-web log seems similar:

 s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service init-db-migration: starting

Running db migration script

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-db-migration successfully started

s6-rc: info: service svc-web: starting

s6-rc: info: service svc-web successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

  ▲ Next.js 14.2.25

  - Local:        http://localhost:3000

  - Network:      http://0.0.0.0:3000

 ✓ Starting...

 ✓ Ready in 159ms

@patach commented on GitHub (Mar 30, 2025): I live in the United States and shouldn't currently have any restricted internet access. Putting CRAWLER_ENABLE_ADBLOCKER=false into the .env didn't make any difference, unfortunately. hoarder-web log seems similar: ``` s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-db-migration: starting Running db migration script s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-db-migration successfully started s6-rc: info: service svc-web: starting s6-rc: info: service svc-web successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started ▲ Next.js 14.2.25 - Local: http://localhost:3000 - Network: http://0.0.0.0:3000 ✓ Starting... ✓ Ready in 159ms ```

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Mar 30, 2025):

can you share your docker compose? The warning in your screenshot means you're running the old container setup where the workers and the web container are separate. So you're either not running the worker container at all, or we're looking at the wrong logs.

@MohamedBassem commented on GitHub (Mar 30, 2025): can you share your docker compose? The warning in your screenshot means you're running the old container setup where the workers and the web container are separate. So you're either not running the worker container at all, or we're looking at the wrong logs.

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@patach commented on GitHub (Mar 30, 2025):

Sure thing:

version: "3.8"
services:
web:
image: ghcr.io/hoarder-app/hoarder-web:latest
restart: unless-stopped
volumes:
# By default, the data is stored in a docker volume called "data".
# If you want to mount a custom directory, change the volume mapping to:
# - /path/to/your/directory:/data
- ./data:/data
- /home/user/shares/data2/o/HoarderData:/assets
ports:
- 3000:3000
env_file:
- .env
environment:
MEILI_ADDR: http://meilisearch:7700
BROWSER_WEB_URL: http://chrome:9222
OLLAMA_BASE_URL: http://192.168.0.189:11434
INFERENCE_TEXT_MODEL: gemma2:2b
INFERENCE_IMAGE_MODEL: llava:7b
# OPENAI_API_KEY: ...
  # You almost never want to change the value of the DATA_DIR variable.
  # If you want to mount a custom directory, change the volume mapping above instead.
  DATA_DIR: /data # DON'T CHANGE THIS
chrome:
image: gcr.io/zenika-hub/alpine-chrome:123
restart: unless-stopped
command:
- --no-sandbox
- --disable-gpu
- --disable-dev-shm-usage
- --remote-debugging-address=0.0.0.0
- --remote-debugging-port=9222
- --hide-scrollbars
meilisearch:
image: getmeili/meilisearch:v1.11.1
restart: unless-stopped
env_file:
- .env
environment:
MEILI_NO_ANALYTICS: "true"
volumes:
- meilisearch:/meili_data

volumes:
meilisearch:
data:

The only other logs I have with hoarder are chrome and meilisearch.

Would you need those?

@patach commented on GitHub (Mar 30, 2025): Sure thing: > version: "3.8" > services: > web: > image: ghcr.io/hoarder-app/hoarder-web:latest > restart: unless-stopped > volumes: > # By default, the data is stored in a docker volume called "data". > # If you want to mount a custom directory, change the volume mapping to: > # - /path/to/your/directory:/data > - ./data:/data > - /home/user/shares/data2/o/HoarderData:/assets > ports: > - 3000:3000 > env_file: > - .env > environment: > MEILI_ADDR: http://meilisearch:7700 > BROWSER_WEB_URL: http://chrome:9222 > OLLAMA_BASE_URL: http://192.168.0.189:11434 > INFERENCE_TEXT_MODEL: gemma2:2b > INFERENCE_IMAGE_MODEL: llava:7b > # OPENAI_API_KEY: ... > > # You almost never want to change the value of the DATA_DIR variable. > # If you want to mount a custom directory, change the volume mapping above instead. > DATA_DIR: /data # DON'T CHANGE THIS > chrome: > image: gcr.io/zenika-hub/alpine-chrome:123 > restart: unless-stopped > command: > - --no-sandbox > - --disable-gpu > - --disable-dev-shm-usage > - --remote-debugging-address=0.0.0.0 > - --remote-debugging-port=9222 > - --hide-scrollbars > meilisearch: > image: getmeili/meilisearch:v1.11.1 > restart: unless-stopped > env_file: > - .env > environment: > MEILI_NO_ANALYTICS: "true" > volumes: > - meilisearch:/meili_data > > volumes: > meilisearch: > data: The only other logs I have with hoarder are chrome and meilisearch. Would you need those?

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Mar 30, 2025):

As expected, don't know how you ended up there but you're running the web only image (that's why the workers are not running).

Replace the image from hoarder-app/hoarder-web to hoarder-app/hoarder and you should see the worker coming into life (and the warning in the admin panel disappearing).

@MohamedBassem commented on GitHub (Mar 30, 2025): As expected, don't know how you ended up there but you're running the web only image (that's why the workers are not running). Replace the image from hoarder-app/hoarder-web to hoarder-app/hoarder and you should see the worker coming into life (and the warning in the admin panel disappearing).

kerem commented

2026-03-02 11:52:38 +03:00

Author

Owner

@patach commented on GitHub (Mar 30, 2025):

Ah I see. I grabbed the wrong image by mistake. Thank you so much for that. The workers are working now :)

@patach commented on GitHub (Mar 30, 2025): Ah I see. I grabbed the wrong image by mistake. Thank you so much for that. The workers are working now :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#771

No description provided.

Rows
Columns