sorry. typing error:

echo "unixsocket /var/lib/redis/redis.sock" >> etc/redis.conf and then rest
of commands.

Eero

2015-09-18 17:04 GMT+03:00 Eero Volotinen <[email protected]>:

> Hi,
>
> I usually don't provide step by step instructions.. but
>
> echo "unixsocket /tmp/redis.sock" >> /etc/redis.conf means that you need
> to add one line to /etc/redis.conf saying 'unixsocket /tmp/redis.sock'
>
> systemctl works only on root account. ask help from your local linux
> support, in case of problems.
>
> Eero
>
>
>
> 2015-09-18 16:56 GMT+03:00 Randy Dover <[email protected]>:
>
>> Eero,
>>
>> I’m a little confused over your reply.
>>
>> (Please forgive this Linux newbie!)
>>
>> Echo? In dos, that just means to show the line…
>>
>> Do I need to edit the redis.conf file?
>>
>>
>>
>> When I type the system enable command I get an “Access denied”, I am
>> signed on as admin (*Should* be root level) after getting that message, I
>> typed “su”, which should have forced it into privilege, even though it
>> should have been already.
>>
>>
>>
>> Randy Dover
>>
>>
>>
>> *From:* [email protected] [mailto:[email protected]] *On
>> Behalf Of *Eero Volotinen
>> *Sent:* Friday, September 18, 2015 9:44 AM
>> *To:* Randy Dover <[email protected]>
>> *Cc:* openvas-discuss <[email protected]>
>> *Subject:* Re: [Openvas-discuss] OpenVas install on CentOS 7 -
>> redis-server
>>
>>
>>
>> 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
>>
>>
>> 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

Reply via email to