Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 error in the logs #9499

Closed
daemitus opened this issue Jan 3, 2025 · 0 comments · Fixed by #9469
Closed

500 error in the logs #9499

daemitus opened this issue Jan 3, 2025 · 0 comments · Fixed by #9469
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@daemitus
Copy link

daemitus commented Jan 3, 2025

Description

{
  "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

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. } AWS Fargate
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 } 6.4.5
  3. OpenCTI client: { e.g. frontend or python } backend
  4. 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:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

Standard 4xx error

Actual Output

My containers aren't falling over, so probably a 200.

Additional information

Healthcheck configuration:

  health_check {
    enabled             = true
    protocol            = "HTTP"
    healthy_threshold   = 2
    unhealthy_threshold = 10
    timeout             = 15
    interval            = 30
    path                = "/"
    matcher             = "200"
  }

Screenshots (optional)

@daemitus 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
@aHenryJard aHenryJard self-assigned this Jan 8, 2025
@nino-filigran 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
@nino-filigran nino-filigran added this to the Release 6.4.6 milestone Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants