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

[Bug] FireHOLBlocklists No such file or directory #707

Closed
asucrews opened this issue Mar 4, 2020 · 8 comments
Closed

[Bug] FireHOLBlocklists No such file or directory #707

asucrews opened this issue Mar 4, 2020 · 8 comments
Labels
category:bug Issue is related to a bug

Comments

@asucrews
Copy link

asucrews commented Mar 4, 2020

Describe the bug
A clear and concise description of what the bug is.

after configure path to blocklist and running a analysis on ip. i get the blow error

{
"errorMessage": "Traceback (most recent call last):\n File "FireHOLBlocklists/firehol_blocklists.py", line 146, in \n FireholBlocklistsAnalyzer().run()\n File "FireHOLBlocklists/firehol_blocklists.py", line 30, in init\n os.mkdir(self.path, 0o0700)\nFileNotFoundError: [Errno 2] No such file or directory: '/etc/firehol/ipsets/'\n",
"input": null,
"success": false
}

To Reproduce
Steps to reproduce the behavior:

  1. set path for firehol blocklist
  2. create new analysis

Expected behavior
A clear and concise description of what you expected to happen.

Matches on firehol blacklist

Complementary information
If applicable, add screenshots and any additional information that might help explain your problem.

{
"errorMessage": "Traceback (most recent call last):\n File "FireHOLBlocklists/firehol_blocklists.py", line 146, in \n FireholBlocklistsAnalyzer().run()\n File "FireHOLBlocklists/firehol_blocklists.py", line 30, in init\n os.mkdir(self.path, 0o0700)\nFileNotFoundError: [Errno 2] No such file or directory: '/etc/firehol/ipsets/'\n",
"input": null,
"success": false
}

Work environment

  • Client OS: windows
  • Server OS: ubuntu 18.04
  • Browse type and version:
  • Cortex version: 3.0.1-2
  • Cortex Analyzer/Responder name: FireHOLBlocklists_2_0
  • Cortex Analyzer/Responder version: lastest

Possible solutions
If applicable, indicate possible solutions to the problem.

Not sure if there way to import folder in docker container or docker need pull the blocklist in to it

Additional context
Add any other context about the problem here.

@asucrews asucrews added the category:bug Issue is related to a bug label Mar 4, 2020
@garanews
Copy link
Contributor

garanews commented Mar 5, 2020

You can pull inside the docker or you can pull outside and then mount a volume to tell cortex where are the files.

@garanews
Copy link
Contributor

Hi @asucrews, was you able to run this Analyzer?

@asucrews
Copy link
Author

Sorry, i am noob to docker. so i am unsure how to implement the suggested changes.

@garanews
Copy link
Contributor

Hi @asucrews , do you have in your docker-compose.yml some volume regarding cortex image such as the config file or cortex-analyzers folder?
image

So for example I just did:

cd /opt
git clone https://github.com/firehol/blocklist-ipsets

then edit the docker-compose in this way:

Cattura

in order to map the folder outside the container.
Then rebuild the container with
docker-compose up

and sed the path in firehol analyzer:
image

And finally execute the analyzer, you see first attempt without correct setting and second attempt working:
image

Let me know if something is not clear or need further help.

@garanews
Copy link
Contributor

garanews commented Apr 2, 2020

@asucrews does it work?

@asucrews
Copy link
Author

asucrews commented Apr 9, 2020

This could work, but i installed cortex via deb package and the Analyzer are docker method and i don't have the docker-compose to mess with.

@garanews
Copy link
Contributor

You can create the volume also with docker, have a look here: http://dockerlabs.collabnix.com/beginners/volume/creating-volume-mount-from-dockercli.html

@garanews
Copy link
Contributor

garanews commented May 7, 2020

Going to close it, feel free to reopen if have other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug Issue is related to a bug
Projects
None yet
Development

No branches or pull requests

2 participants