GVM Not Starting-timing out

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

I saw a post come up similar, but there is no link to be able to look at the post.
Also, the advice was to “see…etc.” I don’t know what that means. Someone else posted a log. Again, I wouldn’t know what to look for or what to do about it. I have installed openvas a few times and not gotten this message. The check setup said it was good…

Same as in GVM Not Updating Feed or Scan Configs - #2 by bricks you need to take a look at the logs for error messages.

Please take a look at Troubleshooting - Greenbone Community Documentation too

1 Like

The commands systemctl status gvmd.service and journalctl -xeu gvmd.service mentioned in in the service failing to start will print output to your terminal that may clearly describe the error. Otherwise, the /var/log/gvm/gvmd.log file needs to be reviewed for critical errors that prevent startup.

1 Like