You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"category": "APP",
"errors": [
{
"attributes": {
"genre": "TECHNICAL",
"http_status": 500,
"reason": "Error: Cannot set headers after they are sent to the client
at ServerResponse.setHeader (node:_http_outgoing:655:11)
at ServerResponse.header (/opt/opencti/build/node_modules/express/lib/response.js:794:10)
at ServerResponse.send (/opt/opencti/build/node_modules/express/lib/response.js:174:12)
at ServerResponse.json (/opt/opencti/build/node_modules/express/lib/response.js:278:15)
at ServerResponse.send (/opt/opencti/build/node_modules/express/lib/response.js:162:21)
at /opt/opencti/build/src/http/httpPlatform.js:490:21
at processTicksAndRejections (node:internal/process/task_queues:95:5)"
},
"message": "Engine unhandled rejection",
"name": "UNKNOWN_ERROR",
"stack": "GraphQLError: Engine unhandled rejection
at error (/opt/opencti/build/src/config/errors.js:7:10)
at UnknownError (/opt/opencti/build/src/config/errors.js:81:47)
at process.<anonymous> (/opt/opencti/build/src/boot.js:61:16)
at process.emit (node:events:518:28)
at process.emit (/opt/opencti/build/node_modules/source-map-support/source-map-support.js:516:21)
at emitUnhandledRejection (node:internal/process/promises:250:13)
at throwUnhandledRejectionsMode (node:internal/process/promises:385:19)
at processPromiseRejections (node:internal/process/promises:470:17)
at processTicksAndRejections (node:internal/process/task_queues:96:32)"
}
],
"level": "error",
"message": "Engine unhandled rejection",
"source": "backend",
"timestamp": "2025-01-03T17:52:38.405Z",
"version": "6.4.5"
}
Environment
OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. } AWS Fargate
OpenCTI version: { e.g. OpenCTI 1.0.2 } 6.4.5
OpenCTI client: { e.g. frontend or python } backend
Other environment details: n/a
Reproducible Steps
Recently upgraded, saw the above error in the logs, 240x/hour. Corresponds to my load balancer health check interval. Going to switch to the new /healthcheck API, however regardless of what my HTTP / check is doing, the above error appears wrong.
Steps to create the smallest reproducible scenario:
{ e.g. Run ... }
{ e.g. Click ... }
{ e.g. Error ... }
Expected Output
Standard 4xx error
Actual Output
My containers aren't falling over, so probably a 200.
The text was updated successfully, but these errors were encountered:
daemitus
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 3, 2025
nino-filigran
added
solved
use to identify issue that has been solved (must be linked to the solving PR)
and removed
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 8, 2025
Description
Environment
Reproducible Steps
Recently upgraded, saw the above error in the logs, 240x/hour. Corresponds to my load balancer health check interval. Going to switch to the new /healthcheck API, however regardless of what my HTTP / check is doing, the above error appears wrong.
Steps to create the smallest reproducible scenario:
Expected Output
Standard 4xx error
Actual Output
My containers aren't falling over, so probably a 200.
Additional information
Healthcheck configuration:
Screenshots (optional)
The text was updated successfully, but these errors were encountered: