"error": "unable to start, otelcol state is Closed"

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 :-

Start by locating the lifecycle.manager extension startup path and the handling of the otelcol Closed state. Use the deployment log and the reported Lambda init failure to investigate why this service reaches that state while the other migrated services do not. Done means the failure is reproducible or explained and the extension starts successfully during deployment.