WARN openvasd: OSPD socket /var/run/ospd/ospd.sock does not exist (Build from Source)

Building from Source and Advanced Topics
1

I just built the community edition from source and am receiving the following output from the command

systemctl status openvasd

● openvasd.service - OpenVASD
     Loaded: loaded (/etc/systemd/system/openvasd.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-07-25 04:25:39 UTC; 1h 7min ago
       Docs: https://github.com/greenbone/openvas-scanner/tree/main/rust/openvasd
   Main PID: 949 (openvasd)
      Tasks: 13 (limit: 19007)
     Memory: 261.7M
        CPU: 1.370s
     CGroup: /system.slice/openvasd.service
             └─949 /usr/local/bin/openvasd --mode service_notus --products /var/lib/notus/products --advisories /var/lib/notus/advisories --listening 127.0.0.1:3000

Jul 25 04:25:39 greenbone systemd[1]: Starting OpenVASD...
Jul 25 04:25:39 greenbone systemd[1]: Started OpenVASD.
Jul 25 04:25:41 greenbone openvasd[949]: 2024-07-25T04:25:41.025387Z  WARN openvasd: OSPD socket /var/run/ospd/ospd.sock does not exist. Some commands will not work until the socket is crea>
Jul 25 04:25:41 greenbone openvasd[949]: 2024-07-25T04:25:41.026604Z  INFO openvasd: configuring storage devices mode=ServiceNotus storage_type=InMemory
Jul 25 04:25:41 greenbone openvasd[949]: 2024-07-25T04:25:41.026662Z  INFO openvasd: using in memory store. No sensitive data will be stored on disk.
Jul 25 04:25:41 greenbone openvasd[949]: 2024-07-25T04:25:41.083992Z  INFO openvasd::controller: running in config.mode=ServiceNotus
Jul 25 04:25:41 greenbone openvasd[949]: 2024-07-25T04:25:41.084679Z  INFO openvasd::controller: listening on http://127.0.0.1:3000

This is a duplicate of this topic, but related to build from source, not container.

2

Updating openvasd to the latest version, 23.8.0, didn’t fix this.

3

I was able to resolve the OSPD socket warning by adding

--ospd-socket /run/ospd/ospd-openvas.sock

to the ExecStart string in openvasd.service.

2 Likes