Gsad.service not restarting after editing --listen IP

Getting Started
1

hello,

we installed the greenbone community edition 22.4 from Soucre on a ubuntu server LTS 22.04.1. Everything is looking good so far.
The services are all up and running, the problem accours when editing the gsad.service to change the --listen address from localhost 127.0.0.1 to the real IP address of the system. Its a class a IPv4 address similar to 73.235.185.163.
After the change is made, the service doesn’t start again.

gsad.service running:

root@xxx:/etc/systemd/system# sudo systemctl status gsad
● gsad.service - Greenbone Security Assistant daemon (gsad)
Loaded: loaded (/etc/systemd/system/gsad.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-02-13 10:41:48 CET; 4s ago
Docs: man:gsad(8)
https://www.greenbone.net
Main PID: 131441 (gsad)
Tasks: 2 (limit: 9530)
Memory: 1.5M
CPU: 10ms
CGroup: /system.slice/gsad.service
└─131441 /usr/local/sbin/gsad --foreground --listen=127.0.0.1 --port=9392 --http-only

Feb 13 10:41:48 xxx systemd[1]: Starting Greenbone Security Assistant daemon (gsad)…
Feb 13 10:41:48 xxx systemd[1]: Started Greenbone Security Assistant daemon (gsad).

gsad.service not starting after editing the --listen parameter:

root@xxx:/etc/systemd/system# sudo systemctl status gsad
× gsad.service - Greenbone Security Assistant daemon (gsad)
Loaded: loaded (/etc/systemd/system/gsad.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-02-13 10:41:13 CET; 5s ago
Docs: man:gsad(8)
https://www.greenbone.net
Process: 131375 ExecStart=/usr/local/sbin/gsad --foreground --listen=xxx.xxx.xxx.xxx --port=9392 --http-only (code=exited, status=1/FAILURE)
Main PID: 131375 (code=exited, status=1/FAILURE)
CPU: 9ms

Feb 13 10:41:13 xxx systemd[1]: gsad.service: Scheduled restart job, restart counter is at 5.
Feb 13 10:41:13 xxx systemd[1]: Stopped Greenbone Security Assistant daemon (gsad).
Feb 13 10:41:13 xxx systemd[1]: gsad.service: Start request repeated too quickly.
Feb 13 10:41:13 xxx systemd[1]: gsad.service: Failed with result ‘exit-code’.
Feb 13 10:41:13 xxx systemd[1]: Failed to start Greenbone Security Assistant daemon (gsad).

Thats the content from gsad.log:

gsad main:MESSAGE:2023-02-13 07h38.04 utc:126297: Starting GSAD version 22.04.1
gsad main:MESSAGE:2023-02-13 07h50.49 utc:127532: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h50.49 utc:127532: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h50.49 utc:127535: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h50.49 utc:127535: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h50.49 utc:127537: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h50.49 utc:127537: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h50.50 utc:127538: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h50.50 utc:127538: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h50.50 utc:127539: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h50.50 utc:127539: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h51.49 utc:127586: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h51.49 utc:127586: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h51.49 utc:127589: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h51.49 utc:127589: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h51.49 utc:127590: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h51.49 utc:127590: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h51.50 utc:127591: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h51.50 utc:127591: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h51.50 utc:127592: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h51.50 utc:127592: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h53.18 utc:127735: Starting GSAD version 22.04.1
gsad main:MESSAGE:2023-02-13 07h54.19 utc:127830: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h54.19 utc:127830: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h54.19 utc:127831: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h54.19 utc:127831: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h54.19 utc:127832: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h54.19 utc:127832: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h54.19 utc:127833: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h54.19 utc:127833: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 07h54.20 utc:127834: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 07h54.20 utc:127834: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 08h53.32 utc:129724: Starting GSAD version 22.04.1
gsad main:MESSAGE:2023-02-13 09h38.23 utc:131104: Starting GSAD version 22.04.1
gsad main:MESSAGE:2023-02-13 09h39.05 utc:131184: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h39.05 utc:131184: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h39.05 utc:131186: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h39.05 utc:131186: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h39.05 utc:131187: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h39.05 utc:131187: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h39.06 utc:131188: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h39.06 utc:131188: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h39.06 utc:131189: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h39.06 utc:131189: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.12 utc:131371: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h41.12 utc:131371: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.12 utc:131372: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h41.12 utc:131372: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.12 utc:131373: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h41.12 utc:131373: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.13 utc:131374: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h41.13 utc:131374: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.13 utc:131375: Starting GSAD version 22.04.1
gsad main:CRITICAL:2023-02-13 09h41.13 utc:131375: main: start_https_daemon failed!
gsad main:MESSAGE:2023-02-13 09h41.48 utc:131441: Starting GSAD version 22.04.1

Does anyone have an idea of what went wrong? Help is appreciated.
Thank you for time and help!

Best regards Matthias

2

hello again, i foregot to mention that if we change the --listen IP address back to the localhost address the gsad.service is starting again without problems.

3

Hi,

You need to find out why the binding failed, should be a local issue.

First i would disable all dynamic tools like Network Manager, firewall etc … and change to a static IP. Then you can check with ip and ss if binding to that IP is possible and the other daemons can connect as well.

1 Like
4

hello Lukas,

thank you for the tipp, it was very helpfull and pointed me in the right direction. The Prolbem accoured because the IP-address allocation of the cloud provider.
In short, i accidentally configured a nonexisting IP-address to the gsad.service and because of that it refused to start.

Thank you for the right thought and topic closed.

1 Like