Gvm11 GUI not working for 'The Greenbone Vulnerability Manager service is not responding.'

tjdhwln · January 27, 2021, 3:14am

Hi,
I had successfully setup gvm 11 at my ubuntu 20 system and works well somedays , like using gui scan my systems, but yesterday. i met below issue can not resolved till now , Can anyone help??thanks you!

Error info when login my system with https://hostname/login

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.’*

then i checked log: at gsad.log

gsad main:WARNING:2021-01-27 03h08.39 utc:549: MHD: Error: received handshake message out of context

gsad main:WARNING:2021-01-27 03h08.41 utc:549: MHD: Error: received handshake message out of context

gsad gmp:WARNING:2021-01-27 03h08.48 utc:549: Failed to connect to server at /opt/gvm/var/run/gvmd.sock: No such file or directory

gsad gmp:WARNING:2021-01-27 03h08.48 utc:549: Authentication failure for ‘gvmadmin’ from 9.197.232.242. Status was 1.

cat gvmd.log
md manage:WARNING:2021-01-26 08h10.59 utc:800: init_manage_process: sql_open failed
md main:MESSAGE:2021-01-26 08h15.14 utc:808: Greenbone Vulnerability Manager version 20.08.0~git-97bdbeebb-gvmd-20.08 (GIT revision 97bdbeebb-gvmd-20.08) (DB revision 233)
md manage: INFO:2021-01-26 08h15.14 utc:808: Creating user.
md manage:WARNING:2021-01-26 08h15.14 utc:808: sql_open: PQconnectStart to ‘gvmd’ failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?
md manage:WARNING:2021-01-26 08h15.14 utc:808: init_manage_process: sql_open failed

GVM versions

gsad: (‘gsad --version’) Greenbone Security Assistant 20.08.0~git-fdd51705e-gsa-20.08
gvmd: (‘gvmd --version’)
20.08.0~git-97bdbeebb-gvmd-20.08

GIT revision 97bdbeebb-gvmd-20.08

Manager DB revision 233

License: AGPL-3.0-or-later
openvas-scanner: (‘openvas --version’, in older GVM versions < 11: ‘openvassd --version’)
gvm-libs:
OpenVAS 20.8.0

gvm-libs 20.8.0~git-e3351106-gvm-libs-20.08

Environment

**Operating system: ubuntu 20.04
Kernel: (‘uname -a’) Linux vm-133 5.4.0-62-generic #70-Ubuntu SMP Tue Jan 12 12:45:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Installation method / source:

bricks · January 27, 2021, 9:40am

Means gvmd is not running correctly and not listening on that socket anymore. And looking at the gvmd logs

it says the postgres db is not available anymore and therefore gvmd can’t start. It is very likely your postgres installation has changed.

tjdhwln · January 28, 2021, 1:50am

Bricks,
I am very appreciated your help!
I have solved my issue following your answer, I can share my solution , hope can help others:

this root cause is that I changed the key (ssl-cert-snakeoil.key)authority for some TLS testing. this lead to database can not be started. after i changed back, it works well ,thanks you!

private key file “/etc/ssl/private/ssl-cert-snakeoil.key” has group or world access
Jan 27 19:50:58 postgresql@12-main[3492]: 2021-01-27 19:50:58.075 EST [3504] DETAIL: *ile must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root.
Jan 27 19:50:58 postgresql@12-main[3492]: 2021-01-27 19:50:58.075 EST [3504] LOG: database system is shut down
Jan 27 19:50:58 postgresql@12-main[3492]: pg_ctl: could not start server

BTW, i still can not understand why database starting need this key??

Linuxintellect · July 29, 2021, 6:37am

@tjdhwln

Hi, I am appreciate your help for others.
As like you I’m facing the same issue. Can you please explain how you changed the the authority for TLS testing. It would be very much helpful for me and others.

Thanks in advance.

tjdhwln · July 29, 2021, 7:23am

I changed all files permissions under folder ‘/etc/ssl/private/’ to 755 because i executed other network applications TLS testing at same time, But postgres will not be started if key file “ /etc/ssl/private/ssl-cert-snakeoil.key ” has bigger right than 640

After i changed back as below, postgres started well. so the issue be fixed, Hope it helps, thanks!

total 20
4 -rw-r----- 1 root ssl-cert 1704 Jan 19 2021 ssl-cert-snakeoil.key