Setting up GVM11 - Revision history

Encode: Change link to Repositories page

2022-06-27T04:26:49Z

Change link to Repositories page

← Older revision		Revision as of 04:26, 27 June 2022
Line 7:		Line 7:

	= Install =		= Install =
	[[~~Enable_Community_Repository~~\|Enable the community repository]] and install the required packages:		[[Repositories#Enabling_the_community_repository\|Enable the community repository]] and install the required packages:

	{{Cmd\|apk add openvas openvas-config gvmd gvm-libs greenbone-security-assistant ospd-openvas}}		{{Cmd\|apk add openvas openvas-config gvmd gvm-libs greenbone-security-assistant ospd-openvas}}

2020-12-17T01:43:18Z

GVMd

← Older revision		Revision as of 01:43, 17 December 2020
Line 58:		Line 58:
	gvmd --get-users --verbose		gvmd --get-users --verbose

	Make sure that gvmd responds with "USER CREATED". If you run through these steps fast, and gvm is in the middle of something, it may not create the user until it is done with ~~whatever~~ it is computing.		Make sure that gvmd responds with "USER CREATED". If you run through these steps fast, and gvm is in the middle of something, it may not create the user until it is done with what it is computing.

	== Update GVM definitions ==		== Update GVM definitions ==

2020-12-17T01:43:08Z

GVMd

← Older revision		Revision as of 01:43, 17 December 2020
Line 57:		Line 57:

	gvmd --get-users --verbose		gvmd --get-users --verbose

			Make sure that gvmd responds with "USER CREATED". If you run through these steps fast, and gvm is in the middle of something, it may not create the user until it is done with whatever it is computing.

	== Update GVM definitions ==		== Update GVM definitions ==

2020-12-15T07:06:20Z

greenbone-nvt-sync can't create /run/ospd/feed-update.lock

← Older revision		Revision as of 07:06, 15 December 2020
Line 98:		Line 98:

	==greenbone-nvt-sync can't create /run/ospd/feed-update.lock==		==greenbone-nvt-sync can't create /run/ospd/feed-update.lock==
	If during the first greenbone-nvt-sync, you get an error about can't create /run/ospd/feed-update.lock permission denied you might've run ospd / openvas too early. In /var/log/gvm/openvas.log there will be a loop where ospd is looking for the feed files which don't exist. Kill the process, then manually remove the lock file.		If during the first greenbone-nvt-sync, or greenbone-feed-sync, you get an error about can't create /run/ospd/feed-update.lock permission denied you might've run ospd / openvas too early. In /var/log/gvm/openvas.log there will be a loop where ospd is looking for the feed files which don't exist. Kill the process, then manually remove the lock file. However, if it looks like it is actively syncing the feed (iftop), then let it complete the sync first.

	[[Category:Server]]		[[Category:Server]]
	[[Category:Monitoring]]		[[Category:Monitoring]]

2020-12-15T01:04:49Z

Configuration

← Older revision		Revision as of 01:04, 15 December 2020
Line 95:		Line 95:
	Happy vulnerability assestment!		Happy vulnerability assestment!

	==Troubleshooting==		=Troubleshooting=

	===greenbone-nvt-sync can't create /run/ospd/feed-update.lock===		==greenbone-nvt-sync can't create /run/ospd/feed-update.lock==
	If during the first greenbone-nvt-sync, you get an error about can't create /run/ospd/feed-update.lock permission denied you might've run ospd / openvas too early. In /var/log/gvm/openvas.log there will be a loop where ospd is looking for the feed files which don't exist. Kill the process, then manually remove the lock file.		If during the first greenbone-nvt-sync, you get an error about can't create /run/ospd/feed-update.lock permission denied you might've run ospd / openvas too early. In /var/log/gvm/openvas.log there will be a loop where ospd is looking for the feed files which don't exist. Kill the process, then manually remove the lock file.

	[[Category:Server]]		[[Category:Server]]
	[[Category:Monitoring]]		[[Category:Monitoring]]

2020-12-15T01:04:33Z

Troubleshooting tips

← Older revision		Revision as of 01:04, 15 December 2020
Line 79:		Line 79:
	su - gvm		su - gvm
	greenbone-nvt-sync		greenbone-nvt-sync

	If you get an error about can't create /run/ospd/feed-update.lock permission denied, check that gvmd is not running in the background performing a sync (with significant cpu usage) via top. If it is, wait for it to complete.

	== Greenbone Security Assistant (GSAD) ==		== Greenbone Security Assistant (GSAD) ==
Line 96:		Line 94:

	Happy vulnerability assestment!		Happy vulnerability assestment!

			==Troubleshooting==

			===greenbone-nvt-sync can't create /run/ospd/feed-update.lock===
			If during the first greenbone-nvt-sync, you get an error about can't create /run/ospd/feed-update.lock permission denied you might've run ospd / openvas too early. In /var/log/gvm/openvas.log there will be a loop where ospd is looking for the feed files which don't exist. Kill the process, then manually remove the lock file.

	[[Category:Server]]		[[Category:Server]]
	[[Category:Monitoring]]		[[Category:Monitoring]]

2020-12-15T00:48:28Z

Update GVM definitions

← Older revision		Revision as of 00:48, 15 December 2020
Line 67:		Line 67:
	greenbone-feed-sync --type SCAP		greenbone-feed-sync --type SCAP
	greenbone-feed-sync --type CERT		greenbone-feed-sync --type CERT
			exit

	This three feeds needs to be scheduled via cron.		This three feeds needs to be scheduled via cron.
Line 78:		Line 79:
	su - gvm		su - gvm
	greenbone-nvt-sync		greenbone-nvt-sync

			If you get an error about can't create /run/ospd/feed-update.lock permission denied, check that gvmd is not running in the background performing a sync (with significant cpu usage) via top. If it is, wait for it to complete.

	== Greenbone Security Assistant (GSAD) ==		== Greenbone Security Assistant (GSAD) ==

2020-12-14T23:00:40Z

GVMd

← Older revision		Revision as of 23:00, 14 December 2020
Line 45:		Line 45:

	rc-service gvmd start		rc-service gvmd start
			su - gvm
	gvmd --create-user=admin --password=admin		gvmd --create-user=admin --password=admin

2020-12-14T22:58:55Z

missing exits: postgres user can't su to gvm

← Older revision		Revision as of 22:58, 14 December 2020
Line 33:		Line 33:
	create extension "pgcrypto";		create extension "pgcrypto";
	exit		exit
			exit
	== GVMd ==		== GVMd ==

Line 41:		Line 41:
	su - gvm		su - gvm
	gvm-manage-certs -a		gvm-manage-certs -a
			exit
	Create credentials used to interact with gvmd:		Create credentials used to interact with gvmd:

2020-12-14T09:37:15Z

gvm user cannot be created if daemon is not started

← Older revision		Revision as of 09:37, 14 December 2020
Line 44:		Line 44:
	Create credentials used to interact with gvmd:		Create credentials used to interact with gvmd:

			rc-service gvmd start
	gvmd --create-user=admin --password=admin		gvmd --create-user=admin --password=admin

Line 67:		Line 68:

	This three feeds needs to be scheduled via cron.		This three feeds needs to be scheduled via cron.

	~~rc-service gvmd start~~

	Add gvmd to start on boot:		Add gvmd to start on boot: