sysadmin@scanner:~$ sudo systemctl start gsad
Job for gsad.service failed because a timeout was exceeded.
See “systemctl status gsad.service” and “journalctl -xe” for details.
A start job for unit gsad.service has begun execution.
–
– The job identifier is 6415.
Okt 25 11:56:00 scanner gsad[7232]: Oops, secure memory pool already initialized
Okt 25 11:56:00 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?>
Okt 25 11:57:26 scanner sudo[7301]: sysadmin : TTY=pts/0 ; PWD=/etc/systemd/system ; USER=root>
Okt 25 11:57:26 scanner sudo[7301]: pam_unix(sudo:session): session opened for user root by sy>
Okt 25 11:57:30 scanner systemd[1]: gsad.service: start operation timed out. Terminating.
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Failed with result ‘timeout’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– The unit gsad.service has entered the ‘failed’ state with result ‘timeout’.
Okt 25 11:57:30 scanner systemd[1]: Failed to start Greenbone Security Assistant daemon (gsad).
– Subject: A start job for unit gsad.service has failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A start job for unit gsad.service has finished with a failure.
–
– The job identifier is 6415 and the job result is failed.
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Scheduled restart job, restart counter is at>
– Subject: Automatic restarting of a unit has been scheduled
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– Automatic restarting of the unit gsad.service has been scheduled, as the result for
– the configured Restart= setting for the unit.
Okt 25 11:57:30 scanner systemd[1]: Stopped Greenbone Security Assistant daemon (gsad).
– Subject: A stop job for unit gsad.service has finished
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A stop job for unit gsad.service has finished.
–
– The job identifier is 6493 and the job result is done.
Okt 25 11:57:30 scanner systemd[1]: Starting Greenbone Security Assistant daemon (gsad)…
– Subject: A start job for unit gsad.service has begun execution
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A start job for unit gsad.service has begun execution.
–
– The job identifier is 6493.
Okt 25 11:57:30 scanner gsad[7304]: Oops, secure memory pool already initialized
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?>
Okt 25 11:57:41 scanner sudo[7301]: pam_unix(sudo:session): session closed for user root
Please use the official install guide linked below step by step (make sure to not skip any, use the commands in separate terminals, …). By following this guide these issues shouldn’t occur.
something catched my eye in log
tail -f /var/log/gvm/gvmd.log
event config:MESSAGE:2022-10-25 10h02.58 UTC:21872: Scan config GaussDB Kernel V500R001C00 Security Hardening Guide (2eec8313-fee4-442a-b3c4-fa0d5dc83d61) has been created by admin
event config:MESSAGE:2022-10-25 10h02.58 UTC:21872: Scan config Host Discovery (2d3f051c-55ba-11e3-bf43-406186ea4fc5) has been created by admin
md gmp: INFO:2022-10-25 10h32.54 UTC:22584: Failed to parse client XML: Command Unavailable
md gmp: INFO:2022-10-25 10h49.34 UTC:23086: Failed to parse client XML: Command Unavailable
event user:MESSAGE:2022-10-25 10h50.04 UTC:23222: User admin_Clone_1 (9f017336-7e27-4f61-b9c6-0e841fe41780) has been created by admin
md gmp: INFO:2022-10-25 13h24.41 UTC:27001: Failed to parse client XML: Command Unavailable