Empty reply from server with status code 0

I deployed a new function (well, redeployed code as a new function) with appwrite deploy function. The deployment failed with Empty reply from server with status code 0. An immediate redeploy worked perfectly.

Node 16.0, Appwrite 1.4.9, self-hosted. I guess this isn't really support so much as just letting the team know that this happened - it doesn't seem to be reproducible (trying again - also as a new function - doesn't have the same issue).

From logs:

appwrite-worker-builds  | [Worker] Worker 0 is ready!
appwrite-worker-builds  | Worker builds  started
appwrite-worker-builds  | [Job] Received Job (655d97b352f9e5.88661161).
appwrite-worker-builds  | Creating build for deployment: 655d97b3447a101005aa
appwrite-worker-builds  | Empty reply from server with status code 0
appwrite-worker-builds  | /usr/src/code/src/Executor/Executor.php:331
appwrite-worker-builds  | #0 /usr/src/code/src/Executor/Executor.php(91): Executor\Executor->call('POST', '/runtimes', Array, Array, true, 900)
appwrite-worker-builds  | #1 /usr/src/code/src/Appwrite/Platform/Workers/Builds.php(401): Executor\Executor->createRuntime('655d97b3447a101...', '648793d6a5100d1...', '/storage/functi...', 'openruntimes/no...', 'v3', true, 'src/main.js', '/storage/builds...', Array, 'tar -zxf /tmp/c...')
appwrite-worker-builds  | #2 {main}

Just as a side-note, I recommend using Node-18 or higher. Node-16 is deprecated.

Hey there 👋 Status code 0 means container is not running, I believe. My guess is that executor container crashed, and thanks to docker-compose, it was instantly restarted - making occurance rare.

If you find any logs from before crash, they could pin-point what went wrong, with docker compose logs openruntimes-executor. So far I saw these on self-hosted caused by memory issues. On Cloud, I dont see occurance of this error in last 30 days.

I know, I’ll get to it 😉