🐛 Bug Report: Function execution failed.

[usamashafiqs]

👟 Reproduction steps

On localhost this is running fine but not on ec2 instance.

Executions Logs

An internal curl error has occurred within the executor! Error Msg: Operation timed out

Appwrite-executor Logs

Executing Runtime: 6359c5064e8969d821a8-6446621b0787a4b581b4
Function executed in 0.38529300689697 seconds, status: failed
Executing Runtime: 6359c5064e8969d821a8-6446621b0787a4b581b4
[Error] Type: Exception
[Error] Message: An internal curl error has occurred within the executor! Error Msg: Operation timed out
[Error] File: /usr/src/code/app/executor.php
[Error] Line: 544
Executing Runtime: 6359c5064e8969d821a8-6446621b0787a4b581b4
Function executed in 120.00923085213 seconds, status: failed

Code

const nodemailer = require('nodemailer');

module.exports = async function (req, res) {
  const transporter = nodemailer.createTransport({
    host: req.variables.HOST,
    port: req.variables.PORT,
    secure: req.variables.SECURE,
    auth: {
      user: req.variables.USER,
      pass: req.variables.PASS,
    },
  });

  const payload = JSON.parse(req.payload);
  const name = payload['name'];
  const email = payload['email'];
  const subject = payload['subject'];
  const text = payload['text'];

  const info = await transporter.sendMail({
    from: `"Sender" <${req.variables.USER}>,`,
    to: `"${name}" <${email}>,`,
    subject: subject,
    text: text,
  });

  res.json({
    message: 'Email sent successfully',
    emailId: info.messageId,
  });
};

👍 Expected behavior

Function execution should be fine.

👎 Actual Behavior

Function execution failed.

🎲 Appwrite version

Version 1.3.x

💻 Operating system

Linux

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[stnguyen90]

@usamashafiqs thanks for creating this issue! 🙏🏼

This typically happens due to an error from your function code. Please try to make sure your code doesn't throw any errors (you can wrap all your code in a big try/catch and call res.json() or res.send() exactly once.

This could also be a true timeout. One way to tell is if your function's execution time is consistently the same as the timeout configured for your function. If this is the case, you should increase the timeout on the function.

[usamashafiqs]

@stnguyen90 I wrap my code with try/catch and increase the timeout as well still getting the same error.

An internal curl error has occurred within the executor! Error Msg: Operation timed out

appwrite-executor logs

Executing Runtime: 6359c5064e8969d821a8-644dc09db4011b512f5c
[Error] Type: Exception
[Error] Message: An internal curl error has occurred within the executor! Error Msg: Operation timed out
[Error] File: /usr/src/code/app/executor.php
[Error] Line: 54

This code is working on local appwrite instance but not on ec2 or linode instances.

[stnguyen90]

I wrap my code with try/catch and increase the timeout as well still getting the same error.

@usamashafiqs, some more questions:

1. what is the new code?
2. how long does the execution run for before erroring out?
3. what did you update the timeout to?

[usamashafiqs]

@stnguyen90, because I set the timeout value to 60, it took 60 seconds.
new code:

const nodemailer = require('nodemailer');

module.exports = async function (req, res) {
  try {
    const transporter = nodemailer.createTransport({
      host: req.variables.HOST,
      port: req.variables.PORT,
      secure: req.variables.SECURE,
      auth: {
        user: req.variables.USER,
        pass: req.variables.PASS,
      },
    });

    const payload = JSON.parse(req.payload);
    const name = payload['name'];
    const email = payload['email'];
    const subject = payload['subject'];
    const text = payload['text'];

    const info = await transporter.sendMail({
      from: `"Sender" <${req.variables.USER}>,`, // Sender email
      to: `"${name}" <${email}>,`,
      subject: subject,
      text: text,
    });

    res.json({
      message: 'Email sent successfully',
      emailId: info.messageId,
    });
  } catch (e) {
    res.send(e);
  }
};

[stnguyen90]

@usamashafiqs this could be a true timeout and because it times out, Appwrite isn't able to capture the logs. Would you please increase the timeout? In addition, instead of calling res.send(e), would you please change it to res.send(e.toString()?

[usamashafiqs]

@usamashafiqs this could be a true timeout and because it times out, Appwrite isn't able to capture the logs. Would you please increase the timeout? In addition, instead of calling res.send(e), would you please change it to res.send(e.toString()?

Same Error:
I test the code run fine on any type of environment.

An internal curl error has occurred within the executor! Error Msg: Operation timed out

[usamashafiqs]

@stnguyen90 I think function is not doing async tasks. When I try to execute a simple fetch request within a function got this error.

ReferenceError: e is not defined
    at module.exports (/usr/code-start/index.js:55:19)
    at /usr/local/src/server.js:68:19
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

[Hu-Wentao]

see #4594 , try catch and return res.send() with 2xx code

[stnguyen90]

When I try to execute a simple fetch request within a function

@usamashafiqs, please share your full code.

[usamashafiqs]

nodemail.tar.gz
@stnguyen90 This is the full code of the function.

[50l3r]

I have the same problem with a function who execute node-fetch call.

I avoid exceptions and use res.json but problem persists.

NOTE: The error occurs arbitrarily and not always.

[50l3r]

Oh my god, after searching a lot in the documentation and github I have seen that each function has a time limit that is specified in its configuration: https://appwrite.io/docs/functions#:~:text=Each%20execution%20has%20a%20default,for%20up%20to%20900%20seconds.

@usamashafiqs I think this can help you

[Haimantika]

Oh my god, after searching a lot in the documentation and github I have seen that each function has a time limit that is specified in its configuration: https://appwrite.io/docs/functions#:~:text=Each%20execution%20has%20a%20default,for%20up%20to%20900%20seconds.

@usamashafiqs I think this can help you

Yes there is a timeout for functions. @usamashafiqs did knowing this help you?

[stnguyen90]

@usamashafiqs,

nodemail.tar.gz @stnguyen90 This is the full code of the function.

The console.error(e); could be a problem. It would be best to do console.error(e.toString());.

In addition, it's odd the stack trace doesn't quite line up with the code. The stack trace says the error occurred on line 55, but your file is less than 55 lines.

[usamashafiqs]

@stnguyen90 The stack trace of the current code is:

An internal curl error has occurred within the executor! Error Msg: Operation timed out

I try to execute a simple fetch request within a function got this stack trace.

ReferenceError: e is not defined
    at module.exports (/usr/code-start/index.js:55:19)
    at /usr/local/src/server.js:68:19
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

They both are different, but they are doing async tasks.

I think the problem is that Function is not doing async tasks.

[stnguyen90]

@usamashafiqs,

I try to execute a simple fetch request within a function got this stack trace.

ReferenceError: e is not defined
    at module.exports (/usr/code-start/index.js:55:19)
    at /usr/local/src/server.js:68:19
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

They both are different, but they are doing async tasks.

Would you please share your latest full code for this function so I can see what's on line 55 that's throwing the error?

I think the problem is that Function is not doing async tasks.

Async code works fine in Appwrite functions.

[stnguyen90]

@usamashafiqs, are you still facing this problem? FYI, I'll need to close this due to inactivity soon.

[MACTEPyc]

If you are using Appwrite locally on your computer, you may have problems connecting to the API. In my case, replacing the localhost address in the endpoint with the IP address of my computer helped.

Do not use "http:https://localhost/v1" or "http:https://127.0.0.1/v1" when calling Appwrite API FUNCTIONS if the server is running locally. Instead, specify the actual IP address of your machine in the ENDPOINT.

I spent two days figuring out this problem. I hope my experience will help someone save time and avoid headaches due to the wrong endpoint.