ERROR: (ospd_openvas.lock) Could not create parent dir /var/run/gvm for lock file. [Errno 13] Permission denied: '/var/run/gvm'

Linux Distribution and External Repo Discussion
1

I experienced scanning crashing after updating gvmd 21.4.3 to gvmd 21.4.5 on Rocky Linux release 8.6. Found in /var/log/gvm/ospd-scanner.log this error looping:

ERROR: (ospd_openvas.lock) Could not create parent dir /var/run/gvm for lock file. [Errno 13] Permission denied: ‘/var/run/gvm’

The error was caused by a wrong parameter in /usr/lib/systemd/system/ospd-openvas.service

So what I did to solve this was.

ln -s /usr/lib/systemd/system/ospd-openvas.service /etc/systemd/system/ospd-openvas.service
vi /etc/systemd/system/ospd-openvas.service

change:
ExecStart=/opt/atomicorp/bin/ospd-openvas --pid-file /var/run/ospd/ospd-openvas.pid --unix-socket=/var/run/ospd/ospd-openvas.sock --log-file /var/log/gvm/ospd-scanner.log --lock-file-dir /var/run/gvm/

to:
ExecStart=/opt/atomicorp/bin/ospd-openvas --pid-file /var/run/ospd/ospd-openvas.pid --unix-socket=/var/run/ospd/ospd-openvas.sock --log-file /var/log/gvm/ospd-scanner.log --lock-file-dir /var/run/gvmd/

save the file then run:
systemctl daemon-reload
systemctl restart ospd-openvas
systemctl restart gvmd
After this, scanning do run without errors.

2

Hi
I was having the same issues , changed the lock-file-dir to /var/run/gvmd/ en i updated my server today en now the service doesnt start
with journalctl -u ospd-openvas
i get this :

image
image1021×139 6.71 KB

in the gvmd logs i see this :

md manage:WARNING:2022-07-18 13h01.53 UTC:57566: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock
md manage:WARNING:2022-07-18 13h02.03 UTC:57593: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock
md manage:WARNING:2022-07-18 13h02.13 UTC:57598: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock
md manage:WARNING:2022-07-18 13h02.23 UTC:57625: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock
md manage:WARNING:2022-07-18 13h02.33 UTC:57628: osp_scanner_feed_version: failed to connect to /var/run/ospd/ospd-openvas.sock

en the folder /var/run/ospd/ is empty.

ospd-openvas version 21.4.4
openvas-scanner 21.4.4

gvm.noarch 21.4.0-18459.el8.art @atomic
gvm-libs.x86_64 21.4.4-26413.el8.art @atomic
gvmd.x86_64 21.4.5-26414.el8.art @atomic

It looks like there is a missing module lxml.etree
Does anyone have any idea how I can solve this?

Thanks

Yilian

3

Similar to Ospd-openvas.service doesnt start - Linux Distribution and External Repo Discussion - Greenbone Community Forum this is probably a packaging issue in the new releases:

4

A related discussion seems to be ongoing here:

https://github.com/Atomicorp/gvm/issues/61