View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002536||Kali Linux||Kali Package Bug||public||2015-08-14 22:35||2015-08-17 14:31|
|Summary||0002536: 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:
 14 Aug 22:22:15.891 # Server started, Redis version 2.8.17
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.
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:
Those changes have been lost on upgrade. Rerunning them should fix the issue for you I guess.
a new version of openvas 8.0+kali2 is now available. Launching the setup of openvas is fixing the redis.conf if needed
|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|