shandshellin
commented
1 year ago HEALTHECHECK FAILED ! These services failed openvas gvmd gsad HEALTHECHECK FAILED ! These services failed openvas gvmd gsad HEALTHECHECK FAILED ! These services failed openvas gvmd gsad postgresql HEALTHECHECK FAILED ! These services failed openvas gvmd gsad redis HEALTHECHECK FAILED ! These services failed openvas gvmd gsad redis HEALTHECHECK FAILED ! These services failed openvas gvmd gsad redis HEALTHECHECK FAILED ! These services failed openvas gvmd gsad redis
immauss
I'm running this as a service in docker swarm on arm. I setup persistent storage with bind but i'm seeing errors like this and no web interface. Can you confirm this image works? Am i missing something? This is not running detached or privilaged but shouldn't matter for this. Persistent storage is /data port 9392.
openvas.1.z0ioqw7muc6b@Cluster7 | starting container at: Sun Apr 9 18:44:19 UTC 2023 openvas.1.z0ioqw7muc6b@Cluster7 | Setting up container filesystem openvas.1.z0ioqw7muc6b@Cluster7 | /data/database/base alredy exists ... openvas.1.z0ioqw7muc6b@Cluster7 | NOT moving data from image to /data openvas.1.z0ioqw7muc6b@Cluster7 | cp: cannot stat '/usr/local/var/lib/': No such file or directory openvas.1.z0ioqw7muc6b@Cluster7 | cp: cannot stat '/var/lib/gvm/': No such file or directory openvas.1.z0ioqw7muc6b@Cluster7 | cp: cannot stat '/var/lib/notus/': No such file or directory openvas.1.z0ioqw7muc6b@Cluster7 | cp: cannot stat '/var/lib/openvas/': No such file or directory openvas.1.z0ioqw7muc6b@Cluster7 | Using existing gvm logging config openvas.1.z0ioqw7muc6b@Cluster7 | Using existing password policy config openvas.1.z0ioqw7muc6b@Cluster7 | Using existing openvas logging config openvas.1.z0ioqw7muc6b@Cluster7 | chown: cannot access '/run/postgres': No such file or directory openvas.1.z0ioqw7muc6b@Cluster7 | Choosing container start method from: openvas.1.z0ioqw7muc6b@Cluster7 | openvas.1.z0ioqw7muc6b@Cluster7 | Starting gvmd & openvas in a single container !! openvas.1.z0ioqw7muc6b@Cluster7 | Wait for redis socket to be created... openvas.1.z0ioqw7muc6b@Cluster7 | Testing redis status... openvas.1.z0ioqw7muc6b@Cluster7 | Redis ready. openvas.1.z0ioqw7muc6b@Cluster7 | Creating postgresql.conf and pg_hba.conf openvas.1.z0ioqw7muc6b@Cluster7 | Starting PostgreSQL... openvas.1.z0ioqw7muc6b@Cluster7 | pg_ctl: another server might be running; trying to start server anyway openvas.1.z0ioqw7muc6b@Cluster7 | waiting for server to start....2023-04-09 18:47:58.699 UTC [119] LOG: redirecting log output to logging collector process openvas.1.z0ioqw7muc6b@Cluster7 | 2023-04-09 18:47:58.699 UTC [119] HINT: Future log output will appear in directory "/data/var-log/postgresql". openvas.1.z0ioqw7muc6b@Cluster7 | ............ done openvas.1.z0ioqw7muc6b@Cluster7 | server started openvas.1.z0ioqw7muc6b@Cluster7 | pg exit with 0 . openvas.1.z0ioqw7muc6b@Cluster7 | Checking for existing DB openvas.1.z0ioqw7muc6b@Cluster7 | Running first start configuration... openvas.1.z0ioqw7muc6b@Cluster7 | Checking DB Version openvas.1.z0ioqw7muc6b@Cluster7 | Current GVMd database version is 250 openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | NOTICE: relation "vt_severities" already exists, skipping openvas.1.z0ioqw7muc6b@Cluster7 | Migrate the database if needed. openvas.1.z0ioqw7muc6b@Cluster7 | Updating NVTs and other data openvas.1.z0ioqw7muc6b@Cluster7 | This could take a while if you are not using persistent storage for your NVTs openvas.1.z0ioqw7muc6b@Cluster7 | or this is the first time pulling to your persistent storage. openvas.1.z0ioqw7muc6b@Cluster7 | the time will be mostly dependent on your available bandwidth. openvas.1.z0ioqw7muc6b@Cluster7 | We sleep for 2 seconds between sync command to make sure everything closes openvas.1.z0ioqw7muc6b@Cluster7 | and it doesnt' look like we are connecting more than once. openvas.1.z0ioqw7muc6b@Cluster7 | Pulling NVTs from greenbone openvas.1.z0ioqw7muc6b@Cluster7 | <28>Apr 9 18:48:16 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream. openvas.1.z0ioqw7muc6b@Cluster7 | <29>Apr 9 18:48:16 greenbone-nvt-sync: No Greenbone Security Feed access key found, falling back to Greenbone Community Feed