View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005003 | Kali Linux | Kali Package Bug | public | 2018-09-18 23:24 | 2019-05-22 10:08 |
Reporter | pcolmer | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | suspended | ||
Summary | 0005003: Cannot get openvas to setup and run on Kali on WSL | ||||
Description | I've installed Kali from the Windows 10 Store. I've followed the steps in https://www.kali.org/penetration-testing/openvas-vulnerability-scanning/ to install the package but I'm hitting errors and blocks. After the initial installation, the following messages are displayed: /usr/sbin/openvasmd [>] Stopping OpenVAS services [>] Starting openvassd (openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.385: get_redis_ctx: redis connection error: No such file or directory (openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.389: redis_new: cannot access redis at '/var/run/redis-openvas/redis-server.sock' (openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.390: get_redis_ctx: redis connection error: No such file or directory /usr/bin/openvas-start: line 20: lsof: command not found System has not been booted with systemd as init system (PID 1). Can't operate. [*] Opening Web UI (https://127.0.0.1:9392) in: 5... 4... 3... 2... 1... After installing lsof and killall, I then looked at trying to solve the redis errors. It looks like the default redis configuration file (/etc/redis/redis.conf) is installed and not configured to meet openvas's needs, namely support for Unix sockets and using the path /var/run/redis-openvas. After fixing that, things look a bit better except for: [>] Migrating openvassd (openvasmd:6410): md manage-WARNING **: 00:03:53.397: sql_exec_internal: sqlite3_step failed: locking protocol (openvasmd:6410): md manage-WARNING **: 00:03:53.399: sqlv: sql_exec_internal failed (openvasmd:6410): md manage-WARNING **: 00:04:03.417: sql_exec_internal: sqlite3_step failed: locking protocol (openvasmd:6410): md manage-WARNING **: 00:04:03.419: sqlv: sql_exec_internal failed (openvasmd:6410): md manage-WARNING **: 00:04:13.433: sql_exec_internal: sqlite3_step failed: locking protocol (openvasmd:6410): md manage-WARNING **: 00:04:13.435: sqlv: sql_exec_internal failed [>] Rebuilding openvassd I'm not sure what is causing these problems or how to fix them. Even with all of that fixed, it looks like openvas-start is going to have problems because it uses systemctl and, as far as I can tell, WSL doesn't yet support systemd/systemctl. | ||||
Looking further at what openvas-start is doing, I've tried using "service yyy start" instead, with the following results: service greenbone-security-assistant startStarting Greenbone Security Assistant: Warning: MHD_USE_THREAD_PER_CONNECTION must be used only with MHD_USE_INTERNAL_POLLING_THREAD. Flag MHD_USE_INTERNAL_POLLING_THREAD was added. Consider setting MHD_USE_INTERNAL_POLLING_THREAD explicitly. service openvas-scanner startStarting OpenVAS Scanner: service openvas-manager start None of the three services is running. |
|
Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2018.3), 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? |
|