Login problem after updating openvas!

Community Containers
1

Hello,

since the OpenVAS update, the login no longer works. It shows the message: “The Greenbone Vulnerability Manager service is not responding. This could be due to system maintenance. Please try again later, check the system status, or contact your system administrator.”

I already restarted the GVMD container, but unfortunately that didn’t help. I also noticed that the containers look strange and some of them are shown twice.

49315621db94 registry.community.greenbone.net/community/gsa:stable “/usr/local/bin/entr…” greenbone-community-edition-gsa-1
42ee4db3d38b registry.community.greenbone.net/community/gvmd:stable “/usr/local/bin/entr…” greenbone-community-edition-gvmd-1
a425fa0dc21c registry.community.greenbone.net/community/openvas-scanner:stable “/bin/sh -c /usr/loc…” greenbone-community-edition-openvasd-1
00e745a00441 registry.community.greenbone.net/community/openvas-scanner:stable “/bin/sh -c 'cat /et…” greenbone-community-edition-openvas-1
c536f6b8058a registry.community.greenbone.net/community/ospd-openvas:stable “/usr/bin/tini – /u…” greenbone-community-edition-ospd-openvas-1
8101265ba254 registry.community.greenbone.net/community/redis-server “docker-entrypoint.s…” greenbone-community-edition-redis-server-1
77a9e60f5c01 registry.community.greenbone.net/community/redis-server “docker-entrypoint.s…” greenbone-container-redis-server-1
8805b08e0349 45ea79725a80 “/usr/local/bin/entr…” greenbone-container-gvmd-1
34696de3da87 fc1bee1d8a8e “/bin/sh -c /usr/loc…” greenbone-container-openvasd-1
73dfc4fccd65 fc1bee1d8a8e "/bin/sh -c 'cat /et… greenbone-container-openvas-1
e2ebcf354323 147c9ba4bd25 “/usr/local/bin/entr…” greenbone-container-pg-gvm-1

GVMD Logs:
md main:WARNING:2025-12-02 14h47.24 utc:24: The gvmd data feed directory /var/lib/gvm/data-objects/gvmd or one of its subdirectories does not exist.
md manage:WARNING:2025-12-02 14h47.24 utc:39: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
md manage:WARNING:2025-12-02 14h47.34 utc:42: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
md manage:WARNING:2025-12-02 14h47.45 utc:45: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
md manage:WARNING:2025-12-02 14h47.55 utc:48: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
md manage:WARNING:2025-12-02 14h48.05 utc:51: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock
md manage:WARNING:2025-12-02 14h48.15 utc:54: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock

PG:
psql: error: connection to server on socket “/tmp/.s.PGSQL.5432” failed: No such file or directory
Is the server running locally and accepting connections on that socket?
createuser: error: connection to server on socket “/tmp/.s.PGSQL.5432” failed: No such file or directory
Is the server running locally and accepting connections on that socket?

What is the difference between greenbone-community-edition and greenbone-container?

1 Like
2

Hello,

I’d like to jump in here — I’m experiencing the same issue as described in the original post.
Even with a matching configuration, I’m running into the exact same error and haven’t been able to resolve it.

Maybe someone has an idea or could give a hint on what might be causing this?

Thanks in advance!

3

Hi,

same issue here. Ended up pinning the pg-gvm container to version 22.6.6 in the docker.compose.yml file. Works for me but maybe it’s not the best workaround (?).

pg-gvm:
image: registry.community.greenbone.net/community/pg-gvm:22.6.6