immauss / openvas

Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
GNU Affero General Public License v3.0
366 stars 102 forks source link

[BUG] #302

Closed mnaismith closed 1 month ago

mnaismith commented 1 month ago

Hi,

All my scanners pulled in the latest version of the openvas container today and now all fail to start with the error below.

ERROR: relation "meta" does not exist LINE 1: select value from meta where name like 'database_version'; ^ Container stopped, performing shutdown waiting for server to shut down.... done

I can reproduce by running the below.

docker pull immauss/openvas docker rm openvas docker volume rm openvas docker volume create openvas docker run --detach --publish 127.0.0.1:8080:9392 --publish 127.0.0.1:9390:9390 -e SKIPSYNC=true -e PASSWORD="PASSWORD" --volume openvas:/data --name openvas immauss/openvas

I run this on Intel NUCS. 8GB RAM, M2 SSD. openvascontainerissue.txt

I have not yet looked into this but thought I'd better raise.

Cheers

Matt

immauss commented 1 month ago

@mnaismith Thanks for the heads up. Please pull the new latest and let me know if that resolves the issue.

Thanks, Scott

mnaismith commented 1 month ago

@immauss Yep all good thanks Scott and appreciate the speedy reply.

Matt

immauss commented 1 month ago

@mnaismith Thank you for finding that.

-Scott

TotalGriffLock commented 2 days ago

Just ran into this issue having followed the same steps as the OP

root@xyz:~# docker pull immauss/openvas
Using default tag: latest
latest: Pulling from immauss/openvas
Digest: sha256:0d1b245aa8ee3ed93aa63cce2a29a78e8f767ce379ae8edb83ab3b0b2a3bf1da
Status: Image is up to date for immauss/openvas:latest
docker.io/immauss/openvas:latest
root@xyz:~# docker image ls
REPOSITORY        TAG       IMAGE ID       CREATED        SIZE
immauss/openvas   latest    3c98390232be   15 hours ago   1.87GB

Then first start:

root@xyz:~# docker logs openvas
starting container ver 24.11.1 at: Thu Nov 21 16:42:58 UTC 2024
--- snip ---
Current GVMd database version is 250
Migrate the database if needed.

(gvmd:235): md manage-WARNING **: 16:43:01.908: sql_exec_internal: PQexec failed: ERROR:  role "dba" does not exist
 (7)

(gvmd:235): md manage-WARNING **: 16:43:01.908: sql_exec_internal: SQL: SET ROLE "dba";

(gvmd:235): md manage-WARNING **: 16:43:01.908: sqlv: sql_exec_internal failed
Container stopped, performing shutdown
waiting for server to shut down.... done
server stopped

Second start:

starting container ver 24.11.1 at: Thu Nov 21 16:43:13 UTC 2024
Looks like this container has already been started once.
--- snip ---
Checking DB Version
Container stopped, performing shutdown
ERROR:  relation "meta" does not exist
LINE 1: select value from meta where name like 'database_version';
                          ^
waiting for server to shut down.... done
server stopped

Is it possible this has regressed?

TotalGriffLock commented 1 day ago

Forcing 24.11.2 seems to work (as latest points to 24.11.1 still)