Hi, I am also facing same issue. Initially the gsad.service and ospd-openvas.service are disabled and inactive, I activated and enabled them.
But still facing issue “gvmd.service: Can’t open PID file /run/gvmd/gvmd.pid (yet?) after start: Operation not permitted”
Please help me in resolving this.
Hi and welcome to our community!
I’ve moved your message to a new topic. It is best to open a new one in such cases.
Sadly I was never able to reproduce this issue therefore I still don’t understand what’s going on here. Systemd should create the
/run/gvmd/ directory with the correct permissions as stated in the service file. Thus please check the
gvmd.service file first. It should contain the following lines
Second you should check if
/run/gvmd has the correct permissions via
ls -l /run/gvmd. The owner should be the
gvm user and not
root for example.
I am still not sure if this error originates from gvmd or systemd.
check your unit
It should look like this:
Description=Greenbone Vulnerability Manager daemon (gvmd)
After=network.target networking.service postgresql.service ospd-openvas.service
ExecStart=/usr/local/sbin/gvmd --osp-vt-update=/run/ospd/ospd-openvas.sock --listen-group=gvm
The second check has to be the already running process that was not killed from previous tries.
ps -elf | grep gvm
Sorry, no this is wrong. It needs to be
This could maybe caused by the same issue as Change service start up type from forking to exec by rfc6919 · Pull Request #84 · greenbone/gsad · GitHub but not for gvmd instead. Changing
exec and adding a
ExecStart may improve the situation.