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

SinkDB analyzer could not find DIG in the Cortex docker image #147

Closed
ParanoidRat opened this Issue Oct 15, 2018 · 0 comments

Comments

Projects
None yet
3 participants
@ParanoidRat

ParanoidRat commented Oct 15, 2018

Request Type

Bug

Work Environment

Question Answer
OS version (server) n/a
OS version (client) n/a
Cortex version / git hash thehiveproject/cortex:2.1.2-1
Package Type Docker (Swarm)

Problem Description

SinkDB uses dig to query data (see line 20 in sinkdb.py). When SinkDB analyzer is used in Cortex docker container it returns the following error

Invalid output Traceback (most recent call last): File "SinkDB/sinkdb.py", line 52, in <module> SinkDBAnalyzer().run() File "SinkDB/sinkdb.py", line 36, in run "is_sinkhole": self.dig(self.data) File "SinkDB/sinkdb.py", line 22, in dig stderr=subprocess.PIPE) File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory 

Steps to Reproduce

  1. Deploy Cortex as a docker container or Swarm service
  2. Supply latest analyzers as a docker volume
  3. Use SinkDB analyzer

Possible Solutions

Provide dig as part of Cortex docker image placed in the standard PATH

@ParanoidRat ParanoidRat changed the title Cortex docker image seems to lack dig tool used by SinkDB analyzer SinkDB analyzer could not find DIG in the Cortex docker image Oct 15, 2018

@saadkadhi saadkadhi added the bug label Oct 16, 2018

@saadkadhi saadkadhi added this to the 2.1.3 milestone Oct 16, 2018

To-om added a commit that referenced this issue Dec 19, 2018

@To-om To-om closed this Dec 19, 2018

To-om added a commit that referenced this issue Dec 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment