Hi, I installed greenbone community edition on container.
but when i try to access it from a different application i can’t. i get gvmd socket error. below is the output of /var/log/gvm/gvmd.log
sudo cat /var/log/gvm/gvmd.log
md main:MESSAGE:2025-04-08 07h28.14 utc:244659: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h28.14 utc:244660: sql_open: PQconnectStart to 'gvmd' failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
md manage:WARNING:2025-04-08 07h28.14 utc:244660: init_manage_open_db: sql_open failed
md main:MESSAGE:2025-04-08 07h50.30 utc:247768: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h50.30 utc:247768: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 07h50.30 utc:247768: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 07h50.30 utc:247770: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h50.30 utc:247770: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 07h50.30 utc:247770: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 07h50.31 utc:247772: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h50.31 utc:247772: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 07h50.31 utc:247772: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 07h50.31 utc:247774: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h50.31 utc:247774: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 07h50.31 utc:247774: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 07h50.31 utc:247776: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 07h50.31 utc:247776: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 07h50.31 utc:247776: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h00.50 utc:261005: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h00.50 utc:261005: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 13h00.50 utc:261005: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h00.51 utc:261007: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h00.51 utc:261007: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 13h00.51 utc:261007: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h00.51 utc:261009: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h00.51 utc:261009: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 13h00.51 utc:261009: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h00.51 utc:261011: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h00.51 utc:261011: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 13h00.51 utc:261011: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h00.52 utc:261013: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h00.52 utc:261013: Failed to open lock file '/var/lib/openvas/gvm-checking': Permission denied
md main:CRITICAL:2025-04-08 13h00.52 utc:261013: gvmd: Error trying to get checking lock
md main:MESSAGE:2025-04-08 13h02.05 utc:261057: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h02.05 utc:261058: sql_open: PQconnectStart to 'gvmd' failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
md manage:WARNING:2025-04-08 13h02.05 utc:261058: init_manage_open_db: sql_open failed
md main:MESSAGE:2025-04-08 13h04.09 utc:261136: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h04.09 utc:261137: sql_open: PQconnectStart to 'gvmd' failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
md manage:WARNING:2025-04-08 13h04.09 utc:261137: init_manage_open_db: sql_open failed
md main:MESSAGE:2025-04-08 13h05.07 utc:261179: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h05.07 utc:261180: sql_open: PQconnectStart to 'gvmd' failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
md manage:WARNING:2025-04-08 13h05.07 utc:261180: init_manage_open_db: sql_open failed
md main:MESSAGE:2025-04-08 13h06.05 utc:261279: Greenbone Vulnerability Manager version 23.1.0 (DB revision 255)
md manage:WARNING:2025-04-08 13h06.05 utc:261280: sql_open: PQconnectStart to 'gvmd' failed: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
md manage:WARNING:2025-04-08 13h06.05 utc:261280: init_manage_open_db: sql_open failed
Additionally I have two possible causes in mind for your issue
Not enough disk space in /var/lib. Please check the disk space on your docker host.
The volume for the postgres unix socket is broken (happened to other users already for unknown reasons). You could shutdown all containers, delete the psql_socket_vol and restart the containers. The volume will be re-created automatically.
I stopped all containers as you mentioned and deleted the psql volume. However, the situation is still the same in socket creation. below I share a different error output: