Nothing Special   »   [go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

start misp modules after new install of misp #5613

Open
open-source-rs opened this issue Feb 8, 2020 · 4 comments
Open

start misp modules after new install of misp #5613

open-source-rs opened this issue Feb 8, 2020 · 4 comments
Assignees
@SteveClement
Labels
help wanted This is an issue that the community can help with S: needs diagnosis Status: needs diagnosis. This issue requires a technical diagnosis T: support Type: support. This issue is seeking support on a problem or question topic: install This issue involves installing MISP or other features topic: module This issue involves a module

Comments

@open-source-rs
Copy link

i'm completely lost as to how to do this using the new install notes.

on the old install i was able to start them as a service.

can someone please literally and verbosely lay out the steps to start and enable module start on reboot after a fresh install of misp on ubuntu 18.04 please?

here's the script options i used to install misp:

bash /tmp/INSTALL.sh -c -M

here's the output i get, and i know it's me and not the modules...

root@osrs-resource1:/usr/local/src/misp-modules/misp_modules/modules/import_mod# cd .. root@osrs-resource1:/usr/local/src/misp-modules/misp_modules/modules# cd ..
root@osrs-resource1:/usr/local/src/misp-modules/misp_modules# cd...
cd...: command not found
root@osrs-resource1:/usr/local/src/misp-modules/misp_modules# cd ..
root@osrs-resource1:/usr/local/src/misp-modules# sudo cp etc/systemd/system/misp-modules.service /etc/systemd/system/
root@osrs-resource1:/usr/local/src/misp-modules# sudo systemctl daemon-reload
root@osrs-resource1:/usr/local/src/misp-modules# sudo systemctl enable --now misp-modules
root@osrs-resource1:/usr/local/src/misp-modules# /var/www/MISP/venv/bin/misp-modules -l 127.0.0.1 -s &
[1] 18925
root@osrs-resource1:/usr/local/src/misp-modules# No module named 'misp_modules.modules.expansion._ransomcoindb'
2020-02-08 17:41:21,177 - misp-modules - INFO - Launch MISP modules server from package.
INFO:misp-modules:Launch MISP modules server from package.
2020-02-08 17:41:21,179 - misp-modules - INFO - Helper loaded cache
INFO:misp-modules:Helper loaded cache
2020-02-08 17:41:21,179 - misp-modules - INFO - Unable to load MISP modules from package.
INFO:misp-modules:Unable to load MISP modules from package.
^C
[1]+ Done /var/www/MISP/venv/bin/misp-modules -l 127.0.0.1 -s
root@osrs-resource1:/usr/local/src/misp-modules#
@open-source-rs open-source-rs added needs triage This issue has been automatically labelled and needs further triage T: support Type: support. This issue is seeking support on a problem or question labels Feb 8, 2020
@GlennHD
Copy link
Contributor
GlennHD commented Feb 9, 2020 •
edited
Loading

Not sure if this is the "most correct" answer but I just did the following on Ubuntu 18.04 LTS and that keeps the modules up and running:

nano /etc/systemd/system/misp-modules.service

[Unit]
Description=System-wide instance of the MISP Modules
After=network.target

[Service]
Restart=always
RestartSec=3
User=www-data
Group=www-data
WorkingDirectory=/usr/local/src/misp-modules
Environment="PATH=/var/www/MISP/venv/bin"
ExecStart=/var/www/MISP/venv/bin/misp-modules -l 127.0.0.1

[Install]
WantedBy=multi-user.target

Take note on ExecStart and how I didn't use -s

@SteveClement SteveClement self-assigned this Feb 11, 2020
@phage-nz
Copy link

Have a look at my comment here: MISP/misp-modules#354 (comment) - it may help.

@open-source-rs
Copy link
Author
open-source-rs commented Feb 20, 2020 via email

@cyamal1b4
Copy link

I have a similar issue. MISP-Modules is running fine one my machine. Checked with curl localhost:6666 and systemctl. However, since getting misp-modules running I changed to a docker version of MISP and now when they are both running (same host/VM) I get a connection refused on the server settings in the GUI. Any help anyone?

@davehouser1 davehouser1 mentioned this issue Aug 6, 2020
Closed
@enjeck enjeck added help wanted This is an issue that the community can help with S: needs diagnosis Status: needs diagnosis. This issue requires a technical diagnosis topic: module This issue involves a module topic: install This issue involves installing MISP or other features and removed needs triage This issue has been automatically labelled and needs further triage labels Nov 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SteveClement SteveClement

Labels
help wanted This is an issue that the community can help with S: needs diagnosis Status: needs diagnosis. This issue requires a technical diagnosis T: support Type: support. This issue is seeking support on a problem or question topic: install This issue involves installing MISP or other features topic: module This issue involves a module
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@SteveClement @phage-nz @GlennHD @enjeck @cyamal1b4 @open-source-rs