[BUG] 500 getaddrinfo ENOTFOUND immich-server #2055

MozPri · 2023-03-23T10:18:12Z

The bug

Can't access Immich web page since version v1.51.0.
I get 500 getaddrinfo ENOTFOUND immich-server error.

_immich_server_logs.txt

The OS that Immich Server is running on

Debian 11

Version of Immich Server

v1.51.2

Version of Immich Mobile App

v1.51.0

Platform with the issue

Server
Web
Mobile

Your docker-compose.yml content

Latest from the docs

Your .env content

Latest from the docs

Reproduction steps

1. Install Immich with Portainer or docker-compose
2. Go to the Immich web page

Additional information

No response

bo0tzz · 2023-03-23T10:20:01Z

Is the typesense container running? The server can't reach it.

MozPri · 2023-03-23T10:27:49Z

It's running if I add restart: always. But it's not running without it.

Edit: Actually it's not running. Just restarting...

bo0tzz · 2023-03-23T10:56:21Z

You'll need to enable logging on the typesense container to figure out why it's having trouble starting. Either way this is not a problem in Immich, so I'll close this issue.

tinju87 · 2023-03-23T10:56:29Z

Same problem with docker-compose running on portainer.
"Failure Unable to retrieve container logs" for typesense container

tinju87 · 2023-03-23T11:03:13Z

TYPESENSE_API_KEY is missing in the env file and needed by typesense container.
Adding TYPESENSE_API_KEY to the env with whatever value worked for me.

Edit: Please also mention how to update to latest version using portainer in the docs.

MozPri · 2023-03-23T12:31:24Z

It seems that typesense requires a CPU with AVX support, which I don't have...
typesense/typesense#423 (comment)

Maybe this should be mentioned in sys requirements.

bo0tzz · 2023-03-23T12:47:39Z

Good find, I think we weren't aware of that! We are planning to make typesense an optional component in a future release.

Peda1996 · 2023-03-24T21:01:33Z

I have the same problem, after updating to the newest version, my immich instance (proxmox instance: debian 5.10.162-1) won't boot up.

getaddrinfo ENOTFOUND immich-server
Where can I find log files, that I can attach to that issue? Im using a dell wyse 5070 thin client as my system.

edit: I'm having the same issues with the typesense_api_key? How can I fix this?

MozPri · 2023-03-25T07:10:59Z

@Peda1996 Try disabling machine learning and typesense.
Add this to env variables:

IMMICH_MACHINE_LEARNING_URL=false
TYPESENSE_ENABLED=false

Logs:
https://documentation.immich.app/docs/guides/docker-help#logs

florihupf · 2023-03-26T07:10:39Z

Running into the same thing.

Should this be re-opened?

florihupf · 2023-03-26T07:27:01Z

Ah, never mind. Didn't realize I need to update .env.

florihupf · 2023-03-26T16:04:53Z

Dang it, I got it all working and that search is SO SUPER AWESOME!

TYTYTYTY!

Peda1996 · 2023-03-26T16:07:19Z

Oh, sorry forgot to mention that I already fixed it with the help of discord. Fixed it as followed: 1. add these to .env TYPESENSE_API_KEY=some-random-text 2. exchange your docker compose for the newest version Now just update like you would regularly update the service: 1. docker compose pull 2. docker compose up -d Florian Sauer ***@***.***> schrieb am So., 26. März 2023, 18:05:

…

Dang it, I got it all working and that search is SO SUPER AWESOME! TYTYTYTY! — Reply to this email directly, view it on GitHub <#2055 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANU6NLIBTOTWIAXHM3UACLW6BZL7ANCNFSM6AAAAAAWE7OKFU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Snuupy · 2023-04-23T02:06:37Z

@bertmelis do you think we can get a non-avx image working here?

bertmelis · 2023-04-23T11:44:25Z

I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens.

Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes.
(changes: replace docker by podman and satisfy SELinux, you might not have to do this)

bertmelis · 2023-04-23T15:18:54Z

So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image.

On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers.

I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for your cpu.

I'm happy to write the instructions if you need help.

Snuupy · 2023-04-23T15:26:47Z

I'll give it a try! Thanks!

Snuupy · 2023-04-23T17:36:34Z

How do you get docker to reference the locally built typesense image in the compose file?

My typesense build worked after running the command several times due to some checksums not working. Eventually it did build though (not sure how long it took, walked away and got some food, when I came back build was done). It was tagged by default as typesense/typesense:nightly, which I re-tagged as typesense (in attempts of trying to make it not pull latest from dockerhub).

However, when I run docker compose pull, docker will complain that the repo typesense does not exist (which rightfully so, it does not on dockerhub). How do I get pull to skip typesense and provide a local image to be used instead? up -d works in the meantime.

bertmelis · 2023-04-23T17:42:45Z

This should go in your composefile:

image: localhost/typesense/typesense:nightly

If you omit the localhost, it searches in the (online) registries as found in your configuration files.

Snuupy · 2023-04-23T17:47:02Z

If I paste that in, I get: Error response from daemon: error unmarshalling content: invalid character '<' looking for beginning of value

  typesense:
    container_name: immich_typesense
    # image: typesense/typesense:0.24.0
    image: localhost/typesense/typesense:nightly
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    # logging:
    #   driver: none
    volumes:
      - tsdata:/data
    restart: always

bertmelis · 2023-04-23T17:59:17Z

Sorry, I'm using Podman, not Docker. I'm not familiar with your error.

Can you run the image as-is, outside of the Immich stack?

Snuupy · 2023-04-23T18:00:42Z

Via docker run? I don't see why that wouldn't work. It's when I pull that it tries to fetch an image remotely but I want it to use the local one instead.

bertmelis · 2023-04-23T18:10:42Z

Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image.

docker/compose#3660

Snuupy · 2023-04-23T18:15:04Z

Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image.

docker/compose#3660

Wait - but I need to pull to update immich

~~I did the build workaround for now~~

Edit: pull_policy: never is likely more correct docker/compose#3660 (comment)

rkononov · 2023-08-06T16:50:55Z

I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens.

Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes.
(changes: replace docker by podman and satisfy SELinux, you might not have to do this)

Could you please share the changes you introduced?

bertmelis · 2023-08-06T19:18:39Z

I'm using postman on a SELinux-enabled machine.

The two changes:

replaced docker command with podman command
added :Z flags to volume mounts

55nevets · 2023-11-09T17:35:49Z

So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image.

On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers.

I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for your cpu.

I'm happy to write the instructions if you need help.

@bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install?

bertmelis · 2023-11-09T20:51:03Z

I'm still running it. For me it is sufficient. It might take a tad longer but it's a background task. It still processes the pictures faster than I shoot them.

I don't know how I built the container but I might find some leftovers on my home server... Stay tuned.

Snuupy · 2023-11-09T21:00:01Z

@bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install?

fyi you need to build this version: https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml#L55C4-L55C4

please see: #300 (comment)

Just follow these instructions: https://github.com/typesense/typesense/tree/v0.24.1#build-from-source

bertmelis · 2023-11-10T07:47:16Z

ah yes. Typesense is on v0.25 but Immich uses v0.24. The instructions to build it yourself are extremely simple: just download/clone the Typesense repo with the correct version and execute the script.

756yang · 2023-11-22T11:06:27Z

After my inspection, the official archive compiled by typesense supports most x64 platforms. Based on the platform instruction set, it requires at least SSE2, SSSE3, SSE4.1 support, and may require SSE3 and SSE4.2 support.

The AVX instruction set is additional and not necessarily required.

MozPri added bug labels Mar 23, 2023

bo0tzz closed this as completed Mar 23, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] 500 getaddrinfo ENOTFOUND immich-server #2055

[BUG] 500 getaddrinfo ENOTFOUND immich-server #2055

MozPri commented Mar 23, 2023

bo0tzz commented Mar 23, 2023

MozPri commented Mar 23, 2023 •

edited

Loading

bo0tzz commented Mar 23, 2023

tinju87 commented Mar 23, 2023 •

edited

Loading

tinju87 commented Mar 23, 2023 •

edited

Loading

MozPri commented Mar 23, 2023

bo0tzz commented Mar 23, 2023

Peda1996 commented Mar 24, 2023 •

edited

Loading

MozPri commented Mar 25, 2023

florihupf commented Mar 26, 2023

florihupf commented Mar 26, 2023

florihupf commented Mar 26, 2023

Peda1996 commented Mar 26, 2023 via email

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023 •

edited

Loading

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023 •

edited

Loading

Snuupy commented Apr 23, 2023 •

edited

Loading

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023 •

edited

Loading

rkononov commented Aug 6, 2023

bertmelis commented Aug 6, 2023

55nevets commented Nov 9, 2023

bertmelis commented Nov 9, 2023

Snuupy commented Nov 9, 2023

bertmelis commented Nov 10, 2023

756yang commented Nov 22, 2023

[BUG] 500 getaddrinfo ENOTFOUND immich-server #2055

[BUG] 500 getaddrinfo ENOTFOUND immich-server #2055

Comments

MozPri commented Mar 23, 2023

The bug

The OS that Immich Server is running on

Version of Immich Server

Version of Immich Mobile App

Platform with the issue

Your docker-compose.yml content

Your .env content

Reproduction steps

Additional information

bo0tzz commented Mar 23, 2023

MozPri commented Mar 23, 2023 • edited Loading

bo0tzz commented Mar 23, 2023

tinju87 commented Mar 23, 2023 • edited Loading

tinju87 commented Mar 23, 2023 • edited Loading

MozPri commented Mar 23, 2023

bo0tzz commented Mar 23, 2023

Peda1996 commented Mar 24, 2023 • edited Loading

MozPri commented Mar 25, 2023

florihupf commented Mar 26, 2023

florihupf commented Mar 26, 2023

florihupf commented Mar 26, 2023

Peda1996 commented Mar 26, 2023 via email

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023 • edited Loading

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023 • edited Loading

Snuupy commented Apr 23, 2023 • edited Loading

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023

bertmelis commented Apr 23, 2023

Snuupy commented Apr 23, 2023 • edited Loading

rkononov commented Aug 6, 2023

bertmelis commented Aug 6, 2023

55nevets commented Nov 9, 2023

bertmelis commented Nov 9, 2023

Snuupy commented Nov 9, 2023

bertmelis commented Nov 10, 2023

756yang commented Nov 22, 2023

MozPri commented Mar 23, 2023 •

edited

Loading

tinju87 commented Mar 23, 2023 •

edited

Loading

tinju87 commented Mar 23, 2023 •

edited

Loading

Peda1996 commented Mar 24, 2023 •

edited

Loading

bertmelis commented Apr 23, 2023 •

edited

Loading

bertmelis commented Apr 23, 2023 •

edited

Loading

Snuupy commented Apr 23, 2023 •

edited

Loading

Snuupy commented Apr 23, 2023 •

edited

Loading