Anyone else seeing a deluge of these messages in the logs?
main:WARNING:......: There was a problem trying to load ..... This may be due to a parse error, or it failed to find the dependency. Please check the path to the file.
The above link says it should resolve with a feed update, but it doesn't.
And anyone else getting subnet scans with and without exclusion being interrupted at 99%?
Nothing in the logs to indicate why, just says
OSPD 2021-03-27 23:15:10,880: INFO: (ospd.ospd) d82570be-b377-4b69-ae0c-0cfd017ca857: Scan stopped with errors.
OSPD 2021-03-27 23:15:10,880: INFO: (ospd.ospd) d82570be-b377-4b69-ae0c-0cfd017ca857: Scan interrupted.
Funny thing is that the scan for all the machines is completed, it just doesn't finish properly and gets interrupted. Started happening only in the last 2 weeks.
Report outdated / end-of-life Scan Engine / Environment (local)
This script checks and reports an outdated or end-of-life scan engine for the following environments:
Greenbone Source Edition (GSE)
Greenbone Security Manager TRIAL (formerly Greenbone Community Edition (GCE))
used for this scan.
NOTE: While this is not, in and of itself, a security vulnerability, a severity is reported to
make you aware of a possible decreased scan coverage or missing detection of vulnerabilities on
the target due to e.g.:
incompatibilities within the feed
Installed GVM Libraries (gvm-libs) version: 20.8.0
Latest available GVM Libraries (gvm-libs) version: 20.8.1
Reference URL(s) for the latest available version: https://community.greenbone.net/t/gvm-20-08-stable-initial-release-2020-08-12/6312
When trying to run the 21.04 without using old databases, I get this error:
9:C 28 Apr 2021 14:16:12.287 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9:C 28 Apr 2021 14:16:12.287 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=9, just started
9:C 28 Apr 2021 14:16:12.287 # Configuration loaded
Wait for redis socket to be created...
Testing redis status...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start....2021-04-28 14:16:13.327 UTC  LOG: starting PostgreSQL 12.6 (Ubuntu 12.6-1.pgdg20.10+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, 64-bit
2021-04-28 14:16:13.327 UTC  LOG: listening on IPv4 address "0.0.0.0", port 5432
2021-04-28 14:16:13.327 UTC  LOG: listening on IPv6 address "::", port 5432
2021-04-28 14:16:13.329 UTC  LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-04-28 14:16:13.340 UTC  LOG: database system was interrupted; last known up at 2021-04-28 14:16:09 UTC
2021-04-28 14:16:13.437 UTC  LOG: database system was not properly shut down; automatic recovery in progress
2021-04-28 14:16:13.438 UTC  LOG: redo starts at 0/1C98530
2021-04-28 14:16:13.441 UTC  LOG: invalid record length at 0/1D70788: wanted 24, got 0
2021-04-28 14:16:13.441 UTC  LOG: redo done at 0/1D70760
2021-04-28 14:16:13.501 UTC  LOG: database system is ready to accept connections
NOTICE: relation "vt_severities" already exists, skipping
Failed to connect to /var/run/ospd/ospd.sock.
Failed to rebuild NVT cache.
Hi @pixelsquared, not sure what happened, but somehow the reports are now working? This is what I recall doing:
1) renamed /var/lib/docker/volumes/gvm-data to something else (eg: /var/lib/docker/volumes/gvm-data.org)
2) created /var/lib/docker/volumes/gvm-data/_data
3) ran the docker command to start gvm
4) docker fails with "Failed to connect to /var/run/ospd/ospd.sock"
5) rm -f /var/lib/docker/volumes/gvm-data
6) mv /var/lib/docker/volumes/gvm-data.org /var/lib/docker/volumes/gvm-data
7) run docker command to start gvm
8) let it update all the nvts, cert and scap data
9) left it alone for about an hour or so (saw this in the last line of logs : "md main:MESSAGE:2021-04-28 15h07.26 utc:407: update_nvt_cache_retry: rebuild successful")
10) checked the reports and all were ok
11) ran a new scan and checked the report - also ok
Hi! I'd like to say that the comentation might be wrong! When I start with this:
docker run --detach --publish 8080:9392
I can't access, however, if I use like this:
docker run --detach --publish 9392:9392
It works! Am I right or misunderstood something?
Hi Eduardo! The port you exchanged for 9392 is the port mapped from the docker host to port 9392 inside the gvm container. Probably you have another container already using/mapping port 8080. Have you checked the docker/host logs for errors? Check output of "sudo netstat -tnlp|grep 8080" on the host for port 8080, as well as the output of "docker ps" (do "docker ps|grep 8080" or "sudo docker ps|grep 8080")
It was the only container running in my machine and one friend send the following command, that worked for me:
docker run -d -p 9392:9392 -p 9390:9390 -e PASSWORD="mypass" -v /gvm/data:/data --name gvm securecompliance/gvm:latest
Do you guys recognize any solution for this error?
There is this moment that a few errors appears:
Downloading data TAR to speed up first sync...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0curl: (6) Could not resolve host: vulndata.securecompliance.solutions
Extracting data TAR...
tar: can't open '/tmp/data.tar.xz': No such file or directory
cp: cannot stat '/tmp/data/nvt-feed/': No such file or directory
cp: cannot stat '/tmp/data/gvmd-data/': No such file or directory
cp: cannot stat '/tmp/data/scap-data/': No such file or directory
cp: cannot stat '/tmp/data/cert-data/': No such file or directory
rm: cannot remove '/tmp/data.tar.xz': No such file or directory