View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004182 | Kali Linux | Kali Package Bug | public | 2017-08-24 14:57 | 2018-02-21 09:42 |
Reporter | grimwiz | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | closed | Resolution | open | ||
Product Version | 2017.1 | ||||
Summary | 0004182: Redis package not appropriately configured for OpenVAS, scans stop or openvas fails to start up. | ||||
Description | The default OpenVAS installation triggers 20 parallel host-scans by default, each can run four vulnerability checks in parallel leading to about 100 instances of openvassd trying to talk to redis when a scan starts. | ||||
Steps To Reproduce | Running a lot of openvassd processes in parallel seems to trigger this, for example downloading a new feed at the same time that a scan is ongoing, or starting a second scan too soon after starting one. The error is fairly rare, I have about one failure/week. | ||||
Additional Information | The redis package configuration could be improved, enabling "appendonly yes" in /etc/redis/redis.conf may reduce dump file corruption. When openvas gets stuck this way:- I am running a postgresql database with my openvas. I don't believe this is relevant to the redis issue but felt I should mention it. In all other respects my system is running the default openvas settings with the rolling 17.1 release of kali. | ||||
Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.1), these legacy versions are no longer supported. Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup? |
|