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

Cortex 2.0.3 docker container having cortex analyzer errors #90

Closed
rayschippers opened this issue Apr 12, 2018 · 0 comments
Closed

Cortex 2.0.3 docker container having cortex analyzer errors #90

rayschippers opened this issue Apr 12, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@rayschippers
Copy link

Request Type

Bug

Work Environment

Question Answer
OS version (server) Ubuntu
OS version (client) Ubuntu
Cortex version / git hash 2.0.3-1
Package Type Docker
Browser type & version n/a

Problem Description

Since upgrading to Cortex 2.0.3-1 docker image I get the following report in The Hive:

{
  "errorMessage": "Invalid output\nTraceback (most recent call last):\n  File \"Abuse_Finder/abusefinder.py\", line 8, in <module>\n    from cortexutils.analyzer import Analyzer\nImportError: No module named cortexutils.analyzer\n",
  "input": null,
  "success": false
}

The Cortex job history shows:

Invalid output
Traceback (most recent call last):
  File "Censys/censys_analyzer.py", line 2, in <module>
    from cortexutils.analyzer import Analyzer
ImportError: No module named 'cortexutils'


Steps to Reproduce

  1. Run The Hive 3.0.8-1 and Cortex 2.0.3-1 and connect them (I verified I have green brain)
  2. Try and run analyzer.

Possible Solutions

Rolling back to 2.0.2-1 fixed the issue (aside from the know python 3 issue) so a change between the two caused it (did not see any PR requests from the last few days).

Complementary information

Failures seen on:
Abuse Finder 2
Censys 1
Fortiguard URL Category 2
MISP 2
OTXQuery 2
Robtex Forward PDNS 1
VirusTotal GetReport 3

@To-om To-om added this to the 2.0.4 milestone Apr 12, 2018
@To-om To-om self-assigned this Apr 12, 2018
@To-om To-om added the bug label Apr 12, 2018
@To-om To-om closed this as completed Apr 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants