GVMD service error

vif · April 8, 2025, 1:16pm

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

bricks · April 9, 2025, 6:28am

Hi, could you check the output of the postgres container

docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs pg-gvm

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.

vif · April 9, 2025, 7:25am

There seems to be enough space on the /var/lib/ disk.

df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           790M  2.9M  787M   1% /run
/dev/sda2        98G   47G   46G  51% /
tmpfs           3.9G  1.1M  3.9G   1% /dev/shm
tmpfs           5.0M  8.0K  5.0M   1% /run/lock
tmpfs           790M   96K  790M   1% /run/user/120
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/da363e2ed46213a5a0650c351875e3746aaa80e93ef409803bcd3c3431e6329d/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/941f2ec63336cc3c008e7b25aa1a824569de576ab762e997bf5b7453737f98d9/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/9021b37984e86afc2f34d4d39cac49d86b36d69973285e9d185e75bc8463fee4/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/af0a7b3acce8d212df364ef355188e88f88c7e95435c2d933c369920977ab350/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/f7d6bdeb026667763ecf2842a5b80614bb1cbf4adf274e69cc761c82740a4bd4/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/7ac6cdc2c315274cc903051b077b83597e183f3656cee409f8569dfa8383eb55/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/5eb70103a50b621cc38f16c039c77b5a634ab1c67d48fcc2a35207e1d006fad2/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/bd632df086d2dc5a7b841a81ac561fed1396d1040a36af4a6e3955ec4dc544d7/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/6084c9dd28290544824c9a2b565dddb63657c082ebc40b46902614d70251920e/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/de9333b7b6717c564247059facdd791ae0535c4c8db8868c2c95c0bb7835bce5/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/a7f417149f12042716590f4ecd5218e7d5db5bb220874e8d53191e701a3ca1ed/merged
overlay          98G   47G   46G  51% /var/lib/docker/overlay2/0e1d542ebe9f886638f2581e4d0f3c850326530b98a7dfad5767ae96272051a0/merged
tmpfs           790M   80K  790M   1% /run/user/0

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:

sudo find /run -name “gvmd.sock”
find: ‘/run/user/120/doc’: Permission denied

journalctl -u gvmd.service -n 50 --no-pager

Apr 08 03:50:30 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 03:50:30 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 03:50:30 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 03:50:31 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 2.

Apr 08 03:50:31 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 03:50:31 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 03:50:31 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 3.

Apr 08 03:50:31 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 03:50:31 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 03:50:31 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 4.

Apr 08 03:50:31 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 03:50:31 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 03:50:31 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 5.

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Start request repeated too quickly.**

Apr 08 03:50:31 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 03:50:31 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:50 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 09:00:50 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 09:00:50 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:50 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:51 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 1.

Apr 08 09:00:51 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:51 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:51 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 2.

Apr 08 09:00:51 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:51 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:51 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 3.

Apr 08 09:00:51 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 09:00:51 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:51 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:52 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 4.

Apr 08 09:00:52 pc systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...

Apr 08 09:00:52 pc systemd[1]: **gvmd.service: Control process exited, code=exited, status=1/FAILURE**

Apr 08 09:00:52 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:52 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**

Apr 08 09:00:52 pc systemd[1]: gvmd.service: Scheduled restart job, restart counter is at 5.

Apr 08 09:00:52 pc systemd[1]: **gvmd.service: Start request repeated too quickly.**

Apr 08 09:00:52 pc systemd[1]: **gvmd.service: Failed with result 'exit-code'.**

Apr 08 09:00:52 pc systemd[1]: **Failed to start gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).**