View Issue Details

IDProjectCategoryView StatusLast Update
0006915Kali LinuxGeneral Bugpublic2021-01-13 09:14
Reporterorenc78 Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Summary0006915: Fresh Kali and gvm install, getting fatal error on gvm-start

gvm-start 2 ⨯
awk: fatal: cannot open file `/etc/default/greenbone-security-assistant’ for reading (No such file or directory)

Any ideas?




2021-01-10 00:14

reporter   ~0014082

I have the same error in kali 2020.4 (for raspberry). The gvm-setup is having a bug in the gvm-start, this is the workaround solution :

after you install your gvm (openvas), execute the following commands:
#gvm-check-setup (follow its instructions and execute their recomended commands, until it says "It seems like your GVM 20.8.0 installation is OK.")

then open your browser in:

Note: every time you restart kali, you'll have to execute gvm-setup and gvm-check-setup

NOTE: DON'T use the gvm-start until kali fix it, i tried the following, and only started the openvas webserver:

The error is because the gvm-start command (/usr/bin/gvm-start) tries to find the GSA_PORT parameter in the /etc/default/greenbone-security-assistant, but that file is does not exist. Since, that file is used to set openvas variables. if you create a file and add the variables, the gvm-start command works fine (but does not start gvm):

cd /etc/default/
sudo touch greenbone-security-assistant
sudo nano greenbone-security-assistant
add the following line: (or the port for the gvm webservice)
save and close the file, now execute gvm-start

Another method:
#nano /usr/bin/gvm-start
change the PORT parameter for your web port:
#PORT=$(awk [function that sucury detects as exploit] /etc/default/greenbone-security-assistant)


As I said, this only start the web application but no the openvas server, so use the gvm-check-setup until they fix it.



2021-01-13 09:14

manager   ~0014112

gvm-start script is now fixed in gvm version

Issue History

Date Modified Username Field Change
2020-12-08 13:50 orenc78 New Issue
2021-01-10 00:14 fearx135 Note Added: 0014082
2021-01-13 09:14 sbrun Assigned To => sbrun
2021-01-13 09:14 sbrun Status new => resolved
2021-01-13 09:14 sbrun Resolution open => fixed
2021-01-13 09:14 sbrun Note Added: 0014112