TheHive-Project / TheHive-Project/Cortex

No such file or directory

Open
#380 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.6k
Forks
264
PR merge metrics
No merged PRs in 30d

Description

Request Type

Bug

Work Environment
Question Answer
OS version (server) RedHat
OS version (client) 10
Cortex version / git hash 3.1.1-1
Package Type Binary
Browser type & version If applicable
Problem Description

Describe the problem/bug as clearly as possible.

when run the analyzers written by myself, it return an error.

Steps to Reproduce
  1. put my analyzers on the position /opt/analyzers
  2. restart service
  3. enable the analyzer, and create a case to run, it will return error in log
  4. have install python3, and run other analyzers ok, for exam, AbuseIPDB
  5. . Pls give some suggestion.
Possible Solutions

(keep this section if you have suggestions on how to solve the problem. Otherwise delete it)

Complementary information

(add anything that can help identifying the problem such as log excerpts, screenshots, configuration dumps etc.)

[info] o.t.c.s.JobSrv - Looking for similar job in the last 10 minutes (worker=7390edfe350776f921219e1696eb409f, dataType=ip, data=Left(58.97.208.199), tlp=2, parameters={})
[info] o.t.c.s.AuditActor - Job QsMuM3sBSgl94jXJ84gZ has be updated (JsDefined("InProgress"))
[info] o.t.c.s.ProcessJobRunnerSrv - Execute /opt/analyzers/ThreatBook/threatbook_analyzer.py in /opt/analyzers, timeout is 30 minutes
[info] o.t.c.s.ProcessJobRunnerSrv - Job QsMuM3sBSgl94jXJ84gZ: /usr/bin/env: python3
[info] o.t.c.s.ProcessJobRunnerSrv - Job QsMuM3sBSgl94jXJ84gZ: : No such file or directory
[info] o.t.c.s.AuditActor - Job QsMuM3sBSgl94jXJ84gZ has be updated (JsDefined("Failure"))
[info] o.t.c.s.JobSrv - Job QsMuM3sBSgl94jXJ84gZ has finished with status Failure

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the analyzer execution path shown in the report, especially ProcessJobRunnerSrv and /opt/analyzers/ThreatBook/threatbook_analyzer.py. Reproduce the service job on the reported RedHat environment and inspect why the logged python3 command returns “No such file or directory”; done means the custom analyzer starts successfully and the job no longer fails at launch.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, scala
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.