bug: Bonfire using 44% CPU and libssl3 missing. #67

Closed
opened 2026-02-16 12:51:19 -05:00 by yindo · 2 comments
Owner

Originally created by @poggingfish on GitHub (Sep 7, 2024).

What happened?

january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
january-1        | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

after updating using docker-compose pull
it was working just fine before.

Originally created by @poggingfish on GitHub (Sep 7, 2024). ### What happened? ``` january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory january-1 | ./january: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory ``` after updating using `docker-compose pull` it was working just fine before.
yindo added the bug label 2026-02-16 12:51:19 -05:00
yindo closed this issue 2026-02-16 12:51:19 -05:00
Author
Owner

@DeclanChidlow commented on GitHub (Sep 9, 2024):

Do you use AutoMod on this self hosted instance?

Also, you can temporarily fix the January issue by pinning it to 0.3.5 until a proper fix is released.

  # Metadata and image proxy (january)
  january:
    image: ghcr.io/revoltchat/january:0.3.5
    depends_on:
      - caddy
    restart: always
@DeclanChidlow commented on GitHub (Sep 9, 2024): Do you use AutoMod on this self hosted instance? Also, you can temporarily fix the January issue by pinning it to 0.3.5 until a proper fix is released. ``` # Metadata and image proxy (january) january: image: ghcr.io/revoltchat/january:0.3.5 depends_on: - caddy restart: always ```
Author
Owner

@poggingfish commented on GitHub (Sep 9, 2024):

Changing the version of january back fixed the issue.

@poggingfish commented on GitHub (Sep 9, 2024): Changing the version of january back fixed the issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#67