# Ospd-openvas.service failed

**URL:** <https://forum.greenbone.net/t/ospd-openvas-service-failed/15910>\
**Category:** Linux Distribution and External Repo Discussion\
**Created:** [October 7, 2023, 3:38am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910 "2023-10-07T03:38:59Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hameleon](https://forum.greenbone.net/letter_avatar/hameleon/32/6_449c533f586939b6e5f246632a46421f.png) [@Hameleon](https://forum.greenbone.net/u/Hameleon)\
**Post date:** [October 7, 2023, 3:38am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/1 "2023-10-07T03:38:59Z")

</div>

Has download Kali week ago, trying to install Openvas-GVM. Installation was ok, but check and start not - first was problem with Requirements Postgresql 16. I did lot of commands and finally have postgre16 with main cluster v16. Now is probleme with redis: Job for gvmd.service failed because a timeout was exceeded.  
See “systemctl status gvmd.service” and “journalctl -xeu gvmd.service” for details.  
Job for ospd-openvas.service failed because the control process exited with error code.  
See “systemctl status ospd-openvas.service” and “journalctl -xeu ospd-openvas.service” for details.

┌──(root㉿kali)-[~]  
└─# journalctl -xeu ospd-openvas.service  
Oct 06 23:16:43 kali ospd-openvas[257596]: File "/usr/lib/python3/dist-pack\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: self.ctx = OpenvasDB.create\_co\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: ^^^^^^^^^^^^^^^^^^^\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: File "/usr/lib/python3/dist-pack\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: ctx = redis.Redis.from\_url(  
Oct 06 23:16:43 kali ospd-openvas[257596]: ^^^^^^^^^^^^^^^^^^^^^  
Oct 06 23:16:43 kali ospd-openvas[257596]: File "/usr/lib/python3/dist-pack\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: connection\_pool = ConnectionPo\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: ^^^^^^^^^^^^\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: File "/usr/lib/python3/dist-pack\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: url\_options = parse\_url(url)  
Oct 06 23:16:43 kali ospd-openvas[257596]: ^^^^^^^^^^^^^^  
Oct 06 23:16:43 kali ospd-openvas[257596]: File "/usr/lib/python3/dist-pack\>  
Oct 06 23:16:43 kali ospd-openvas[257596]: raise ValueError(  
Oct 06 23:16:43 kali ospd-openvas[257596]: ValueError: Redis URL must specify\>  
Oct 06 23:16:43 kali systemd[1]: ospd-openvas.service: Control process exited\>

---

<div class="post-metadata">

**Author:** ![m4lf0](https://forum.greenbone.net/letter_avatar/m4lf0/32/6_449c533f586939b6e5f246632a46421f.png) [@m4lf0](https://forum.greenbone.net/u/m4lf0)\
**Post date:** [October 7, 2023, 11:05am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/2 "2023-10-07T11:05:52Z")

</div>

try

```auto
sudo systemctl start redis-server

```

---

<div class="post-metadata">

**Author:** ![m4lf0](https://forum.greenbone.net/letter_avatar/m4lf0/32/6_449c533f586939b6e5f246632a46421f.png) [@m4lf0](https://forum.greenbone.net/u/m4lf0)\
**Post date:** [October 7, 2023, 11:07am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/3 "2023-10-07T11:07:24Z")

</div>

Once i had problem with redis, this worked for me

```auto
1. apt-get purge --auto-remove redis*

 2. apt-get install openvas

 3. apt-get install redis

 4. In these files /etc/redis/redis.conf && /etc/redis/redis-openvas.conf, you change et uncheck these parameters : 

    bind 127.0.0.0.1 ::1 => bind 0.0.0.0

    unixsocket run/redis.sock (OR) unixsocket /var/run/redis-openvas/redis-server.sock => unixsocket /var/run/redis/redis.sock

    unixsocketperm 700 => unixsocketperm 770

 5. In this file /etc/openvas/openvas.conf, you change this parameter :
    
    db_address = /var/run/redis-openvas/redis-server.sock => db_address = /var/run/redis/redis.sock

 6. systemctl daemon-reload

 7. systemctl restart redis-server.service

 8. gvm-setup

 9. gvm-check-setup

```

---

<div class="post-metadata">

**Author:** ![rippledj](https://forum.greenbone.net/user_avatar/forum.greenbone.net/rippledj/32/2006_2.png) [@rippledj](https://forum.greenbone.net/u/rippledj)\
**Post date:** [October 7, 2023, 3:37pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/4 "2023-10-07T15:37:01Z")

</div>

For the future, it may be easier to identify the error or get help if you print the whole error line untruncated:

To make the journalctl command print the whole lines instead of truncating them based on screen size, you can use the -o cat option. This option will output the log entries as untruncated lines.

```auto
journalctl -xeu ospd-openvas.service -o cat

```

---

<div class="post-metadata">

**Author:** ![Lukas](https://forum.greenbone.net/user_avatar/forum.greenbone.net/lukas/32/17_2.png) [@Lukas](https://forum.greenbone.net/u/Lukas)\
**Post date:** [October 8, 2023, 5:43pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/5 "2023-10-08T17:43:21Z")

</div>

> [@m4lf0](#):
>
> ` bind 127.0.0.0.1 ::1 => bind 0.0.0.0`

You really should not do that, this will expose _ALL_ redis data without any authentication to the network via all IPv4 interfaces.

---

<div class="post-metadata">

**Author:** ![libellux](https://forum.greenbone.net/user_avatar/forum.greenbone.net/libellux/32/1424_2.png) [@libellux](https://forum.greenbone.net/u/libellux)\
**Post date:** [October 8, 2023, 6:07pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/6 "2023-10-08T18:07:08Z")

</div>

@Hameleon can you double check and make sure that user Redis is in the GVM group.

---

<div class="post-metadata">

**Author:** ![bwittm](https://forum.greenbone.net/letter_avatar/bwittm/32/6_449c533f586939b6e5f246632a46421f.png) [@bwittm](https://forum.greenbone.net/u/bwittm)\
**Post date:** [October 12, 2023, 4:09pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/7 "2023-10-12T16:09:35Z")

</div>

I believe you have that backwards:  
user gvm must be a member of group redis.  
sudo usermod -aG redis gvm

---

<div class="post-metadata">

**Author:** ![libellux](https://forum.greenbone.net/user_avatar/forum.greenbone.net/libellux/32/1424_2.png) [@libellux](https://forum.greenbone.net/u/libellux)\
**Post date:** [October 12, 2023, 4:10pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/8 "2023-10-12T16:10:17Z")

</div>

should be group \_gvm

---

<div class="post-metadata">

**Author:** ![libellux](https://forum.greenbone.net/user_avatar/forum.greenbone.net/libellux/32/1424_2.png) [@libellux](https://forum.greenbone.net/u/libellux)\
**Post date:** [October 12, 2023, 4:12pm UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/9 "2023-10-12T16:12:29Z")

</div>

@Hameleon I’ve added support on how-to build GVM from source on Kali Linux 2023.3. Feel free to try it out. I’ve had no issues so far and done a scan test.

> **[Libellux](https://libellux.com/openvas/)**
>
> Libellux: Up & Running provides documentation on how-to install open-source software from source. The focus is Zero Trust Network to enhance the security for existing applications or install tools to detect and prevent threats.

---

<div class="post-metadata">

**Author:** ![sehranrasooljan](https://forum.greenbone.net/letter_avatar/sehranrasooljan/32/6_449c533f586939b6e5f246632a46421f.png) [@sehranrasooljan](https://forum.greenbone.net/u/sehranrasooljan)\
**Post date:** [December 13, 2024, 11:51am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/10 "2024-12-13T11:51:39Z")

</div>

I was facing the same issue and it have been resolved using this command:

sudo greenbone-feed-sync --type GVMD\_DATA  
sudo greenbone-feed-sync --type SCAP  
sudo greenbone-feed-sync --type CERT

---

<div class="post-metadata">

**Author:** ![system](https://forum.greenbone.net/uploads/default/original/2X/4/4660e797edfaea797a8c9965246072ea26732804.png) [@system](https://forum.greenbone.net/u/system)\
**Post date:** [April 7, 2025, 10:28am UTC](https://forum.greenbone.net/t/ospd-openvas-service-failed/15910/11 "2025-04-07T10:28:28Z")

</div>

Closed on April 7, 2025, 10:28am UTC


