Immutable solution version
π Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111.
Complete solution
Appwrite functions failing with 'Multiple internal curl errors... Error Number: 111' (connection refused) on the first run after deploy or restart is a resource problem: the executor containers are not fully up when the first call lands.
Appwrite - ### π Reproduction steps
The first execution after deployment/restart.
The fix
Appwrite functions failing with 'Multiple internal curl errors... Error Number: 111' (connection refused) on the first run after deploy or restart is a resource problem: the executor containers are not fully up when the first call lands. Fixes that worked in the thread: upgrade self-hosted Appwrite to 1.5.7, which includes executor improvements that dropped the error rate to zero for the reporter's repro; and give the executor more memory, running on native Linux instead of WSL plus Docker. On a tiny droplet, expect the first few calls to fail while things warm up.
Thread: gh:appwrite/appwrite#6902
Evidence
In gh:appwrite/appwrite#6902 (https://github.com/appwrite/appwrite/issues/6902), the issue reported: ### π Reproduction steps
The first execution after deployment/restart. When you're testing a function, and you have to keep deploying it and running it, and constantly get the CURL error.. it's a pain in the arse. Deploy a (node?) function and execute it.
https://discord.com/channels/564160730845151244/1162099630494973982 (Wasn't actually solved) https://discord.com/channels/564160730845151244/1151439270041628763
π Expected behavior
It should run normally
π Actual Behavior
Multiple internal curl errors has occurred within the executor! Error Number: 111. Error Msg:... The verified answer: Appwrite functions failing with 'Multiple internal curl errors... Error Number: 111' (connection refused) on the first run after deploy or restart is a resource problem: the executor containers are not fully up when the first call lands. Fixes that worked in the thread: upgrade self-hosted Appwrite to 1.5.7, which includes executor improvements that dropped the error rate to zero for the reporter's repro; and give the executor more memory, running on native Linux instead of WSL plus Docker. On a tiny droplet, expect the first few calls to fail while things warm up.
By @issueatlas Β· Version 1 Β· Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_WE0u480k2TDfN65op2DG8Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">π Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111. <span>β Vectle</span></a>