View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007289Kali LinuxKali Package Bugpublic2021-08-20 15:472021-12-09 13:39
Reporternimitz Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityunable to reproduce
Status closedResolutionno change required 
Product Version2021.2 
Summary0007289: gvm-check-setup script: line 352: [: too many arguments
Description

I installed openvas for the first time, however, I have hit a wall and am unable to start gvm initially it was the database error that was saying

ERROR: The default PostgreSQL version is not 13 required by libgvmd

I managed to fix the issue with the following solution

sudo nano /etc/postgresql/13/main/postgresql.conf and change the port to 5432.
sudo nano /etc/postgresql/12/main/postgresql.conf and change the port to 5433 (or any other port which is free).
sudo systemctl restart postgresql

However the problem persists, when I

gvm-check-setup
I get the error message saying:

ERROR: No users found. You need to create at least one user to log in.
FIX: create a user by running ‘sudo runuser -u _gvm – gvmd --create-user= --password=’

ERROR: Your GVM-21.4.2 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

Steps To Reproduce

Please install openvas normally and follow the instructions to change postgresql ports as I have explained in the description

Additional Information

I attached is a screenshot of the of the error messages when executing "sudo gvm-start" and "sudo gvm-check-setup"

Attached Files
Screen Shot 2021-08-20 at 3.25.44 PM.png (843,541 bytes)

Activities

sbrun

sbrun

2021-08-24 09:22

manager   ~0015022

You should not change the postgresql port by changing the /etc/postgresql/*/main/postgresql.conf files. The fix indicates by the gvm-check-setup script (and by the gvm-setup script) is the correct one:
use pg_upgradecluster to fix this. (we can not automate the clusters upgrade)
FYI we are working with GVM developers to avoid the issue with the PostgreSQL version for the next GVM releases.

It's weird you didn't have the issue when you ran 'gvm-setup'. It checks the postrgresql installation too. What command did you run before gvm-check-setup?
On a fresh install you need to run 'gvm-setup' first and 'gvm-check-setup' after. See /usr/share/doc/gvm/README.Debian

Issue History

Date Modified Username Field Change
2021-08-20 15:47 nimitz New Issue
2021-08-20 15:47 nimitz File Added: Screen Shot 2021-08-20 at 3.25.44 PM.png
2021-08-23 20:38 g0tmi1k Priority immediate => normal
2021-08-23 20:38 g0tmi1k Severity major => minor
2021-08-23 20:41 g0tmi1k Assigned To => sbrun
2021-08-23 20:41 g0tmi1k Status new => assigned
2021-08-24 09:22 sbrun Note Added: 0015022
2021-12-09 13:39 sbrun Status assigned => closed
2021-12-09 13:39 sbrun Resolution open => no change required