openvassd creates Unix socket /tmp/redis.sock, whereas other openvas services expect /var/run/openvassd.sock

Bug #1759115 reported by Konstantin Boyandin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openvas (Debian)
Fix Released
Unknown
openvas-scanner (Debian)
Fix Released
Unknown
openvas-scanner (Ubuntu)
New
Undecided
Unassigned

Bug Description

OS: Ubuntu 17.10 64-bit, standard repositories used
openvas packages installed:

openvas 9.0.0
openvas-cli 1.4.5-1
openvas-manager 7.0.2-1
openvas-manager-common 7.0.2-1
openvas-scanner 5.1.1-2

When being run openvas-scanenr.servcie (openvassd) creates Unix sockeet as

/tmp/redis.sock

whereas other openavs servics/Web GUI expect the socket at

/var/run/openvassd.sock

Quick solution looks like this

sudo ln -s /tmp/redis.sock /var/run/openvassd.sock

but creating correct Unix socket could help much more. Also, ther's no documented setting that specifies Unix socket path.

1x6PY78 (1x6py78)
no longer affects: openvas-scanner (Debian)
Changed in openvas-scanner (Debian):
status: Unknown → New
Changed in openvas (Debian):
status: Unknown → New
Changed in openvas-scanner (Debian):
status: New → Fix Released
Changed in openvas (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.