Greenbone/Fehlerbehebung: Unterschied zwischen den Versionen
Keine Bearbeitungszusammenfassung |
K Textersetzung - „= Bekannte Probleme =“ durch „= Problembehebung =“ |
||
(4 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
Zeile 1: | Zeile 1: | ||
== | == Problembehebung == | ||
There is a lot that can go wrong during the installation of OpenVAS as some of our readers has pointed out, therefore, we decided to create a little extra section here, covering the most common errors. | There is a lot that can go wrong during the installation of OpenVAS as some of our readers has pointed out, therefore, we decided to create a little extra section here, covering the most common errors. | ||
== PostgreSQL Version Errors v13 and v14 == | |||
There are multiple possible version errors for PostgreSQL. As our reader Tom has pointed out, the first one is: | There are multiple possible version errors for PostgreSQL. As our reader Tom has pointed out, the first one is: | ||
Zeile 21: | Zeile 21: | ||
sudo systemctl restart postgresql | sudo systemctl restart postgresql | ||
== PostgreSQL Version Errors v14 and v15 == | |||
During my installation, I got the following error affecting '''v14''' and '''v15''' of PostgreSQL: | During my installation, I got the following error affecting '''v14''' and '''v15''' of PostgreSQL: | ||
Zeile 31: | Zeile 31: | ||
sudo /usr/bin/pg_dropcluster --stop 14 main | sudo /usr/bin/pg_dropcluster --stop 14 main | ||
== OpenVAS failed to find config == | |||
Another common error is the '''failed to find config ‘long-string-value’''' message. There are multiple possible solutions for this issue. The one that worked for me is the following: | Another common error is the '''failed to find config ‘long-string-value’''' message. There are multiple possible solutions for this issue. The one that worked for me is the following: | ||
$ sudo runuser -u _gvm – gvmd --get-scanners | |||
sudo runuser -u _gvm – gvmd --get-scanners | |||
Note down the scanner ID. | Note down the scanner ID. | ||
Then run | Then run | ||
$ sudo runuser -u _gvm – gvmd --get-users --verbose | |||
sudo runuser -u _gvm – gvmd --get-users --verbose | |||
This gives you the users, including their IDs. You are probably an admin. To solve the issue, enter: | This gives you the users, including their IDs. You are probably an admin. To solve the issue, enter: | ||
$ sudo runuser -u _gvm – gvmd --modify-scanner [scanner id] --value [user id] | |||
[[Kategorie:Greenbone]] | |||
[[Kategorie:Greenbone |
Aktuelle Version vom 19. Oktober 2024, 10:14 Uhr
Problembehebung
There is a lot that can go wrong during the installation of OpenVAS as some of our readers has pointed out, therefore, we decided to create a little extra section here, covering the most common errors.
PostgreSQL Version Errors v13 and v14
There are multiple possible version errors for PostgreSQL. As our reader Tom has pointed out, the first one is:
[>] Starting PostgreSQL service[-] ERROR: The default PostgreSQL version (13) is not 14 that is required by libgvmd[-] ERROR: Use pg_upgradecluster to update your PostgreSQL cluster
Solution:
Open the postgresql.conf file of version 14 and change the port to 5432:
sudo nano /etc/postgresql/14/main/postgresql.conf
Then open the postgresql.conf file of version 13 and check if the port is the same as in version 14. If it is the same – change it to 5433:
sudo nano /etc/postgresql/13/main/postgresql.conf
Restart the PostgreSQL service:
sudo systemctl restart postgresql
PostgreSQL Version Errors v14 and v15
During my installation, I got the following error affecting v14 and v15 of PostgreSQL:
[>] Starting PostgreSQL service[-] ERROR: The default PostgreSQL version (14) is not 15 that is required by libgvmd[-] ERROR: Use pg_upgradecluster to update your PostgreSQL cluster
Gladly, the solution to this problem was easier than the one above and might as well work for the problem above:
sudo systemcctl stop postgresql@14-main sudo /usr/bin/pg_dropcluster --stop 14 main
OpenVAS failed to find config
Another common error is the failed to find config ‘long-string-value’ message. There are multiple possible solutions for this issue. The one that worked for me is the following:
$ sudo runuser -u _gvm – gvmd --get-scanners
Note down the scanner ID.
Then run
$ sudo runuser -u _gvm – gvmd --get-users --verbose
This gives you the users, including their IDs. You are probably an admin. To solve the issue, enter:
$ sudo runuser -u _gvm – gvmd --modify-scanner [scanner id] --value [user id]