Xargon
Xargon
Explore posts from servers
HHomarrIImmich
PostsComments
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Thanks for your support, really 🙂
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
I can see the webpage now, thanks a lot, was definitely that
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
YES!
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
I try
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Ah yes
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
can I add it to the env?
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
(just not the mounted picture folder)
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
I don't care deleting all the data as I never reached the Immich screen yet
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Well technically yes as it's a new deploy (first time) and I changed it, but probably postgres came up with the default password once
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
immich_server is not producing logs
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
however not yet running
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
I run docker with sudo (because old configs on my server, when I will migrate I will fix it) and the posgtres folder is now a+wrx
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
previous: 
2025-04-10 10:25:09.368 JST [48] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-10 10:25:09.374 JST [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-10 10:25:09.462 JST [50] LOG:  database system was shut down at 2025-04-10 10:25:05 JST
2025-04-10 10:25:09.476 JST [48] LOG:  database system is ready to accept connections
2025-04-10 10:25:10.966 JST [48] LOG:  received fast shutdown request
2025-04-10 10:25:10.973 JST [48] LOG:  aborting any active transactions
2025-04-10 10:25:10.975 JST [48] LOG:  background worker "logical replication launcher" (PID 57) exited with exit code 1
2025-04-10 10:25:10.977 JST [52] LOG:  shutting down
2025-04-10 10:25:11.036 JST [48] LOG:  database system is shut down
2025-04-10 10:25:09.368 JST [48] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-10 10:25:09.374 JST [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-10 10:25:09.462 JST [50] LOG:  database system was shut down at 2025-04-10 10:25:05 JST
2025-04-10 10:25:09.476 JST [48] LOG:  database system is ready to accept connections
2025-04-10 10:25:10.966 JST [48] LOG:  received fast shutdown request
2025-04-10 10:25:10.973 JST [48] LOG:  aborting any active transactions
2025-04-10 10:25:10.975 JST [48] LOG:  background worker "logical replication launcher" (PID 57) exited with exit code 1
2025-04-10 10:25:10.977 JST [52] LOG:  shutting down
2025-04-10 10:25:11.036 JST [48] LOG:  database system is shut down
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
2025-04-10 10:25:11.140 JST [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-10 10:25:11.141 JST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-10 10:25:11.141 JST [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-10 10:25:11.151 JST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-10 10:25:11.166 JST [68] LOG:  database system was shut down at 2025-04-10 10:25:11 JST
2025-04-10 10:25:11.182 JST [1] LOG:  database system is ready to accept connections
2025-04-10 10:25:11.140 JST [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-10 10:25:11.141 JST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-10 10:25:11.141 JST [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-10 10:25:11.151 JST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-10 10:25:11.166 JST [68] LOG:  database system was shut down at 2025-04-10 10:25:11 JST
2025-04-10 10:25:11.182 JST [1] LOG:  database system is ready to accept connections
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Ah ok sorry now I understood: I missed that there was a ./postgres mount point in the env, ok yes, I found the folder and I got data inside, 27 items @bo0tzz @Alex
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
My /mnt folder is empty in me immich_server container
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Hmm not very useful, yeah: 
Initializing Immich v1.131.3
DEBUG: cgroup v2 detected.
DEBUG: No CPU limits set.
Detected CPU Cores: 8
Starting api worker
Starting microservices worker
[Nest] 7  - 04/09/2025, 10:37:16 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: TypeError: Cannot read properties of undefined (reading 'replace'), stack: TypeError: Cannot read properties of undefined (reading 'replace')
    at queryError (/usr/src/app/node_modules/postgres/cjs/src/connection.js:389:48)
    at errored (/usr/src/app/node_modules/postgres/cjs/src/connection.js:384:17)
    at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:318:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
microservices worker exited with code 1
Killing api process
Initializing Immich v1.131.3
DEBUG: cgroup v2 detected.
DEBUG: No CPU limits set.
Detected CPU Cores: 8
Starting api worker
Starting microservices worker
[Nest] 7  - 04/09/2025, 10:37:16 AM     LOG [Microservices:EventRepository] Initialized websocket server
microservices worker error: TypeError: Cannot read properties of undefined (reading 'replace'), stack: TypeError: Cannot read properties of undefined (reading 'replace')
    at queryError (/usr/src/app/node_modules/postgres/cjs/src/connection.js:389:48)
    at errored (/usr/src/app/node_modules/postgres/cjs/src/connection.js:384:17)
    at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:318:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
microservices worker exited with code 1
Killing api process
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
Yes, the query returned a schema
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
ok, they seems to be rachable: 
# ping database
PING database (172.24.0.3) 56(84) bytes of data.
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=2 ttl=64 time=0.080 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=4 ttl=64 time=0.053 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=5 ttl=64 time=0.045 ms
^C
--- database ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4094ms
rtt min/avg/max/mdev = 0.045/0.066/0.106/0.023 ms
# ping redis
PING redis (172.24.0.2) 56(84) bytes of data.
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=1 ttl=64 time=0.112 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=2 ttl=64 time=0.043 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=3 ttl=64 time=0.044 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=4 ttl=64 time=0.044 ms
^C
--- redis ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3086ms
rtt min/avg/max/mdev = 0.043/0.060/0.112/0.029 ms
# ping database
PING database (172.24.0.3) 56(84) bytes of data.
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=2 ttl=64 time=0.080 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=4 ttl=64 time=0.053 ms
64 bytes from immich_postgres.immich_default (172.24.0.3): icmp_seq=5 ttl=64 time=0.045 ms
^C
--- database ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4094ms
rtt min/avg/max/mdev = 0.045/0.066/0.106/0.023 ms
# ping redis
PING redis (172.24.0.2) 56(84) bytes of data.
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=1 ttl=64 time=0.112 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=2 ttl=64 time=0.043 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=3 ttl=64 time=0.044 ms
64 bytes from immich_redis.immich_default (172.24.0.2): icmp_seq=4 ttl=64 time=0.044 ms
^C
--- redis ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3086ms
rtt min/avg/max/mdev = 0.043/0.060/0.112/0.029 ms
72 replies
IImmich
Created by Xargon on 4/8/2025 in #help-desk-support
Microservices fail to run
at least, the things that I defined are defined
72 replies