Back

Functions Ending Without Logged Reason

  • 0
  • Self Hosted
  • Functions
Tanner Meade
2 Jan, 2024, 23:13

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?

TL;DR
The user is experiencing failures in their executions on a remote cluster. They suspect that the function is using an old version of the Appwrite SDK. They also mention that they haven't found any useful logs yet and suspect it could be a RAM issue. They ask for help on how to debug the problem. Another user suggests that the error could be due to logging too much. The user also mentions an error related to "http.php" file and asks for clarification on its path. Solution: The issue could be due to an outdated Appwrite SDK or excessive logging. To debug the problem, the user can try updating the Appwrite SDK to
Drake
2 Jan, 2024, 23:17

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

Tanner Meade
2 Jan, 2024, 23:19

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.

Tanner Meade
4 Jan, 2024, 07:06

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.

Tanner Meade
4 Jan, 2024, 07:09

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

Tanner Meade
4 Jan, 2024, 07:12

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

Tanner Meade
4 Jan, 2024, 07:13

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

Tanner Meade
4 Jan, 2024, 07:14

It's using dart_appwrite: ^10.0.0

Tanner Meade
4 Jan, 2024, 07:22

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.

Tanner Meade
5 Jan, 2024, 07:11

Ya I'm getting that error.

Tanner Meade
5 Jan, 2024, 07:13

@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.

ideclon
5 Jan, 2024, 09:24
ideclon
5 Jan, 2024, 09:25

This error usually means youโ€™re logging too much.

Tanner Meade
5 Jan, 2024, 14:35

That's definitely possible. Really hope this is all it is.

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more