[STANDBY] executor log Error but function works

In all cases, the functions are launched correctly, despite the errors.

only 1 runtime container is created

I try with fresh install of appwrite 1.3.4/6/7, only upload fonction, same things

what error?

Connection refused

on every execution?

Hard to say, locally now error is gone

If I force docker compose -f docker-compose-appwrite.yml up -d --force-recreate error returns

But I can see document updated on redis

perhaps the runtime containers are trying to exit so they aren't accepting new requests

Maybe... Do you think these errors aren't serious and can be ignored?

up to you. i'd look into somehow cleanly exiting

What could cause this exit? Because the runtime works, since it sends to redis 100% of the time.

Your force re create stops the executor which then tries to stop the runtime containers it's managing

From that you mean ? I wait for executor up before test it

maybe in your code somehow catch the kill signall and then stopping execution?

All the code is encapsulated in a try/catch

Catch only set isError=err.message

that won't do it. you would need to do something along the lines to https://stackoverflow.com/questions/43003870/how-do-i-shut-down-my-express-server-gracefully-when-its-process-is-killed.

I try with a blank function

module.exports = async function (req, res) {
  res.json({
    areDevelopersAwesome: true,
  });
};

And have same behavior

oh...perhaps the runtime container isn't actually ready yet before it's trying to be executed?

I can see {areDevelopersAwesome: true} on Console > Functions > Executions > Logs
Or executor auto retry perhaps ?

it could be a tiny window where the runtime container is created, but the web server isn't actually up and ready yet

Everyone should reproduce in this case ? Let's just say it's a normal error...

[STANDBY] executor log Error but function works