Immich crashes: libxml2: getentropy failed with error code 38 -> immich_server exited with code 134 #21835
Replies: 5 comments
-
|
Probably related: What's the kernel version you're running? My first thoughts are we could maybe try updating some deps but I think this is not at the core an Immich issue. |
Beta Was this translation helpful? Give feedback.
-
Synology DSM 6.2.4-25556 Update 8 |
Beta Was this translation helpful? Give feedback.
-
|
I'm not running on latest DSM 7.1.x for my model, but AFAIK that uses the same kernel version. claude.ai suggested to do: So added this envvar and volume mapping to my |
Beta Was this translation helpful? Give feedback.
-
|
unfortunately that didn't help. Again, compose down/up resolved it. That failure really makes a change to the container that will result in restarting the container to fail. |
Beta Was this translation helpful? Give feedback.
-
|
I'm experiencing this same issue on DSM 7.2.2. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
Last relevant logs:
After this, immich will keep restarting and not recover.
It requires
docker-compose downthendocker-compose up.This seems to imply that some state in the immich container causes startup to fail as recreating the container makes it start again.
The OS that Immich Server is running on
Synology DSM 6.2 Docker
Version of Immich Server
v1.135.3
Version of Immich Mobile App
NA
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions