You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although I saw on docs that IPv6 is supported, and some Issues from other users point to problems of redis configuration, i think this is from immich container specifically to the redis module? PostgreSQL seems to resolve to the server without problems...
This is the failure from immich container:
Defaulted container "immich" out of: immich, debugger-bfcxx (ephem), debugger-85vlq (ephem)
Initializing Immich v1.119.0
Detected CPU Cores: 16
Starting api worker
Starting microservices worker
Error: getaddrinfo ENOTFOUND media-server-redis-master.media-server.svc.cluster.local
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3007,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'media-server-redis-master.media-server.svc.cluster.local'
}
[....]
missing 'error' handler on this Redis client
microservices worker error: MaxRetriesPerRequestError: Reached the max retries per request limit (which is 20). Refer to "maxRetriesPerRequest" option for details.
microservices worker exited with code 1
Configs:
values.yaml
immich:
fullnameOverride: immichenv:
# TZ: GMT# UMASK: 022# PUID: 1001# PGID: 1001IMMICH_PORT: 3001DB_HOSTNAME: 'media-server-postgresql.media-server.svc.cluster.local'REDIS_HOSTNAME: 'media-server-redis-master.media-server.svc.cluster.local'# IMMICH_PORT: 2283# IMMICH_HOST: "::"# IMMICH_LOG_LEVEL: "verbose"#'media-server-redis-master'# REDIS_PORT: 6379# DB_USERNAME: "immich"# DB_DATABASE_NAME: "immich"# DB_PASSWORD: "immich"## # -- You should provide your own secret outside of this helm-chart and use `postgresql.global.postgresql.auth.existingSecret` to provide credentials to the postgresql instance## IMMICH_MACHINE_LEARNING_URL: '{{ printf "http://%s-machine-learning:3003" .Release.Name }}'immich:
persistence:
library:
#enabled: trueexistingClaim: scrapbook#skipuninstall: truesecurityContext:
runAsGroup: 1001runAsUser: 1001postgresql:
enabled: falseimage:
repository: tensorchord/pgvecto-rstag: pg16-v0.3.0-rootless@sha256:d125f3aec02bfa66764432eae76e1098a3b0c6f8bf13db38f5af1156499c90b5global:
postgresql:
auth:
username: immichdatabase: immichpassword: immichredis:
enable: false # use our redis installationserver:
image:
tag: latest@sha256:24df1172544370826349159692d177ba22ca773c81857d36996a254c08422b95repository: ghcr.io/immich-app/immich-serverpullPolicy: Alwaysingress:
main:
enabled: falseannotations:
kubernetes.io/ingress.class: nginxcert-manager.io/issuer: "letsencrypt"nginx.ingress.kubernetes.io/ssl-redirect: "true"nginx.ingress.kubernetes.io/force-ssl-redirect: "true"#nginx.ingress.kubernetes.io/proxy-body-size: "0"hosts:
- host: your.dns.compaths:
#- path: "/immich"
- path: "/"tls:
- secretName: media-server-tlshosts:
- your.dns.netmachine-learning:
enabled: falseimage:
tag: v1.119.0@sha256:fa558ae8752eae335c5bfafeb5716dc60d0882f026350adb45e18ab28fbd36ae#tag: v1.117.0-armnn@ arm cpus and mali gpusrepository: ghcr.io/immich-app/immich-machine-learningpullPolicy: Always
For all fellows searching for this issue, and because there is lot's of pointers but nobody presents anything. For a single client configuration it should be something like:
The bug
immich connecting to redis on IPv6 only cluster fails.
Can create a debug container and connect without problems:
Although I saw on docs that IPv6 is supported, and some Issues from other users point to problems of redis configuration, i think this is from immich container specifically to the redis module? PostgreSQL seems to resolve to the server without problems...
This is the failure from immich container:
Configs:
values.yaml
values-temp.yaml
Chart.yaml
will try to figre out stuff
The OS that Immich Server is running on
Linux cyborg 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux
Version of Immich Server
v.1.119.0
Version of Immich Mobile App
NAN
Platform with the issue
Your docker-compose.yml content
See above
Your .env content
Reproduction steps
See above
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: