search

MISP / misp-dashboard

A live dashboard for a real-time overview of threat intelligence from MISP instances
GNU Affero General Public License v3.0
194 stars 65 forks source link

Redis server error #164

Open Linow974 opened 2 years ago

Linow974 commented 2 years ago

Hello,

I recently installed MISP on an LXC storyteller, it works fine.

I then wanted to install the misp-dashboard because it seemed interesting to me to test.

So I followed the installation steps:

Everything went well, with no errors.

So I run

root@misp-int:/opt/misp-dashboard# ./start_all.sh
dashboard virtualenv seems to exist, good
        * Launching Redis servers
864:C 05 May 2022 15:30:18.421 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
864:C 05 May 2022 15:30:18.421 # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=864, just started
864:C 05 May 2022 15:30:18.421 # Configuration loaded
* Redis 6250 is running
        * Launching flask server
root@misp-int:/opt/misp-dashboard# dashboard virtualenv seems to exist, good
No screen detected
        * Launching zmq subscribers
        * Launching zmq dispatcher
 * Serving Flask app 'server' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: on

Everything works, and I can verify that all prots are listening:

root@misp-int:/opt/misp-dashboard# netstat -ltpnd
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:50000         0.0.0.0:*               LISTEN      3287/python         
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      246/sshd            
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      373/master          
tcp        0      0 127.0.0.1:8001          0.0.0.0:*               LISTEN      3114/python         
tcp        0      0 127.0.0.1:6250          0.0.0.0:*               LISTEN      3106/redis-server 1 
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      233/mysqld          
tcp6       0      0 :::8080                 :::*                    LISTEN      372/apache2         
tcp6       0      0 :::22                   :::*                    LISTEN      246/sshd            
tcp6       0      0 ::1:25                  :::*                    LISTEN      373/master          
tcp6       0      0 :::8443                 :::*                    LISTEN      372/apache2         
tcp6       0      0 ::1:6250                :::*                    LISTEN      3106/redis-server 1

But when I connect to http://localhost:8001 it doesn't work. With curl I get:

root@misp-int:/opt/misp-dashboard# curl http://localhost:8001
curl: (56) Recv failure: Connection reset by peer

and when I go to my MISP interface, in the maintenance tab, I have this:

image

I think it's not normal.

How to fix this ?

PS : I used the tutorial from the link: https://github.com/MISP/misp-dashboard

Nicolas-Pellletier commented 1 year ago

I think you have to enable it via plugin page in server & maintenance settings to be able to run ZeroMQ test. On the screenshot it says "...not enabled (so not tested)". It could help you to have more information about what's wrong. You could launch the python script ./diagnostic.py as well to see what happend, which service doesn't work.

Then to see more you can go at logs directory where you will find a lot of log files dedicated to specific task (updates.log/zmq_subscribe.log/zmq_dispatcher.log). Then you can as well check the following files: sudo tail -f /var/www/MISP/app/tmp/logs/mispzmq*

you can do a sudo tail -f logs/* in a specific terminal window while your doing other things in another window.