Sudo gvm-start not work

└─$ sudo gvm-check-setup 2 ⨯
gvm-check-setup 20.8.0
Test completeness and readiness of GVM-20.8.0
Step 1: Checking OpenVAS (Scanner)…
OK: OpenVAS Scanner is present in version 20.8.0.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock.
OK: redis-server configuration is OK and redis-server is running.
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 64463 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-OpenVAS is present in version 20.8.0.
Step 2: Checking GVMD Manager …
OK: GVM Manager (gvmd) is present in version 20.08.0.
Step 3: Checking Certificates …
OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data …
OK: SCAP data found in /var/lib/gvm/scap-data.
OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user …
OK: Postgresql version and default port are OK.
gvmd | _gvm | UTF8 | cs_CZ.UTF-8 | cs_CZ.UTF-8 |
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) …
Oops, secure memory pool already initialized
OK: Greenbone Security Assistant is present in version 20.08.0~git.
Step 7: Checking if GVM services are up and running …
Starting ospd-openvas service
Waiting for ospd-openvas service
OK: ospd-openvas service is active.
Starting gvmd service
Waiting for gvmd service
OK: gvmd service is active.
Starting greenbone-security-assistant service
Waiting for greenbone-security-assistant service
OK: greenbone-security-assistant service is active.
Step 8: Checking few other requirements…
OK: nmap is present in version 20.08.0~git.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.

It seems like your GVM-20.8.0 installation is OK.

I get an error when I start
151 / 5000

Výsledky překladu

── (pc㉿pc) - [~] Sud $ sudo gvm-start awk: fatal: cannot open file `/ etc / default / greenbone-security-assistant 'for reading (Directory or file does not exist)

I don’t know where the mistake might be

Closing as a duplicate of Fresh Kali and gvm install, getting fatal error on gvm-start, Encounter error message [wk: fatal: cannot open file `/etc/default/greenbone-security-assistant' for reading (No such file or directory)] and Awk: fatal: cannot open file `/etc/default/greenbone-security-assistant' for reading (No such file or directory) (there are three existing threads about that message).

If you have further questions / remarks on this issue / problem on this third party packaging problem please follow up in the issue reported to the Kali package maintainers linked in