Executor - Could not resolve host

[pseudo beacon]

Getting this on all my functions now:

An internal curl error has occurred within the executor! Error Number: 6. Error Msg: Could not resolve host: 65eb51c3dfd36\nError Code: 500

Self-hosted, 1.5

[rugged lark]

Does a redeploy fix it? @drifting mantle @gaunt hazel

[pseudo beacon]

it does not

[pseudo beacon]

Made a new function, same error

[severe smelt]

What are the logs for
docker compose logs appwrite
And
docker compose logs openruntimes-executor
?

[pseudo beacon]

same issue

appwrite.. does a lot more

I'm guessing it's talking about this..?

[thin rivet]

can you check the docker networks to see what containers are in which networks? the executor and the function runtime containers should be in the same docker network named runtimes or something like that

[pseudo beacon]

This yeah?

[thin rivet]

ya that last network. make sure the executor and runtime containers are in there

[pseudo beacon]

how do i check

[thin rivet]

you can inspect it: docker inspect <id>

[thin rivet]

there's nothing in there 👀 . inspect the runtime container and executor

[spark quarry]

what's the output of docker stats --no-stream

[pseudo beacon]

Runtime

uhh.. the openruntimes-executor? it's pretty long haha

[thin rivet]

you can focus only on the networks section

[thin rivet]

oh wait there's stuff there

[pseudo beacon]

openruntime-executor ^

[thin rivet]

i think these are runtime containers. i don't think the executor is in the runtimes network

[pseudo beacon]

all of my containers

[thin rivet]

ya as this shows. the executor is only in the appwrite network. not in the runtimes network

[pseudo beacon]

i saw someone else also have this issue.. but i couldn't find it anymore as well

[thin rivet]

check the executor's networks in your docker-compose.yml

[thin rivet]

try to recreate things.

docker compose down
docker compose up -d

make sure the network is recreated

[pseudo beacon]

already tried

didn't work

reboot the server? would that do anything? probably not

[west tapir]

1. What is the results of

docker ps -a

2. Try to redeploy one of the function to see if it fixes it

[pseudo beacon]

2. as said above, already tried

[west tapir]

Okay

[pseudo beacon]

and all my functions are broken, not just one, so my guess is something is wrong entirely

[west tapir]

Yes. I can see as the executor is unable to connect to the runtime network

What is the network output in

docker exec opentuntime-executor env

[pseudo beacon]

typo

[west tapir]

Sorry

[pseudo beacon]

2 typos

[lofty grotto]

Might have pinpointed the issue here, looking into a fix. There's a workaround if you need to get things running urgently

[pseudo beacon]

Depends when the fix is 😄

[lofty grotto]

You can downgrade the open-runtimes executor to 0.4.6, but you will lose access to the new runtimes added in 1.5

[pseudo beacon]

that's fine

i use node-20 anyway 🙂

[lofty grotto]

Cool, so you can go into the appwrite/docker-compose.yml file, find the openruntimes-executor service, and make the change:

- image: openruntimes/executor:0.4.9
+ image: openruntimes/executor:0.4.6

[pseudo beacon]

starting up appwrite takes quite long

[pseudo beacon]

Works!

Thanks 🙂

[lofty grotto]

Awesome 😁 we'll work towards getting the proper fix sorted too

[pseudo beacon]

btw, is the functions timeout fixed as well? or not yet

[rugged lark]

@echo steeple fyi

[drifting mantle]

@pseudo beacon Would it be possible to share source code for us? We cant seem to reproduce it.

[pseudo beacon]

what source? 🙂

[drifting mantle]

Of a function that said Could not resolve host: 65eb51c3dfd36

[pseudo beacon]

all of them? 😂

sure

[drifting mantle]

Sheesh 😅 Just one is fine. Also if you can simplfy, taht would be perfect

[pseudo beacon]

give me a few mins

[drifting mantle]

We tried with hello world and simple SDK call, and couldnt achieve the error

[pseudo beacon]

it's literally a get documents, that's all

also happened after migrating

[drifting mantle]

Thats perfect, should be easy to reproduce

[pseudo beacon]

okay a little bit more than that, since it's a switch case, but in general each endpoint only does one job, which is collecting documents