Closed zenithyr closed 1 year ago
curl http://<ip>:2283/api/server-info/stats
returns
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.23.4</center>
</body>
</html>
Can you put in the .env
file LOG_LEVEL=debug
and see if you can pull additional information from the server container? It looks like the server cannot start up because, somehow the docker network in your stack cannot communicate with Typesense.
Is it your standard procedure to perform docker compose down
then docker volume prune
?
UPLOAD_LOCATION does point to a folder filled with data from previously. Not sure if it's related.
Is it the same data though?
Thanks for the quick turnaround.
Can you put in the
.env
fileLOG_LEVEL=debug
and see if you can pull additional information from the server container? It looks like the server cannot start up because, somehow the docker network in your stack cannot communicate with Typesense.
echo "LOG_LEVEL=debug" >> .env
. Then ensured the line is present in the file.tail -n5 .env
# Examples: http://localhost:3001, http://immich-api.example.com, etc
####################################################################################
LOG_LEVEL=debug
3. `docker compose down; docker compose up -d`
4. `docker ps | grep immich-server`
```bash
dcbcd7fac27c ghcr.io/immich-app/immich-server:release "/bin/sh start-micro…" 22 seconds ago Up 17 seconds 3001/tcp immich_microservices
3bc421247963 ghcr.io/immich-app/immich-server:release "/bin/sh start-serve…" 22 seconds ago Up 17 seconds 3001/tcp immich_server
docker logs 3bc421247963
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [RouterExplorer] Mapped {/album/:id, GET} route +0ms
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [RouterExplorer] Mapped {/album/:id/assets, DELETE} route +1ms
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [RouterExplorer] Mapped {/album/:id/user/:userId, DELETE} route +0ms
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [RouterExplorer] Mapped {/album/:id/download, GET} route +1ms
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [RouterExplorer] Mapped {/album/create-shared-link, POST} route +0ms
[Nest] 1 - 05/30/2023, 2:53:01 AM LOG [SearchService] Running bootstrap
Request #1685415181852: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685415181852: Sleeping for 4s and then retrying request...
Request #1685415181852: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685415181852: Sleeping for 4s and then retrying request...
Request #1685415181852: Request to Node 0 failed due to "ECONNABORTED timeout of 10000ms exceeded"
Request #1685415181852: Sleeping for 4s and then retrying request...
Request #1685415181852: Request to Node 0 failed due to "ECONNABORTED timeout of 10000ms exceeded"
Request #1685415181852: Sleeping for 4s and then retrying request...
Request #1685415181852: Request to Node 0 failed due to "ECONNABORTED timeout of 10000ms exceeded"
Request #1685415181852: Sleeping for 4s and then retrying request...
seems DEBUG level isn't working. Anything I was missing?
Is it your standard procedure to perform
docker compose down
thendocker volume prune
?
No, just this once in order to have a clean volume. I usually do docker compose down
followed by docker compose up -d
Same, well not really. I am getting 502 bad gateway after upgrading to 1.58.0. Re-pulled the new image and changed the docker-compose lines as mentioned in the release note, but now the web page won't load nor the android app would load my server url :(
Edit: my status page correctly shows the content info, but not loading the web page even with localip:2283 My issue is probably isolated, but not sure what it is after upgrading to 1.58 from 1.57.
Edit 2: solved it by adding the line 45 "entrypoint: ["/bin/sh", "./entrypoint.sh"]" back in to docker-compose.
UPLOAD_LOCATION does point to a folder filled with data from previously. Not sure if it's related.
Is it the same data though?
Yes. But in case it's the culprit, I changed it to a new path, restarted the container, and got the same error :( After restart I can see the new directory being created with nothing in it.
Please instruct how to print out more logs, thanks.
@dhanadhan Have you read the release note to make the appropriate changes to the docker-compose file since we changed a few things in it?
@dhanadhan Have you read the release note to make the appropriate changes to the docker-compose file since we changed a few things in it?
Yes, there were 3 changes. It didn't load the web page. But I have just resolved it by adding the line 45 back in.
@dhanadhan It wasn't the intention to keep that line and have the container working, it looks like you haven't pulled the new version?
In case it helps, this is the list of containers. They all look normal.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
beb903abea2f ghcr.io/immich-app/immich-proxy:release "/docker-entrypoint.…" About a minute ago Up About a minute 0.0.0.0:2283->8080/tcp, :::2283->8080/tcp immich_proxy
dd7a61c63d65 ghcr.io/immich-app/immich-server:release "/bin/sh start-serve…" About a minute ago Up About a minute 3001/tcp immich_server
655dabb49f9c ghcr.io/immich-app/immich-server:release "/bin/sh start-micro…" About a minute ago Up About a minute 3001/tcp immich_microservices
294c8e350e51 postgres:14 "docker-entrypoint.s…" About a minute ago Up About a minute 5432/tcp immich_postgres
4c8c30da73da ghcr.io/immich-app/immich-machine-learning:release "python src/main.py" About a minute ago Up About a minute immich_machine_learning
8dcefe72d626 ghcr.io/immich-app/immich-web:release "/bin/sh entrypoint.…" About a minute ago Up About a minute 3000/tcp immich_web
5076a8cc60e5 typesense/typesense:0.24.0 "/opt/typesense-serv…" 20 minutes ago Up 20 minutes 8108/tcp immich_typesense
4d9843482874 redis:6.2 "docker-entrypoint.s…" 20 minutes ago Up 20 minutes 6379/tcp immich_redis
@zenithyr Can you remove the logging
directive in the typesense container in the docker-compose file? Your typesense container has the issue.
FYI, after using docker compose down
it could remove all the containers so that when you perform docker volume prune
.
In case it helps, this is the list of containers. They all look normal.
This doesn't look normal as the typesense and redis container doesn't get restart with the same timestamp as other containers. Please bring all the containers down, and make sure that typesense and redis get brought down as well so when you bring up the whole stack, they would be able to communicate with each other.
@dhanadhan It wasn't the intention to keep that line and have the container working, it looks like you haven't pulled the new version?
Pretty sure i pulled the new image. Web page shows v1.58.0 correctly on the bottom left and working as of now with having line 45 "entrypoint: ["/bin/sh", "./entrypoint.sh"]" in the docker compose. Do I keep this change? It will probably stop working if I remove it.
@zenithyr Can you remove the
logging
directive in the typesense container in the docker-compose file? Your typesense container has the issue.FYI, after using
docker compose down
it could remove all the containers so that when you performdocker volume prune
.In case it helps, this is the list of containers. They all look normal.
This doesn't look normal as the typesense and redis container doesn't get restart with the same timestamp as other containers. Please bring all the containers down, and make sure that typesense and redis get brought down as well so when you bring up the whole stack, they would be able to communicate with each other.
Update docker-compose.yml
typesense:
container_name: immich_typesense
image: typesense/typesense:0.24.0
environment:
- TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
- TYPESENSE_DATA_DIR=/data
#logging:
# driver: none
volumes:
- tsdata:/data
restart: always
made sure to have down redis and typesense then up again.
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9cbb6c142af1 ghcr.io/immich-app/immich-proxy:release "/docker-entrypoint.…" 7 seconds ago Up 2 seconds 0.0.0.0:2283->8080/tcp, :::2283->8080/tcp immich_proxy d6054f9db2e0 ghcr.io/immich-app/immich-server:release "/bin/sh start-micro…" 7 seconds ago Up 4 seconds 3001/tcp immich_microservices a22e338d218f ghcr.io/immich-app/immich-server:release "/bin/sh start-serve…" 7 seconds ago Up 3 seconds 3001/tcp immich_server 01d7b7e89f54 redis:6.2 "docker-entrypoint.s…" 8 seconds ago Up 5 seconds 6379/tcp immich_redis 13b047cbec76 postgres:14 "docker-entrypoint.s…" 8 seconds ago Up 5 seconds 5432/tcp immich_postgres c49927afb7d4 ghcr.io/immich-app/immich-machine-learning:release "python src/main.py" 8 seconds ago Up 5 seconds immich_machine_learning 5b561bf8dbc2 ghcr.io/immich-app/immich-web:release "/bin/sh entrypoint.…" 8 seconds ago Up 5 seconds 3000/tcp immich_web a32e40169bb4 typesense/typesense:0.24.0 "/opt/typesense-serv…" 8 seconds ago Up 5 seconds 8108/tcp immich_typesense
The issue persists :(.
typesense logs looks like below
```bash
I20230530 03:21:37.153359 165 raft_meta.cpp:546] Saved single stable meta, path /data/state/meta term 21 votedfor 0.0.0.0:0:0 time: 9569
I20230530 03:21:47.154302 165 raft_server.cpp:545] Term: 21, last_index index: 10, committed_index: 0, known_applied_index: 3, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
W20230530 03:21:47.154343 165 raft_server.cpp:569] Single-node with no leader. Resetting peers.
I20230530 03:21:47.723843 169 node.cpp:1484] node default_group:192.168.16.3:8107:8108 term 21 start pre_vote
I20230530 03:21:47.723978 169 node.cpp:1549] node default_group:192.168.16.3:8107:8108 term 21 start vote and grant vote self
I20230530 03:21:47.740236 169 raft_meta.cpp:546] Saved single stable meta, path /data/state/meta term 22 votedfor 192.168.16.3:8107:8108 time: 16131
I20230530 03:21:47.740278 169 node.cpp:1783] node default_group:192.168.16.3:8107:8108 term 22 become leader of group 192.168.16.3:8107:8108
I20230530 03:21:47.748555 169 raft_server.h:273] Configuration of this group is 172.23.0.3:8107:8108
I20230530 03:21:47.748601 169 raft_server.h:273] Configuration of this group is 172.25.0.5:8107:8108
I20230530 03:21:47.748620 169 raft_server.h:273] Configuration of this group is 172.26.0.6:8107:8108
I20230530 03:21:47.748637 169 raft_server.h:273] Configuration of this group is 172.27.0.5:8107:8108
I20230530 03:21:47.748653 169 raft_server.h:273] Configuration of this group is 172.30.0.3:8107:8108
I20230530 03:21:47.748670 169 raft_server.h:273] Configuration of this group is 172.31.0.3:8107:8108
I20230530 03:21:47.748687 169 raft_server.h:273] Configuration of this group is 192.168.0.5:8107:8108
I20230530 03:21:47.748694 169 raft_server.h:273] Configuration of this group is 192.168.16.3:8107:8108
I20230530 03:21:47.748701 169 node.cpp:3142] node default_group:192.168.16.3:8107:8108 reset ConfigurationCtx, new_peers: 192.168.16.3:8107:8108, old_peers: 192.168.16.3:8107:8108
I20230530 03:21:47.748711 169 raft_server.h:256] Node becomes leader, term: 22
I20230530 03:21:57.155246 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:21:57.155386 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:07.156229 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:07.156322 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:17.157153 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:17.157231 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:27.158087 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:27.158147 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:37.159025 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:37.159099 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:38.035077 166 batched_indexer.cpp:279] Running GC for aborted requests, req map size: 0
I20230530 03:22:47.159945 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:47.160013 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:22:57.160825 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:22:57.160929 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:07.161732 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:07.161800 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:17.162842 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:17.162955 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:27.163966 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:27.164098 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:37.165251 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:37.165385 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:39.040940 166 batched_indexer.cpp:279] Running GC for aborted requests, req map size: 0
I20230530 03:23:47.166237 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:47.166321 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:23:57.167263 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:23:57.167353 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:24:07.168507 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:24:07.168588 207 raft_server.h:60] Peer refresh succeeded!
I20230530 03:24:17.169873 165 raft_server.cpp:545] Term: 22, last_index index: 11, committed_index: 11, known_applied_index: 11, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1
I20230530 03:24:17.170038 207 raft_server.h:60] Peer refresh succeeded!
@zenithyr What is the log now for the server? Maybe try restart your system?
@zenithyr What is the log now for the server? Maybe try restart your system?
Same as before
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [RouterExplorer] Mapped {/album/:id, GET} route +0ms
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [RouterExplorer] Mapped {/album/:id/assets, DELETE} route +0ms
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [RouterExplorer] Mapped {/album/:id/user/:userId, DELETE} route +1ms
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [RouterExplorer] Mapped {/album/:id/download, GET} route +0ms
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [RouterExplorer] Mapped {/album/create-shared-link, POST} route +1ms
[Nest] 1 - 05/30/2023, 3:58:39 AM LOG [SearchService] Running bootstrap
Request #1685419119631: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685419119631: Sleeping for 4s and then retrying request...
I then tried to set TYPESENSE_ENABLED=false
in the .env
file, and commented out typesense from docker-compose completely. Down the stack and up again. I saw no error from the server
[Nest] 1 - 05/30/2023, 4:04:52 AM LOG [RouterExplorer] Mapped {/album/create-shared-link, POST} route +1ms
[Nest] 1 - 05/30/2023, 4:04:52 AM LOG [NestApplication] Nest application successfully started +46ms
[Nest] 1 - 05/30/2023, 4:04:52 AM LOG [ImmichServer] Running Immich Server in PRODUCTION environment - version 1.58.0 - Listening on port: 3001
[Nest] 1 - 05/30/2023, 4:04:52 AM WARN [ImmichServer] Machine learning is enabled
[Nest] 1 - 05/30/2023, 4:04:52 AM WARN [ImmichServer] Search is disabled
But this time, while I still got the same 503 error by curl http://<ip>:2283
, I got some response on curl http://<ip>:2283/api/server-info/stats
: {"statusCode":401,"message":"Authentication required","error":"Unauthorized"}
It looks like the server cannot start up because, somehow the docker network in your stack cannot communicate with Typesense.
So is it safe to assume the 503 isn't related to typesense?
Okay, why don't we do this, please follow exactly the commands below.
Then let me know if all the logs look good.
Ah I notice you did docker pull
which is not the correct command to pull updates for all containers. It has to be docker compose pull
Based on the previous configurations, with typesense disabled:
user@omv ~/d/immich> docker compose down
user@omv ~/d/immich> docker container prune
user@omv ~/d/immich> docker compose pull
user@omv ~/d/immich> docker compose up
And then refresh the webpage or curl, got nothing but that status code 503...
Your immich-server
is starting up fine. Looking at the logs it looks like the immich-proxy
is started before immich-server
is ready to accept connections, which is why you get a 503
. Just restart the proxy container (after everything else has started) and you should be good to go.
Your
immich-server
is starting up fine. Looking at the logs it looks like theimmich-proxy
is started beforeimmich-server
is ready to accept connections, which is why you get a503
. Just restart the proxy container (after everything else has started) and you should be good to go.
Thanks for jumping in. I tried the following.
docker ps
ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dc12bee5c3f5 ghcr.io/immich-app/immich-proxy:release "/docker-entrypoint.…" 14 minutes ago Up 3 seconds 0.0.0.0:2283->8080/tcp, :::2283->8080/tcp immich_proxy
6e684e1fc572 ghcr.io/immich-app/immich-server:release "/bin/sh start-serve…" 14 minutes ago Up 5 seconds 3001/tcp immich_server
cc434814b002 ghcr.io/immich-app/immich-server:release "/bin/sh start-micro…" 14 minutes ago Up 4 seconds 3001/tcp immich_microservices
59d170627db2 redis:6.2 "docker-entrypoint.s…" 14 minutes ago Up 6 seconds 6379/tcp immich_redis
91d664d8b569 ghcr.io/immich-app/immich-web:release "/bin/sh entrypoint.…" 14 minutes ago Up 6 seconds 3000/tcp immich_web
08b07ae8acfb postgres:14 "docker-entrypoint.s…" 14 minutes ago Up 6 seconds 5432/tcp immich_postgres
b2380714154f ghcr.io/immich-app/immich-machine-learning:release "python src/main.py" 14 minutes ago Up 6 seconds immich_machine_learning
docker container restart dc12bee5c3f5
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dc12bee5c3f5 ghcr.io/immich-app/immich-proxy:release "/docker-entrypoint.…" 14 minutes ago Up 1 second 0.0.0.0:2283->8080/tcp, :::2283->8080/tcp immich_proxy
6e684e1fc572 ghcr.io/immich-app/immich-server:release "/bin/sh start-serve…" 14 minutes ago Up 20 seconds 3001/tcp immich_server
cc434814b002 ghcr.io/immich-app/immich-server:release "/bin/sh start-micro…" 14 minutes ago Up 20 seconds 3001/tcp immich_microservices
59d170627db2 redis:6.2 "docker-entrypoint.s…" 14 minutes ago Up 21 seconds 6379/tcp immich_redis
91d664d8b569 ghcr.io/immich-app/immich-web:release "/bin/sh entrypoint.…" 14 minutes ago Up 21 seconds 3000/tcp immich_web
08b07ae8acfb postgres:14 "docker-entrypoint.s…" 14 minutes ago Up 21 seconds 5432/tcp immich_postgres
b2380714154f ghcr.io/immich-app/immich-machine-learning:release "python src/main.py" 14 minutes ago Up 21 seconds immich_machine_learning
So the proxy is indeed restarted. And that 503 still didn't go away....
What are the latest immich-web logs and what hardware are you running this on?
What are the latest immich-web logs and what hardware are you running this on?
docker logs 91d664d8b569
Listening on 0.0.0.0:3000
Listening on 0.0.0.0:3000
I am running this on top of the OpenMediaVault 6.1.0-0.deb11.7-amd64, which sits on PromoxVE. Memory usage 8.7G/24G. The UPLOAD_LOCATION is on a RAID-0 ZFS drive.
There are some other docker containers like qBitTorrent, PhotoView running fine so far.
Things I can think of:
user@omv ~/d/immich> uname -r
6.1.0-0.deb11.7-amd64
user@omv ~/d/immich> lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 58
Model name: Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz
Stepping: 9
CPU MHz: 2500.016
BogoMIPS: 5000.03
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 16 MiB
L3 cache: 16 MiB
NUMA node0 CPU(s): 0-3
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Mitigation; PTE Inversion; VMX flush not necessary, SMT disabled
Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Mmio stale data: Unknown: No mitigations
Vulnerability Retbleed: Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Unknown: Dependent on hypervisor status
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_f
req pni pclmulqdq vmx ssse3 cx16 pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority ept vpid fsg
sbase tsc_adjust smep erms xsaveopt arat umip arch_capabilities
user@omv ~/d/immich> grep MemTotal /proc/meminfo
MemTotal: 24610032 kB
user@omv ~/d/immich> free -h
total used free shared buff/cache available
23Gi 8.6Gi 13Gi 18Mi 1.8Gi 14Gi
974Mi 0B 974Mi
user@omv ~/d/immich> lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Device 1234:1111 (rev 02)
00:03.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon
00:05.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
00:12.0 Ethernet controller: Red Hat, Inc. Virtio network device
00:1e.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
00:1f.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
01:01.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
01:02.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
01:03.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
01:04.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
02:1b.0 USB controller: Red Hat, Inc. QEMU XHCI Host Controller (rev 01)
One thing to note is that I have set up http proxy for docker server
user@omv ~/d/immich> sudo cat /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://<my local proxy ip>:<my port>/"
Environment="HTTPS_PROXY=http://<my local proxy ip>:<my port>/"
Environment="NO_PROXY=localhost,127.0.0.1,.example.com"
But even if I commented out above settings and run sudo systemctl daemon-reload;sudo systemctl restart docker
. The 503 error is still there.
Before the version upgrade (I forgot the old version), everything went on pretty well. And there hasn't been any hardware changes in between.
Can you please try to setup a new instance of Immich using stock setup? I have a feeling your proxy settings cause the issue
Can you please try to setup a new instance of Immich using stock setup? I have a feeling your proxy settings cause the issue
Sure. I dropped all proxy entries in the http-proxy.conf file.
user@omv ~> docker info | grep -I proxy # to confirm there is no proxy now.
(no output)
restarted by docker compose down and up -d. Then
user@omv ~> curl http://127.0.0.1:2283 | tail -n10
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1304 100 1304 0 0 793 0 0:00:01 0:00:01 --:--:-- 793
</head>
<body>
<div class="error">
<span class="status">500</span>
<div class="message">
<h1>Request failed with status code 503</h1>
</div>
</div>
</body>
</html>
Seems nobody else ran into similar issues that I am having. I will try to revert to an older version later. Will keep you posted. Please also let me know if you have anything else to try. Thanks.
Where is the 503 error coming from? You should see it in the web logs, proxy logs, or server logs. If those are clean then it is coming from something in front of immich-proxy.
Older version didn't work either. So I dropped everything including images, and start refresh from docker compose pull
.
Then I follow the guidance by docker logs immich_server --follow
.
After the whole stack is up, even before I make any web request, the server keeps printing out errors, and ends with something below
[Nest] 1 - 05/30/2023, 4:17:06 PM LOG [SearchService] Running bootstrap
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
Request #1685463426275: Request to Node 0 failed due to "undefined Request failed with HTTP code 503"
Request #1685463426275: Sleeping for 4s and then retrying request...
/usr/src/app/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23
var _this = _super.call(this, message) || this;
^
ServerError: Request failed with HTTP code 503
at ServerError.TypesenseError [as constructor] (/usr/src/app/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ServerError (/usr/src/app/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
at ApiCall.customErrorForResponse (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:347:21)
at /usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:204:58
at step (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
httpStatus: 503
}
I wonder if it's possible to find what that mystery request is so I can reproduce easier by go into the running container. Any hint is welcome.
This isn't a mystery request, this is the server trying to connect to typesense on start up.
I tested the same set up on a brand new virtual host and there is no problem. Closing the ticket for now.
OK I found it. @alextran1502 is correct, the 503 comes from the proxy.
~/.docker/config.json
/etc/systemd/system/docker.service.d/http-proxy.conf
Thanks to @jrasm91 who helped look into it!
I met same problem too, and immich works after disabled proxy. How can I let proxy and immich work together?
Hey @alextran1502 Im starting to see this on v1.88.2 i updated from v1.88.1 and now seem to take a bit for th server to come up. Then after a 1 or 2 web ui starts to work
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | [Nest] 7 - 11/22/2023, 6:44:43 PM LOG [MetadataService] Initialized local reverse geocoder with cities500
immich_microservices | [Nest] 7 - 11/22/2023, 6:44:43 PM LOG [SearchService] Running bootstrap
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_typesense | W20231122 18:45:21.251355 646 controller.cpp:1454] SIGINT was installed with 1
immich_typesense | W20231122 18:45:21.251394 646 raft_server.cpp:570] Single-node with no leader. Resetting peers.
immich_typesense | W20231122 18:45:21.251399 646 node.cpp:894] node default_group:172.19.0.3:8107:8108 set_peer from 172.20.0.3:8107:8108 to 172.19.0.3:8107:8108
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | Request #1700678683661: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_microservices | Request #1700678683661: Sleeping for 4s and then retrying request...
immich_server | Request #1700678670571: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
immich_server | Request #1700678670571: Sleeping for 4s and then retrying request...
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [TypesenseRepository] Schema up to date: assets/assets-v10
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [TypesenseRepository] Schema up to date: albums/albums-v2
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [TypesenseRepository] Schema up to date: faces/faces-v1
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [TypesenseRepository] Alias mapping: [{"collection_name":"faces-v1","name":"faces"},{"collection_name":"albums-v2","name":"albums"},{"collection_name":"assets-v10","name":"assets"}]
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [TypesenseRepository] Collections needing migration: {"assets":false,"albums":false,"faces":false}
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [NestApplication] Nest application successfully started +21ms
immich_microservices | [Nest] 7 - 11/22/2023, 6:45:27 PM LOG [ImmichMicroservice] Immich Microservices is listening on http://[::1]:3002 [v1.88.2] [PRODUCTION]
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [TypesenseRepository] Schema up to date: assets/assets-v10
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [TypesenseRepository] Schema up to date: albums/albums-v2
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [TypesenseRepository] Schema up to date: faces/faces-v1
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [TypesenseRepository] Alias mapping: [{"collection_name":"faces-v1","name":"faces"},{"collection_name":"albums-v2","name":"albums"},{"collection_name":"assets-v10","name":"assets"}]
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [TypesenseRepository] Collections needing migration: {"assets":false,"albums":false,"faces":false}
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [AppService] Feature Flags: {
immich_server | "clipEncode": true,
immich_server | "facialRecognition": true,
immich_server | "tagImage": true,
immich_server | "map": true,
immich_server | "reverseGeocoding": true,
immich_server | "sidecar": true,
immich_server | "search": true,
immich_server | "trash": true,
immich_server | "oauth": false,
immich_server | "oauthAutoLaunch": false,
immich_server | "passwordLogin": true,
immich_server | "configFile": false
immich_server | }
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [NestApplication] Nest application successfully started +13ms
immich_server | [Nest] 7 - 11/22/2023, 6:45:30 PM LOG [ImmichServer] Immich Server is listening on http://[::1]:3001 [v1.88.2] [PRODUCTION]
immich_server | [Nest] 7 - 11/22/2023, 6:45:34 PM LOG [CommunicationRepository] Websocket Connect: EqfRp3bwfldEe9qvAAAB
Heres what i see after starting up the docker
root@immich:/var/immich-app# docker logs immich_server --follow
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [NestFactory] Starting Nest application...
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +46ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] BullModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] ConfigHostModule dependencies initialized +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] DiscoveryModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] ScheduleModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] ConfigModule dependencies initialized +6ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] BullModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] ScheduleModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] BullModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] TypeOrmCoreModule dependencies initialized +227ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] InfraModule dependencies initialized +3ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] AppModule dependencies initialized +7ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [InstanceLoader] DomainModule dependencies initialized +17ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] ActivityController {/api/activity}: +131ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/activity, GET} route +3ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/activity/statistics, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/activity, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/activity/:id, DELETE} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AssetsController {/api/assets}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/assets, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AssetController {/api/asset}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/map-marker, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/memory-lane, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/random, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/download/info, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/download/archive, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/download/:id, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/statistics, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/time-buckets, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/time-bucket, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/jobs, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/restore, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/trash/empty, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/trash/restore, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/stack/parent, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/:id, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AssetController {/api/asset}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/upload, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/file/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/thumbnail/:id, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/curated-objects, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/curated-locations, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/search-terms, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/:deviceId, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/assetById/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/exist, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/asset/bulk-upload-check, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AppController {/api}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/.well-known/immich, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/custom.css, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/refresh-config, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AlbumController {/api/album}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/count, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id, PATCH} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id, DELETE} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id/assets, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id/assets, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id/users, PUT} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/album/:id/user/:userId, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] APIKeyController {/api/api-key}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/api-key, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/api-key, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/api-key/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/api-key/:id, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/api-key/:id, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AuditController {/api/audit}: +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/audit/deletes, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/audit/file-report, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/audit/file-report/checksum, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/audit/file-report/fix, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] AuthController {/api/auth}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/login, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/admin-sign-up, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/devices, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/devices, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/devices/:id, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/validateToken, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/change-password, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/auth/logout, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] JobController {/api/jobs}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/jobs, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/jobs/:id, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] LibraryController {/api/library}: +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id, PUT} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id/statistics, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id/scan, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/library/:id/removeOffline, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] OAuthController {/api/oauth}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/mobile-redirect, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/config, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/authorize, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/callback, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/link, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/oauth/unlink, POST} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] PartnerController {/api/partner}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/partner, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/partner/:id, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/partner/:id, PUT} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/partner/:id, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] SearchController {/api/search}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/search/person, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/search, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/search/explore, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] ServerInfoController {/api/server-info}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/ping, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/version, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/features, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/theme, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/config, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/statistics, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/server-info/media-types, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] SharedLinkController {/api/shared-link}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/me, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/:id, PATCH} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/:id, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/:id/assets, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/shared-link/:id/assets, DELETE} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] SystemConfigController {/api/system-config}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/system-config, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/system-config/defaults, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/system-config, PUT} route +1ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/system-config/storage-template-options, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/system-config/map/style.json, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RoutesResolver] TagController {/api/tag}: +0ms
[Nest] 7 - 11/22/2023, 6:52:19 PM LOG [RouterExplorer] Mapped {/api/tag, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id, PATCH} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id, DELETE} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id/assets, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id/assets, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/tag/:id/assets, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RoutesResolver] UserController {/api/user}: +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/info/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/me, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/profile-image, DELETE} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/:id, DELETE} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/:id/restore, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/profile-image, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/user/profile-image/:id, GET} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RoutesResolver] PersonController {/api/person}: +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person, PUT} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id, PUT} route +1ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id/statistics, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id/thumbnail, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id/assets, GET} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [RouterExplorer] Mapped {/api/person/:id/merge, POST} route +0ms
[Nest] 7 - 11/22/2023, 6:52:20 PM LOG [SearchService] Running bootstrap
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
Request #1700679140035: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1700679140035: Sleeping for 4s and then retrying request...
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [TypesenseRepository] Schema up to date: assets/assets-v10
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [TypesenseRepository] Schema up to date: albums/albums-v2
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [TypesenseRepository] Schema up to date: faces/faces-v1
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [TypesenseRepository] Alias mapping: [{"collection_name":"faces-v1","name":"faces"},{"collection_name":"albums-v2","name":"albums"},{"collection_name":"assets-v10","name":"assets"}]
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [TypesenseRepository] Collections needing migration: {"assets":false,"albums":false,"faces":false}
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [AppService] Feature Flags: {
"clipEncode": true,
"facialRecognition": true,
"tagImage": true,
"map": true,
"reverseGeocoding": true,
"sidecar": true,
"search": true,
"trash": true,
"oauth": false,
"oauthAutoLaunch": false,
"passwordLogin": true,
"configFile": false
}
[Nest] 7 - 11/22/2023, 6:53:20 PM LOG [NestApplication] Nest application successfully started +13ms
@AndyXheli Typesense on start-up would index the library to serve the quick search purpose, which might take a few minutes depending on the size of your gallery
Ah okay! yes i have about 300GB worth of data
The bug
The application worked perfectly fine in docker until yesterday when I upgraded to the latest with the added typesense feature. After
docker pull & docker compose up -d
, the web portal now complains "Request failed with status code 503".Tried to use the latest yaml and .env files with no luck. Commenting out typesense from docker-compose.yml and .env completely resulted the same error.
UPLOAD_LOCATION does point to a folder filled with data from previously. Not sure if it's related.
Please find container logs in the sections below.
The OS that Immich Server is running on
OpenMediaVault 6.1.0-0.deb11.7-amd64
Version of Immich Server
ghcr.io/immich-app/immich-server:release
Version of Immich Mobile App
not used here
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
3.
docker compose up -d
curl http://127.0.0.1:2283 # or from remotely by http://<ip>:2283
server
microservers
web
typesense