Cant login into GSA after editing gvmd

Archive Greenbone Community Edition
1

Hi,
i am a little confused about my gvmd.service.

[Service]
Type=forking
User=gvm
Group=gvm
PIDFile=/opt/gvm/var/run/gvmd.pid
WorkingDirectory=/opt/gvm
ExecStart=/opt/gvm/sbin/gvmd -a 0.0.0.0 -p 9390 --osp-vt-update=/opt/gvm/var/run/ospd.sock
ExecReload=/bin/kill -HUP $MAINPID
KillMode=mixed
Restart=on-failure
RestartSec=2min
KillMode=process
KillSignal=SIGINT
GuessMainPID=no
PrivateTmp=true

when i add the -a and -p parameter, i am not able to login in my gsa anymore.
It says its not reacting.

What am i doing wrong?

2

If you change the gvmd so that it is listening on a TCP port instead of a unix socket then AFAIK you need to reconfigure the gsad to use that TCP port with something like e.g.:

 --mlisten=$managerip --mport=9390
1 Like
3

Yes i did that too.
My gsad.service looks like

[Service]
Type=forking
PIDFile=/opt/gvm/var/run/gsad.pid
WorkingDirectory=/opt/gvm
ExecStart=/opt/gvm/sbin/gsad --mport=9390 --mlisten=1.2.3.4 --drop-privileges=gvm --ssl-private-key=/opt/gvm/sbin/private.pem --ssl-certificate=/opt/gvm/sbin/certificate.pem --timeout=3600 --munix-socket=/opt/gvm/var/run/gvmd.sock
Restart=on-failure
RestartSec=2min
KillMode=process
KillSignal=SIGINT
GuessMainPID=no
PrivateTmp=true

so i am really confused why i cant login anymore

4

Probably something blocking the TCP communication (local firewall, SElinux, …).

5

Hm i checked this too. Local Firewall is even disabled. My TCP connections works but login into the webGUI is not possible anymore. This is really strange behaviour.

I hope someone has an idea how to fix this?

6

Change to a file socked connection.

7

Is there no easier way?
I dont know what it needs for getting that code working and this is not in the scope of this community i guess.

8

Yes use the Community Edition, that is turnkey.

9

Alright, thank you. If I don’t get this done I’ll use the community edition :slight_smile:

10

Mhhh, have you tried to remove the --munix-socket ? I’m not sure how gsad is behaving if that is specified in addition to the --mlisten and --mport.

11

Thank you, that was it! Works fine now :slight_smile:

1 Like