So Im trying to create a new nmap scan to run but it doesnt seem to work - the management interface freezes up and starts loading but never really finishes the request.
I think I have my engines correctly set up ( tested both docker container name in API url & docker container IP: docker-nmap-001 and 172.18.0.7 )
Both the engine lights are green and i assume this means to show its good.
I can communicate with the engine from the patrowl-django container, which you can see here
[root@localhost scripts]# docker exec -it patrowl-django bashroot@d4f2ed7cd604:/opt/patrowl-manager# curl docker-nmap-001:5001/engines/nmap/status{"page":"status","scanner":{"allowed_asset_types":["ip","domain","fqdn","url","ip-range","ip-subnet"],"description":"Network Scanner","name":"Nmap","options":{"aggressive_scan":{"type":"optional","value":"-T4"},"all_scan":{"type":"optional","value":"-A"},"detect_os":{"type":"optional","value":"-O --osscan-guess --max-os-tries 1"},"detect_service_version":{"type":"optional","value":"-sV"},"hosts":{"type":"required"},"no_dns":{"type":"optional","value":"-n"},"no_ping":{"type":"optional","value":"-Pn"},"perfs":{"type":"optional","value":"--defeat-rst-ratelimit"},"ping_scan":{"type":"optional","value":"-sP"},"ports":{"type":"optional","value":"-p"},"scan_udp":{"type":"optional","value":"-sU --max-retries 3"},"script":{"type":"optional","value":"--script"},"script_args":{"type":"optional","value":"--script-args"},"script_output_fields":{"type":"optional","value":[""]},"script_scan":{"type":"optional","value":"-sC"},"show_open_ports":{"type":"optional","value":"--open"},"slow_scan":{"type":"optional","value":"-T1"},"syn_scan":{"type":"optional","value":"-sS"},"tcp_scan":{"type":"optional","value":"-sT"}},"path":"/usr/bin/nmap","status":"READY","version":"1.0"},"scans":{},"status":"READY"}
in the patrowl-rabbitmq container i listed the queue to see if anything was getting there but it doesnt look that way:Every 2.0s: rabbitmqctl list_queues | grep nmap
0dc6435c8682: Tue Feb 26 19:44:12 2019
scan-nmap 0
monitor-nmap 0
nmap-node@d4f2ed7cd604.celery.pidbox 0
Im not 100% sure of the flow of things or if im looking in the right place/
so im thinking there is something happening between submission of SCAN request -> and inserting into the NMAP queue
manager -> RMQ -><- NMAP
___^^^
LOGGING_LEVEL = "INFO,WARNING,ERROR,DEBUG"
` environment:
- DB_PORT_5432_TCP_HOST=db
- DEBUG=True
- RABBIT_PORT_5672_TCP=rabbitmq:5672
- LOGGING_LEVEL = "INFO,WARNING,ERROR,DEBUG"`im assuming
aargh had to readd my engine after upping my cotainers - and when i went back to edit the engine .. manager froze again...patrowl-django | <ul class="errorlist"><li>title<ul class="errorlist"><li>This field is required.</li></ul></li><li>engine_policy<ul class="errorlist"><li>This field is required.</li></ul></li><li>scan_type<ul class="errorlist"><li>This field is required.</li></ul></li></ul>
patrowl-django | <ul class="errorlist"><li>title<ul class="errorlist"><li>This field is required.</li></ul></li><li>engine_policy<ul class="errorlist"><li>This field is required.</li></ul></li><li>scan_type<ul class="errorlist"><li>This field is required.</li></ul></li></ul>
patrowl-rabbitmq | 2019-02-26 20:05:09.016 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:09:49.011 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:14:29.012 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:19:09.008 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:23:49.013 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:28:29.017 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-rabbitmq | 2019-02-26 20:33:09.015 [warning] <0.113.0> lager_error_logger_h dropped 9 messages in the last second that exceeded the limit of 1000 messages/sec
patrowl-django | [2019-02-26 20:34:14 +0000] [54] [CRITICAL] WORKER TIMEOUT (pid:58)
patrowl-django | [2019-02-26 21:34:14 +0000] [58] [INFO] Worker exiting (pid: 58)
patrowl-django | [2019-02-26 20:34:15 +0000] [219] [INFO] Booting worker with pid: 219
are these MQ dropped messages normal?lager_error_logger_h dropped 9 messages in the last second
FO] Worker exiting (pid: 58) . was from my request never finishing..
almost seems like there is a bottleneck with the manager - Would putting nginx infront of the manager as a reverse proxy maybe help with the requests, sessions management and connection caching? https://www.nginx.com/blog/maximizing-python-performance-with-nginx-parti-web-serving-and-caching/ .
BTW
Where would I see this "EVENTS" tab?
In scan results
1/ download the GitHub repos and build the docker images
2/ synchronize your local registry with all required images: patrowl/patrowl-manager-community-edition, rabbitmq:3-alpine, postgres:11-alpine and nginx
With those versions I'm not able to make Engines go into Available State. Even though they are indeed ALIVE when querying them through HTTP or through the Info button on Manager. Absolute fresh install without any modifications. I indeed see permanent status requests onto one example engine -NMAP- but still they is not going available onto the Manager and thus it's not executing scans; it just enqueues them.
