-
-
Notifications
You must be signed in to change notification settings - Fork 113
Open
Description
Tried to update my image from immauss/openvas:25.08.28.01 to the latest from 2025-10-25.
Container is not starting correctly, shuts down and repeats forever. See the logs below.
Switching back to immauss/openvas:25.08.28.01: No problem!
starting container ver 25.06.01 at: Tue Oct 28 13:46:02 UTC 2025
Setting up container filesystem
Creating needed Directories
Validating other directories
Create gvm user
Setting up soft links
/data/database/base already exists ...
NOT moving data from image to /data
/usr/local/var/lib
/usr/local/var/log
/var/log
Setting up logs
Fixing local/share
Fixing run
Fixing /var/lib/gvm
Fixing /var/lib/notus
Fixing /var/lib/openvas
Handling config files
Fixing some permissions
All done ... mark the container as setup and ready
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
waiting for server to start..............................2025-10-28 13:46:33.274 UTC [102] LOG: redirecting log output to logging collector process
2025-10-28 13:46:33.274 UTC [102] HINT: Future log output will appear in directory "/data/var-log/postgresql".
done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Creating dir structure for feed sync
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
starting container ver 25.06.01 at: Tue Oct 28 13:46:34 UTC 2025
Looks like this container has already been started once.
Just doing a little cleanup instead of the whole fs-setup.
-rw-r--r-- 1 root root 0 Oct 28 13:46 /.fs-setup-complete
removing Socket files ....
removing pids
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start..............................2025-10-28 13:47:02.905 UTC [27] LOG: redirecting log output to logging collector process
2025-10-28 13:47:02.905 UTC [27] HINT: Future log output will appear in directory "/data/var-log/postgresql".
. done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
starting container ver 25.06.01 at: Tue Oct 28 13:47:04 UTC 2025
Looks like this container has already been started once.
Just doing a little cleanup instead of the whole fs-setup.
-rw-r--r-- 1 root root 0 Oct 28 13:46 /.fs-setup-complete
removing Socket files ....
removing pids
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start.............................2025-10-28 13:47:31.513 UTC [27] LOG: redirecting log output to logging collector process
2025-10-28 13:47:31.513 UTC [27] HINT: Future log output will appear in directory "/data/var-log/postgresql".
. done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
starting container ver 25.06.01 at: Tue Oct 28 13:47:32 UTC 2025
Looks like this container has already been started once.
Just doing a little cleanup instead of the whole fs-setup.
-rw-r--r-- 1 root root 0 Oct 28 13:46 /.fs-setup-complete
removing Socket files ....
removing pids
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start..............................2025-10-28 13:48:00.961 UTC [27] LOG: redirecting log output to logging collector process
2025-10-28 13:48:00.961 UTC [27] HINT: Future log output will appear in directory "/data/var-log/postgresql".
. done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
starting container ver 25.06.01 at: Tue Oct 28 13:48:02 UTC 2025
Looks like this container has already been started once.
Just doing a little cleanup instead of the whole fs-setup.
-rw-r--r-- 1 root root 0 Oct 28 13:46 /.fs-setup-complete
removing Socket files ....
removing pids
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start...............................2025-10-28 13:48:31.055 UTC [27] LOG: redirecting log output to logging collector process
2025-10-28 13:48:31.055 UTC [27] HINT: Future log output will appear in directory "/data/var-log/postgresql".
done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
starting container ver 25.06.01 at: Tue Oct 28 13:48:32 UTC 2025
Looks like this container has already been started once.
Just doing a little cleanup instead of the whole fs-setup.
-rw-r--r-- 1 root root 0 Oct 28 13:46 /.fs-setup-complete
removing Socket files ....
removing pids
Choosing container start method from:
Nothing ... so we start in the default of single container mode
Starting gvmd & openvas in a single container !!
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating postgresql.conf and pg_hba.conf
Starting PostgreSQL...
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start..............................2025-10-28 13:48:59.997 UTC [27] LOG: redirecting log output to logging collector process
2025-10-28 13:48:59.997 UTC [27] HINT: Future log output will appear in directory "/data/var-log/postgresql".
done
server started
pg exit with 0 .
Checking for existing DB
Running first start configuration...
CREATE_EMPTY_DATABASE=false
LOADDEFAULT=false
Checking DB Version
Current GVMd database version is 262
Migrate the database if needed.
Container stopped, performing shutdown
docker-compose.yml:
services:
openvas:
ports:
- "127.0.0.1:8080:9392"
environment:
- "PASSWORD=xxxxxx"
- "USERNAME=admin"
- "RELAYHOST=172.17.0.1"
- "SMTPPORT=25"
- "REDISDBS=512" # number of Redis DBs to use
- "QUIET=false" # dump feed sync noise to /dev/null
- "NEWDB=false" # only use this for creating a blank DB
- "SKIPSYNC=false" # Skips the feed sync on startup.
- "RESTORE=false" # This probably not be used from compose... see docs.
- "DEBUG=false" # This will cause the container to stop and not actually start gvmd
- "HTTPS=false" # wether to use HTTPS or not
- "GMP=9390" # to enable see docs
- "GSATIMEOUT=120" # Configurable session timeout in minutes
volumes:
- "openvas:/data"
container_name: openvas
image: immauss/openvas:25.08.28.01
# image: immauss/openvas:latest
deploy:
restart_policy:
condition: unless-stopped
delay: 10s
window: 120s
volumes:
openvas:
Metadata
Metadata
Assignees
Labels
No labels