View Issue Details

IDProjectCategoryView StatusLast Update
0002536Kali LinuxKali Package Bugpublic2015-08-17 14:31
Reportersteorra Assigned Torhertzog  
Status resolvedResolutionfixed 
Summary0002536: openvas not starting post 2.0 upgrade due to redis permission issue

Upon attempting to scan a target in openvas post upgrade to 2.0, scan does not initiate and displays the error under the reports section as "WARNING: Cannot connect to KB at '/var/lib/redis/redis.sock': Connection refused'" Please note that openvas was running successfully prior to the upgrade.

Verified redis server is running by doing a ps aux | grep redis-server. Upon checking redis' log, I'm not showing any errors but the following:

[816] 14 Aug 22:22:15.891 # Server started, Redis version 2.8.17
[816] 14 Aug 22:22:15.891 # WARNING overcommit_memory is set to 0! Background sa
ve may fail under low memory condition. To fix this issue add 'vm.overcommit_mem
ory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overc
ommit_memory=1' for this to take effect.
[816] 14 Aug 22:22:15.912 DB loaded from disk: 0.021 seconds
[816] 14 Aug 22:22:15.912
The server is now ready to accept connections on por
t 6379

I do not see any such redis.sock file under /var/lib/redis but rather the only file in the dir is dump.rdb.

I was able to reproduce this on a second instance running openvas post 2.0 upgrade.




2015-08-15 21:55

administrator   ~0003775

Can you attach your /etc/redis/redis.conf?

During the upgrade, you got a prompt about this file. I guess you installed the new file and did not keep the old modified file... is that correct?

The following commands are run in the openvas postinst script to configure redis properly:

    sed -i -e 's/^\(#.\)\?port.*$/port 0/' /etc/redis/redis.conf
    sed -i -e 's/^\(#.\)\?unixsocket \/.*$/unixsocket \/var\/lib\/redis\/redis.sock/' /etc/redis/redis.conf
    sed -i -e 's/^\(#.\)\?unixsocketperm.*$/unixsocketperm 700/' /etc/redis/redis.conf

Those changes have been lost on upgrade. Rerunning them should fix the issue for you I guess.



2015-08-17 14:31

manager   ~0003799

a new version of openvas 8.0+kali2 is now available. Launching the setup of openvas is fixing the redis.conf if needed

Issue History

Date Modified Username Field Change
2015-08-14 22:35 steorra New Issue
2015-08-15 21:55 rhertzog Note Added: 0003775
2015-08-15 21:55 rhertzog Assigned To => rhertzog
2015-08-15 21:55 rhertzog Status new => feedback
2015-08-17 14:31 sbrun Note Added: 0003799
2015-08-17 14:31 sbrun Status feedback => resolved
2015-08-17 14:31 sbrun Resolution open => fixed