Repository navigation
"error": "unable to start, otelcol state is Closed" #2531
Description
We deployed the changes to production, and during the application deployment we encountered the following error:
2026-07-01T11:40:51.875Z {"level": "warn", "ts":1782906051.8750505,"logger":"lifecycle.manager", "msg": "Failed t...}
{
"level": "warn",
"ts": 1782906051.8750505,
"logger": "lifecycle.manager",
"msg": "Failed to start the extension",
"error": "unable to start, otelcol state is Closed"
}
2026-07-01T11:40:51.875Z INIT_REPORT Init Duration: 262.80 ms Phase: init Status: error Error Type: Extension....
INIT_REPORT Init Duration: 262.80 ms Phase: init Status: error Error Type: Extension. InitError
Although we have done Log Migration in other services as well such as Beat and Call Masking Services but only for this service did we face this error.
Attached here is the screenshot of the Exact Logs from the Time of Deployment :-
Activity
tylerbenson commentedon Aug 11, 2026
Do you know which version of the collector extension you're using? Is this with the one that was just released? If so, can you try the previous version? Trying to rule out a regression.
princekumaryadav001 commentedon Aug 12, 2026
For collector we are using :-
opentelemetry-collector-amd64-0_22_0:1
and for Python we are using :-
opentelemetry-python-0_19_0:1
but both of these are working in our other repositories completely fine but they failed here only !!
however we are using Python 3.9 in other services and 3.11 here so does it have any relation to this issue ??