GSAD Problems

Asking for Help…

Job for gsad.service failed because a timeout was exceeded.
See “systemctl status gsad.service” and “journalctl -xeu gsad.service” for details.

ERROR: gsad service did not start.
Please check journalctl -xe and /var/log/gvm/gsad.log

journalctl -xe
No visible errors regarding gsad

systemctl status gsad.service
● gsad.service - Greenbone Security Assistant daemon (gsad)
Loaded: loaded (/lib/systemd/system/gsad.service; disabled; preset: disabled)
Active: activating (start) since Thu 2022-09-22 16:07:26 UTC; 11s ago
Docs: man:gsad(8)
Process: 3954 ExecStart=/usr/sbin/gsad --listen --port 9392 (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 18717)
Memory: 2.4M
CPU: 27ms
CGroup: /system.slice/gsad.service
└─3955 /usr/sbin/gsad --listen --port 9392

gsad main:MESSAGE:2022-09-22 16h14.58 utc:4374: Starting GSAD version 21.4.4
gsad main:WARNING:2022-09-22 16h14.58 utc:4376: main: start_http_daemon redirect failed !
When opening Web browser manually and trying to login:
● I do LOGIN as Admin
● Selected task runs
● A couple of times or more it returned to the login screen, logged in again and it was running as before.
● Eventually, scanning was completed successfully and reporting was as expected.

Now, systemctl status gsad.service returns:
Active: active (running) since Thu 2022-09-22 16:30:03 UTC; 18min ago

and gvm-stop returns (standing out with yellow fonts)
gsad.service: Supervising process 9794 which is not our child. We’ll most likely not notice when it exits.

I would very much appreciate any ideas regarding this problem…
Thank you in advance!


Please always mention where you did get our software from. I suppose it is Kali.

This issue is very likely already fixed with Change service start up type from forking to exec by rfc6919 · Pull Request #84 · greenbone/gsad · GitHub and has been discussed in Gsad.service activating - #13 by russm before

1 Like

Yes, it’s Kali!

Thank you for your response and sorry for skipping that.

I’ will apply the changes and try again.

Everything is OK now.

Thanks a lot for your instructions; I appreciate it!