
I've got a dart function that fails after the timeout. There is no error thrown in dart and the console logs debugging messages I put in until it gets to a line of code that is querying the DB for docs. I haven't nailed down yet if that is reliably the only line of code that it is stopping at yet.
Many other functions work with querying the DB so I don't think it is a self-hosted communication in the cluster issue between the function and the DB. Sometimes the problematic function does work when running for different parameters.
My current thought is maybe there is a memory issue and the execution fails when loading the data in from the DB. I can't see any obvious RAM issues when looking at the server as a whole.
Any ideas on how to debug this?

executor or runtime container would indicate if it's a ram problem.

Thought I checked those before and it wasn't obvious to me what the issue was. I'll reproduce the problem and check the logs again. Maybe post them here.

Haven't found any useful logs yet. Just the normal executor logs like the maintenance tasks and eventually a successful removing of a function runtime after it hasn't been called in a while.

Container logs just have the preparing to start and "starting..." log entries.

ah, wait -- I think I found something. Shortly after the Successfully removed xxxxx
in the executor it has these:

maybe my function is using an old appwrite sdk for appwrite v1.4.11?

It's using dart_appwrite: ^10.0.0

I'm creating several execution via the cli on my machine for a remote cluster and each timeI run the list of executions some more of those failures pop up in the executor now. I'll need to redeploy the cluster to get a clean slate to try to isolate the issue.

Ya I'm getting that error.

@Steven any idea where that executor log file path of " File: /usr/local/app/http.php" is pointing towards? The error is on line 1019, so I would think it isn't Appwrite's app/http.php file. I'm not sure it's in the open runtimes repo either.

Pretty sure itโs this - https://github.com/open-runtimes/executor/blob/main/app/http.php?

This error usually means youโre logging too much.

That's definitely possible. Really hope this is all it is.
Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
