So I checked that the redis.sock file exists in the /tmp directory and
openVAS expects it at the same place.

Checking presence of redis ...
        OK: redis-server is present in version v=3.0.7.

Checking if redis-server is configured properly to run with openVAS ...
        OK: scanner (kb_location setting) is configured properly using the
redis-server socket: /tmp/redis.sock
Checking if redis-server is running ...
        OK: redis-server is running and listening on socket:
/tmp/redis.sock.
        OK: redis-server configuration is OK and redis-server is running.

 The redis.conf file creates socket in the same place:
unixsocket /tmp/redis.sock
unixsocketperm 700

Do I have to recompile or just restart services for changing this path and
conf file?

Thanks!


On Fri, Jun 23, 2017 at 5:58 PM, Thijs Stuurman <
[email protected]> wrote:

> First check where your redis.sock actually is located; if it exists at
> all.. look at your redis configuration file for the path.
>
> Then look at where openvas expects it to be.. it should show in the
> logging.
>
>
>
> I run openvas9 on Ubuntu 16.04 and openvas somehow expects it to be in
> /tmp/ but for some (probably good) reason redis refuses or cannot make it
> in /tmp.
>
> Haven’t bothered to figure out why, set it back to default
> /var/run/redis/redis.sock and made a symlink in /tmp to it because I had to
> get it working ;p
>
> (ln -s /var/run/redis/redis.sock /tmp/redis.sock) .. I should recompile
> openvas to fix the path I guess.. someday.. after my vacation ;p
>
>
>
> Thijs Stuurman
>
> Security Operations Center | KPN Internedservices
>
> [email protected] | [email protected]
>
> T: +31(0)299476185 | M: +31(0)624366778
>
> PGP Key-ID: 0x16ADC048 (https://pgp.surfnet.nl/)
>
> Fingerprint: 2EDB 9B42 D6E8 7D4B 6E02 8BE5 6D46 8007 16AD C048
>
>
>
> W: https://www.internedservices.nl | L: http://nl.linkedin.com/in/
> thijsstuurman
>
>
>
> *Van:* Openvas-discuss [mailto:[email protected]]
> *Namens *Harsh kapadia
> *Verzonden:* vrijdag 23 juni 2017 14:25
> *Aan:* Eero Volotinen <[email protected]>
> *CC:* [email protected]
> *Onderwerp:* Re: [Openvas-discuss] Scans not executing
>
>
>
> Thanks for responding!
>
>
>
> Should I move the socket file from /tmp to /run/redis and also modify the
> kb_location path accordingly?
>
>
>
> I'm new to openvas and not really sure what needs to be done.
>
>
>
> Harsh
>
>
>
> On Fri, Jun 23, 2017 at 5:47 PM, Eero Volotinen <[email protected]>
> wrote:
>
> sounds like connection to redis it not working.
>
>
>
> Eero
>
>
>
> 23.6.2017 3.15 ip. "Harsh kapadia" <[email protected]> kirjoitti:
>
> Hi,
>
>
>
> Please see the attached output from openvas-check-setup.log file.
> Everything seems OK but still the scans do not execute:
>
>
>
> I do still see the below errors in openvassd.dump file.
>
> (openvassd:23236): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> (openvassd:23236): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> (openvassd:23236): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> (openvassd:23236): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> (openvassd:22085): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> (openvassd:22085): lib  kb_redis-CRITICAL **: get_redis_ctx: redis
> connection error: No such file or directory
>
>
>
> Kindly suggest. SELinux is turned off so it shouldn't be a problem to use
> the socket for redis from /tmp directory.
>
>
>
> Thanks!
>
>
>
> _______________________________________________
> Openvas-discuss mailing list
> [email protected]
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
>
>
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to