Contrib.social

"Export retry limit exceeded in line 114" when enabling module

Open on Drupal.org →
Created on 1 February 2024, 10 months ago
Updated 5 February 2024, 10 months ago

Problem/Motivation

When I enable this module via the CLI, I get the following error:

$ drush en opentelemetry 
 [success] Successfully enabled: opentelemetry
 [error]  Export failure: Export retry limit exceeded in line 114 of /var/www/html/vendor/open-telemetry/sdk/Common/Export/Http/PsrTransport.php (previous exception message: cURL error 7: Failed to connect to localhost port 4318: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://localhost:4318/v1/traces). <pre>#0 /var/www/html/vendor/open-telemetry/exporter-otlp/SpanExporter.php(41): OpenTelemetry\SDK\Common\Export\Http\PsrTransport->send('\n\xD9\x06\n\xB3\x05\n!\n\thost....', NULL)
....

Drupal: 10.2.2
OpenTelemetry: 1.0@beta2

Steps to reproduce

1. Install Drupal `10.2.2`
2. Install opentelemetry module

composer require 'drupal/opentelemetry:^1.0@beta'

3. Enable module via CLI

$ drush en opentelemetry
 [success] Successfully enabled: opentelemetry
 [error]  Export failure: Export retry limit exceeded in line 114 of /var/www/html/vendor/open-telemetry/sdk/Common/Export/Http/PsrTransport.php (previous exception message: cURL error 7: Failed to connect to localhost port 4318: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://localhost:4318/v1/traces). <pre>#0 /var/www/html/vendor/open-telemetry/exporter-otlp/SpanExporter.php(41): OpenTelemetry\SDK\Common\Export\Http\PsrTransport->send('\n\xC1\x06\n\x9B\x05\n!\n\thost....', NULL)
...

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Postponed: needs info

Version

1.0

Component

Code

Created by

🇯🇵Japan tyler36 Osaka

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tyler36
  • Comment 10 months ago →
    🇮🇳India gaurav_manerkar Vasco Da Gama, Goa

    @tyler36, use beta2 version

  • Comment 10 months ago →
    🇮🇳India mukhtarm

    its because the module is trying to connect to the telemetry default endpoint specified in the opentelemetry.settings.yml (http://localhost:4318). Either need to disable it or enable the server and try.

  • Comment 10 months ago →
    🇯🇵Japan tyler36 Osaka
  • Comment 10 months ago →
    🇯🇵Japan tyler36 Osaka

    @gaurav_manerkar
    Seems I was on beta2; I update the summary.

    @MukhtarM
    Disabling the enpoint resolves the issue.
    Perhaps we can improve the error message?

  • Comment 10 months ago →
    🇮🇳India gaurav_manerkar Vasco Da Gama, Goa

    @tyler36
    1. Use the dev version of the module which has latest fixes.

    2. Update all the dependent composer packages to latest stable version:-
    - Package versions i use

    drupal/opentelemetry (dev-1.0.x 6d55b6f)
google/protobuf (v3.25.2)
open-telemetry/api (1.0.2)
open-telemetry/context (1.0.2)
open-telemetry/exporter-otlp (1.0.3)
open-telemetry/gen-otlp-protobuf (1.1.0)
open-telemetry/opentelemetry-propagation-traceresponse (0.0.2)
open-telemetry/sdk (1.0.6)
open-telemetry/sem-conv (1.23.1)
php-http/discovery (1.19.2)
symfony/polyfill-php82 (v1.28.0)

    3. Make sure open-telemetry module is configured with endpoint, by default it will point to localhost.
    4. For remote env, you might problem described in https://www.drupal.org/project/opentelemetry/issues/3416011 🐛 Unhandled export error: Error occurred during parsing: Fail to push limit. Closed: won't fix

  • Status changed to Postponed: needs info 10 months ago
  • Comment 10 months ago →
    🇦🇲Armenia murz Yerevan, Armenia

    @tyler36, this error means that the module can't upload traces to the default endpoint "localhost:4318".

    So, if your OpenTelemetry receiver has another endpoint - configure it in the module settings, and the error should gone.

    If your endpoint matches the default one ("localhost:4318") - please check errors on the endpoint side, maybe the format is wrong or some other settings.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024