Karakeep updates successfuly to v0.32.0 but fails to start

Support apps
,
1

What app is this about, and its version: Karakeep, v.0.32.0
What YunoHost version are you running: 12.1.39
What type of hardware are you using: VPS bought online

Describe your issue

What I’m trying to do
I am attempting to update the Karakeep application from v0.31.0 to v0.32.0 on a YunoHost 12.1.39 (stable) system. Upgrade issues with Karakeep have occurred consistently with every update since v0.28.0 for me (not sure if related).

What happens

  • Update Process: The update completes without errors, whether initiated via the YunoHost web-admin or CLI.

  • Post-Update Behavior:
    The application fails to start correctly.
    The UI returns a Internal Server Error error when accessed.
    The karakeep-workers service fails to start after the update.
    The karakeep-web and karakeep-browser services appear to run correctly.

  • Rollback Attempt:
    Rolling back to v0.31.0 succeeds technically, but the application still does not start correctly afterward (services karakeep-workers and karakeep-web dead; karakeep-browser up and running).

Troubleshooting already attempted
Restarted the karakeep-workers service manually (no resolution).
Verified that the issue occurs regardless of the update method (web-admin or CLI).

Additional Information
I’ve been experiencing upgrade problems withe every upgrade since version 0.28.0.

If anyone has encountered similar issues or has insights into the karakeep-workers service failure, your guidance would be greatly appreciated. Let me know if further details or diagnostics are needed.

Share relevant logs or error messages

Update log:

https://paste.yunohost.org/raw/yezonojoqo

karakeep-workers unit log:

https://paste.yunohost.org/raw/bevuculifo

Restore log:

https://paste.yunohost.org/raw/irisekikid

After-rollback karakeep-web log:

After-rollback karakeep-workers log:

2

As a workaround, you can try this:

  1. upgrade karakeep via CLI with the --continue-on-failure flag.
  2. check the latest node.js 22 minor version installed on your server: ls -l /opt/node_n/n/versions/node/ (22.22.3 I guess ?)
  3. Replace 22.22.1 with this version in /etc/systemd/system/karakeep-workers.service
  4. systemctl daemon-reload
  5. systemctl restart karakeep-workers
3

Did not work for 0.32.0 since:ls -l /opt/node_n/n/versions/node/ returns 22.22.3 indeed

and 22.22.3 already in /etc/systemd/system/karakeep-workers.service, so nothing really to replace.

Your solution did the trick for the restored version though - so I’m back to 0.31.0.

0.32.0 still doesn’t work.

4

I kind of suspected that, so this log here doesn’t seem to match the karakeep-workers service after the upgrade :

5

what are the actual contents of /var/www/karakeep/.env, specifically the values of INFERENCE_ENABLE_AUTO_TAGGING and INFERENCE_ENABLE_AUTO_SUMMARIZATION. don’t paste the whole file as it may contain secrets.

Did you do any tweaking using config panel?

I’m asking because I just did fresh install of 0.31.0, upgraded to 0.32.0, changed settings using config panel and stuff still works :person_shrugging:

6

Both are commented out:

# --- AI Features (Booleans) ---
#INFERENCE_ENABLE_AUTO_TAGGING=1
#INFERENCE_ENABLE_AUTO_SUMMARIZATION=0
7

Can you uncomment them and change their respective values to true and false ?

8

I replaced both values pre-upgrade. Upgrade went fine but it made no difference.

Upgrade log:

https://paste.yunohost.org/raw/wevogimiho

Service logs:

Post upgrade I switched those values back to:

# --- AI Features (Booleans) ---
#INFERENCE_ENABLE_AUTO_TAGGING=1
#INFERENCE_ENABLE_AUTO_SUMMARIZATION=0

and restarted the unit. karakeep-workers started. I’m still getting Internal Server Error when trying to reach the app - despite the fact that all 3 apps services are up and running.

karakeep-web logs:

karakeep-browser logs:

karakeep-workers logs:

9

Ok, I think I resolved the issue: commenting out all the AI-related .env variables did the trick.
Not using any of these for the time being so not a big deal.

Thanks to all the involved.

10

Config panel handles these keys.

Did you try to set them “false” instead of “0”