Hi, There is bug in atomic corp rpms, so you need to start, enable and configure redis.service correctly.
try following: echo "unixsocket /tmp/redis.sock" >> /etc/redis.conf systemctl enable redis.service systemctl restart redis.service Then it should work fine .. -- Eero 2015-09-18 16:03 GMT+03:00 Randy Dover <[email protected]>: > I have just installed (or actually should probably say I am ATTEMPTING TO > INSTALL) OpenVAS 8 on CentOS7. > > > > I did the install and when I run the openvas-check-setup I am getting: > > ERROR: redis-server is not running or not listening on socket: > /var/lib/redis/redis.sock > > FIX: You should start the redis-server or configure it to listen on > socket: /var/lib/redis/redis.sock > > > > Before going further – I am not good at Linux, so will please give me > exact commands and paths, etc. > > > > I have searched for the fix before posting this. > > > > I found different answers: > > One answer: > > Edit /etc/redis.conf and add lines: > > Unixsocket /var/lib/redis/redis.sock > > Port > 0 > > > Timeout 0 > > > > Another answer: > > port 0 # prevent redis from listening on a TCP socket > > unixsocket /tmp/redis.sock > > unixsocketperm 700 > > timeout 0 > > > > Another answer: > > unixsocket /tmp/redis.sock > unixsocketperm 755 > > > > I have tried a couple of different iterations of the above suggestions, > and keep getting the error. > > My /etc/redis.conf currently has these lines at the very bottom: > > Aof-rewrite-incremental -fsync yes (this line was in there before I edited > it) > > Unixsocket /var/lib/redis/redis.sock > > Port 0 #prevent redis from listening on a TCP socket > > Unixsocketperm 700 > > Timeout 0 > > > > Also, it could be that the redis-server is not started after I made those > changes. I don’t know how to start it (I searched that also, but didn’t > find anything. Remember, I am a very novice Linux user, so please tell me > EXACTLY how to start it in CentOS.) > > > > Randy Dover > > > This email is intended for its designated recipients. The information, and > attachments, contained in this email may be considered private and/or > confidential. If the transmission is received in error, delete messages(s) > from your system and notify the sender. You may not, directly or > indirectly, use, disclose or distribute any part of this email. > > _______________________________________________ > 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
