Problems with startup after updating from 1.79.1
I have been running Immich on a fairly weak laptop. Docker has about 6GB RAM available, but all containers were running fine on 1.79.1
After updating I am getting typesense errors:
Single-node with no leader. Resetting peers.
... is in state ERROR, can't reset_peer
This keeps looping. I tried freeing up memory by disabling machine learning, but the same kept happening.
If I try running the migrate task or generate missing thumbnails task there are lots of errors and the jobs never actually execute.
I think there is something new hogging up the RAM. Did the default reverse geocoding setting change when it was moved into the settings menu?
3 Replies
2023-10-04 02:11:28 immich_typesense | I20231004 06:11:28.462838 262 raft_server.cpp:546] Term: 201, last_index index: 89127, committed_index: 89127, known_applied_index: 88448, applying_index: 0, queued_writes: 298, pending_queue_size: 0, local_sequence: 1224089
2023-10-04 02:11:28 immich_typesense | W20231004 06:11:28.462932 262 raft_server.cpp:570] Single-node with no leader. Resetting peers.
2023-10-04 02:11:28 immich_typesense | W20231004 06:11:28.462949 262 node.cpp:866] node default_group:172.20.0.7:8107:8108 is in state ERROR, can't reset_peer
2023-10-04 02:11:28 immich_microservices | Request #1696399741338: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
2023-10-04 02:11:28 immich_microservices | Request #1696399741338: Sleeping for 4s and then retrying request...
2023-10-04 02:11:29 immich_microservices | Request #1696399850309: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
2023-10-04 02:11:29 immich_microservices | Request #1696399850309: Sleeping for 4s and then retrying request...
2023-10-04 02:11:32 immich_microservices | [Nest] 7 - 10/04/2023, 6:11:32 AM ERROR [TypesenseRepository] Unable to index documents
2023-10-04 02:11:32 immich_microservices | [Nest] 7 - 10/04/2023, 6:11:32 AM LOG [TypesenseRepository] []
this is a small sample of output
I tried updating to 1.81.1 and I am still getting very similar errors, any ideas on what to do?
This is what happens if I only run the Typesense container and nothing else.
2023-10-05 16:10:08 immich_typesense | /typesense/external-Linux/s2geometry-efb124d8eaf3433323d3e877dedd5e94a63339a3/src/s2/s2latlng.cc:37 ERROR Invalid S2LatLng in S2LatLng::ToPoint: [-79.9462000, 286.7789920]
2023-10-05 16:10:18 immich_typesense | E20231005 20:10:18.365083 262 raft_server.cpp:620] 1385 lagging entries > healthy read lag of 1000
2023-10-05 16:10:18 immich_typesense | E20231005 20:10:18.365149 262 raft_server.cpp:632] 1385 lagging entries > healthy write lag of 500
2023-10-05 16:10:22 immich_typesense | I20231005 20:10:22.365665 262 raft_server.cpp:546] Term: 208, last_index index: 89132, committed_index: 89132, known_applied_index: 87563, applying_index: 87749, queued_writes: 108, pending_queue_size: 0, local_sequence: 1102735
2023-10-05 16:10:22 immich_typesense | W20231005 20:10:22.365721 262 node.cpp:811] [default_group:172.18.0.2:8107:8108 ] Refusing concurrent configuration changing
Seems like its data may have gotten corrupted. Try deleting the typesense volume and restarting the stack
@bo0tzz Thank you! That worked 🙂