#server crashing because it's running out of memory (after 1.132.0 update)

1 messages · Page 1 of 1 (latest)

nova wedge
#

my machine is not very powerful (celeron n5095, it's a QNAP ts-464 NAS) but it handles immich OK with its 16GB RAM (running many containers at once). After this last update (1.131.3 --> 1.132.0) it crashes apparently because it runs out of memory, just minutes after starting the server. The immich_server container is the one that crashes, the rest is apparently OK. Maybe it is worth noting i changed the redis container to the new "valkey" one.

    at [kOnExit] (node:internal/worker:314:26)
    at Worker.<computed>.onexit (node:internal/worker:230:20)
microservices worker exited with code 1
Killing api process

this is the console output on verbose logging.
I'm not sure this is an immich problem, but I feel it is not some weird thing about my NAS. I'm gonna restart everything and try to discard other problems rn, but if i can get some help it would be appreciated :D

untold flameBOT
#

:wave: Hey @nova wedge,

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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: 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.

nova wedge
#

wait it may be one thing i enabled uhhhhh

#

alright i concluded that enabling the EXPERIMENTAL option "library monitoring" (i think it's named like that, not sure because I have Immich in spanish) made Immich crash

#

kinda embarassing ngl

#

i'd like to know if that option actually is being worked on or if its just not good enough compared with just scanning the library periodically or what but mmehhhh future will tell

#

for now its all ok thank yall devs for making Immich it's great have a good day