Error WARNING ReactorEpoll::add()

[jilcimar]

I encountered an issue when using a coroutine to send data to AWS SNS within my application. The error occurs at runtime with the following message:

WARNING	ReactorEpoll::add(): failed to add events[fd=26#0, type=27, events=512], Error: Bad file descriptor[9]

This happens when executing the coroutine using co(function () { ... })

Environment Details:

[ElielFC]

I have the same problem too

[b-bianca]

Any update?

[NathanFreeman]

Hi. Please tell me what framework you are using.
If possible, could you provide a reproducible code example?
Thank you
@jilcimar @ElielFC @b-bianca

[matyhtf]

You need to provide a code example that can reproduce this issue. Additionally, if you are using extensions such as gRPC, there may be compatibility issues with Swoole.

[jilcimar]

Hi. Please tell me what framework you are using. If possible, could you provide a reproducible code example? Thank you @jilcimar @ElielFC @b-bianca

The framework used is Hyperf, and here is the code snippet showing an example of the coroutine usage that is causing the issue:

co(function () use ($parameter1, $parameter2, $parameter3, $parameter4, $parameter5) {
    try {
        $client = new SnsClient(config("notification." . config('notification.requests_logs.config')));
        $message = [
            //content
        ];
        $client->publish([
            'TopicArn' => config('notification.requests_logs.topic'),
            'Subject' => 'Requests Logs',
            'Message' => json_encode($message),
        ]);
    } catch (Throwable $e) {
        logger()->error("{$e->getMessage()}, trace: {$e->getTraceAsString()}");
    }
});

I had to hide the contents of the $message array for confidentiality reasons.

[NathanFreeman]

Could you please run php --ri curl? @jilcimar

[jilcimar]

Could you please run php --ri curl? @jilcimar

[matyhtf]

@jilcimar Please provide the full namespace and Composer package name.

[matyhtf]

I cannot replicate your issue. My curl version is 7.81.0, and my PHP version is 8.2.23.

[jilcimar]

I cannot replicate your issue. My curl version is 7.81.0, and my PHP version is 8.2.23.

@matyhtf
My curl version is 8.12.1, and my PHP version is 8.3.15 .

Guzzle version is "guzzlehttp/guzzle": "^7.9" - 7.9.2
AWS SDK version is "aws/aws-sdk-php": "^3.324" - 3.339.14

It only happens in the production environment and when the request volume is high

[matyhtf]

@jilcimar Please test with the latest code from the GitHub master branch, setting the print_backtrace_on_error option to true. This option will print the call stack when an unknown error occurs. This is an unknown error, and I cannot currently think of the circumstances under which this issue might arise.

[iamrafaelmelo]

print_backtrace_on_error

@matyhtf This option is for enable on Swoole Server or swoole.ini file?

[matyhtf]

@iamrafaelmelo

This is a global option that can be set as follows:

\Swoole\Coroutine::set(['print_backtrace_on_error' => true]);
// or 
swoole_async_set(['print_backtrace_on_error' => true]);

Thank you for your bug report. We need more information to analyze the issue. What impacts arise after this error log appears?

[matyhtf]

I recommend installing the Boost Stacktrace library before compiling the new version of swoole.

sudo apt install libboost-stacktrace-dev