#immich_server exited with code 139

1 messages · Page 1 of 1 (latest)

feral hatch
#

On any version after v1.135.3 goes like into a boot loop with immich_server exited with code 139, and i can't figure out why. My logs, .yml and .env are attached due to character limits. I'm running it on openmediavault at the latest version. Any help would be greatly appreciated, thanks in advance!

📎 logs.txt 📎 Immich.env.txt 📎 docker-compose.yml.txt
frail cryptBOT
#

:wave: Hey @feral hatch,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

feral hatch
#

Also here is the docker compose ps, which i forgot

immich_machine_learning   ghcr.io/immich-app/immich-machine-learning:release                                                                                       "tini -- python -m i…"   immich-machine-learning   17 minutes ago   Up 17 minutes (healthy)           
immich_postgres           ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a   "/usr/local/bin/immi…"   database                  17 minutes ago   Up 17 minutes (healthy)           5432/tcp
immich_redis              docker.io/valkey/valkey:8-bookworm@sha256:facc1d2c3462975c34e10fccb167bfa92b0e0dbd992fc282c29a61c3243afb11                               "docker-entrypoint.s…"   redis                     17 minutes ago   Up 17 minutes (healthy)           6379/tcp
immich_server             ghcr.io/immich-app/immich-server:v1.137.3                                                                                                "tini -- /bin/bash -…"   immich-server             17 minutes ago   Restarting (139) 48 seconds ago ```

idk how to make it more readable in discord im sorry
#

Also the System runs on a mini PC with an Intel N100 and 16GB of RAM, as already said with OpenMediaVault as OS. I currently use a USB HDD as a temporary solution, but the database is on a M.2 NVMe SSD.

Disk /dev/sda: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: TWSC TSC10N512-F
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: [REDACTED]

Device     Start        End    Sectors   Size Type
/dev/sda1   2048 1000215182 1000213135 476,9G Linux filesystem


Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: External USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: [REDACTED]

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 3907029134 3907027087  1,8T Linux filesystem


Disk /dev/sdc: 30 GiB, 32212254720 bytes, 62914560 sectors
Disk model: Premium Line
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: [REDACTED]

Device        Start      End  Sectors  Size Type
/dev/sdc1      2048  1050623  1048576  512M EFI System
/dev/sdc2   1050624 60913663 59863040 28,5G Linux filesystem
/dev/sdc3  60913664 62912511  1998848  976M Linux swap```
# 
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
udev            7,7G       0  7,7G    0% /dev
tmpfs           1,6G    3,3M  1,6G    1% /run
/dev/sdc2        28G     20G  7,0G   74% /
tmpfs           7,7G       0  7,7G    0% /dev/shm
tmpfs           5,0M       0  5,0M    0% /run/lock
efivarfs        192K     95K   93K   51% /sys/firmware/efi/efivars
/dev/sda1       469G    2,9G  466G    1% /srv/dev-disk-by-uuid-f0c19ae3-a365-4038-859c-538618ff751c
/dev/sdb1       1,8T    156G  1,7T    9% /srv/dev-disk-by-uuid-d6772b7b-8892-461e-b916-3f38f3522f4d
/dev/sdc1       511M    148K  511M    1% /boot/efi
tmpfs           7,7G     12K  7,7G    1% /tmp
folder2ram      7,7G    504M  7,2G    7% /var/log
folder2ram      7,7G       0  7,7G    0% /var/tmp
folder2ram      7,7G    764K  7,7G    1% /var/lib/openmediavault/rrd
folder2ram      7,7G     16K  7,7G    1% /var/spool
folder2ram      7,7G     15M  7,7G    1% /var/lib/rrdcached
folder2ram      7,7G    4,0K  7,7G    1% /var/lib/monit
folder2ram      7,7G     12K  7,7G    1% /var/cache/samba
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/b375e468a43b680882c89f336a1eeb645978ded07f3bc27e095c33e7f44500db/merged
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/d282931b3a9d1d747e48c2e2673a9a06c9d5ed7ec2f778dcf646594b22da4873/merged
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/df25b18ce3736ba04deec9782f2bd48aaadcbd4c4cdbe9c70e589eed748542a5/merged
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/3cbf91e3767a987e77f3a6e1e43aee1f5e03d4c5ab106c60eabbdbf8c84a7a56/merged
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/755c6607aae009dc537d3c9a31fa07629b52afd64f708198c1b3294e32d4d843/merged
overlay          28G     20G  7,0G   74% /var/lib/docker/overlay2/bd98a76a53a4898f553f51a894b388bd94d6b03cbe2aa0c758afe866a62e6ca2/merged```
frail cryptBOT
mystic barn
#

Can you bring the entire stack down docker compose down. Then try and do docker compose up and see what it says?

feral hatch
mystic barn
#

Honestly I have no idea, the logs just exit lol. Very strange

feral hatch
#

A remove of the container and than rebuilding solved the issue :)