Ospd-openvas not starting after upgrade

I had Greenbone Community Edition installed from source on Ubuntu 22.04 from a couple years ago; didn’t record what exact version, but it warned me to update to a newer release. I ran through the uninstall and reinstall procedure, also upgrading the OS from 22.04 to 24.04 to fix libcurl version dependency, but now ospd-openvas service is not starting. Journalctl show this repeating over and over:

░░ A start job for unit ospd-openvas.service has begun execution.
░░
░░ The job identifier is 24158.
Oct 12 10:57:05 openvas systemd[1]: ospd-openvas.service: Main process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ An ExecStart= process belonging to unit ospd-openvas.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 203.
Oct 12 10:57:05 openvas systemd[1]: ospd-openvas.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit ospd-openvas.service has entered the ‘failed’ state with result ‘exit-code’.
Oct 12 10:57:05 openvas systemd[1]: Failed to start ospd-openvas.service - OSPd Wrapper for the OpenVAS Scanner (ospd-openvas).

Looking at /var/log/gvm, nothing new is being written into /var/log/gvm/ospd-openvas.log. All other services - gsad, gvmd, openvas, redis, postgres - appear to be running. Where can I look to diagnose this?

@bmekler start from log entries.

Eero

What log entries? Looking under /var/log/gvm, nothing new has been written since the upgrade to gsad.log, notus-scanner.log, openvas.log or ospd-openvas.log. In gvmd.log, the following repeats constantly:

update_scap: Updating data from feed
update_scap_cpes: No CPE dictionary found at /var/lib/gvm/scap-data/official-cpe-dictionary_v2.2.xml
osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock

Which makes sense, since ospd-openvas is not running, but I don’t have any clues as to why.

@bmekler run that service process (ospd) with strace to get information where it fails.

something like strace -s 255 command

You need to pick the command from systemd startup files

if its too hard to install then try this on debian:GitHub - Kastervo/OpenVAS-Installation: A secure, automated script to install and configure OpenVAS (Greenbone Community Edition) from source on Debian 12. Features GPG verification, self-signed SSL, and systemd integration.

Eero