southyfromtassie
IImmich
•Created by Eazy E on 7/18/2023 in #help-desk-support
Explore Not Loading
The error seems to appear constantly after around ~1hour. This is recuring in the Typsense logs once the error appears:
W20230718 12:07:26.904009 646 raft_server.cpp:570] Single-node with no leader. Resetting peers.
W20230718 12:07:26.904014 646 node.cpp:866] node default_group:172.22.0.4:8107:8108 is in state ERROR, can't reset_peer
I20230718 12:07:36.904918 646 raft_server.cpp:546] Term: 3, last_index index: 6268, committed_index: 6268, known_applied_index: 6268, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 53234
W20230718 12:07:36.904953 646 raft_server.cpp:570] Single-node with no leader. Resetting peers.
W20230718 12:07:36.904963 646 node.cpp:866] node default_group:172.22.0.4:8107:8108 is in state ERROR, can't reset_peer
I20230718 12:07:46.906127 646 raft_server.cpp:546] Term: 3, last_index index: 6268, committed_index: 6268, known_applied_index: 6268, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 53234
19 replies
IImmich
•Created by Eazy E on 7/18/2023 in #help-desk-support
Explore Not Loading
Commented the logging section out and updated the stack. The recreation brought the Typsense server back online, but the logs are now visible. Will wait for the error to re-occur and then check the Typesense logs
19 replies
IImmich
•Created by Eazy E on 7/18/2023 in #help-desk-support
Explore Not Loading
From the Unraid UI, the log window just closes on the Typesense container (works on all other containters). Reverted to the CLI via Unraid Terminal and got:
"Error response from daemon: configured logging driver does not support reading"
Any ideas?
19 replies
IImmich
•Created by Eazy E on 7/18/2023 in #help-desk-support
Explore Not Loading
Issue re-appeared within an hour and appears to be a Typesense error:
ServerError: Request failed with HTTP code 503 | Server said: Not Ready or Lagging
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)
19 replies
IImmich
•Created by Eazy E on 7/18/2023 in #help-desk-support
Explore Not Loading
I am getting the same issue here on Unraid. Fresh install today. Explore was working when only a few hundred assets loaded. Now there are close to 2,000 and getting this error.
19 replies