Thank you once again.
The redis-server status is as follows, which did not change after restarting
the service.
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; disabled; vendor
preset: disabled)
Active: failed (Result: signal) since Sun 2017-11-26 12:23:54 EET; 1min 58s
ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 2303 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf
(code=exited, status=0/SUCCESS)
Main PID: 2304 (code=killed, signal=SEGV)
Nov 26 12:23:54 kali systemd[1]: redis-server.service: Service hold-off time
over, scheduling restart.
Nov 26 12:23:54 kali systemd[1]: redis-server.service: Scheduled restart job,
restart counter is at 5.
Nov 26 12:23:54 kali systemd[1]: Stopped Advanced key-value store.
Nov 26 12:23:54 kali systemd[1]: redis-server.service: Start request repeated
too quickly.
Nov 26 12:23:54 kali systemd[1]: redis-server.service: Failed with result
'signal'.
Nov 26 12:23:54 kali systemd[1]: Failed to start Advanced key-value store.
Panagiotis Leontios
Business Engineer | Project Manager | Consultant
BEng, DIC, MSc, MBA, IRCA Lead Auditor
----------------------------------------------------------------------------------------
Am 26.11.2017 um 08:59 schrieb Παναγιώτης Λεόντιος:
> Thanks for considering.
>
> 1. Yes, I think it does run, because when I run it separately it seems
> working OK (so it shows from the command line)
you think?
frankly is that a joke?
> 2. The problem happens every time I try to start openvas services. How
> should I REstart redis anyway?
as every other service?
> 3. The problem seems to be that for some reason the redis is not
> listening on /var/run/redis/redis.sock, although in its config file
> the unixsocket is just that
you evenb don#t know how to look if it is running, how to restart it, how to
start it or how to ensure that it is started at boot which means you have a
real problem operating your operating system
[root@openvas:~]$ systemctl status redis ? redis.service - Redis persistent
key-value database
Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled; vendor
preset: disabled)
Drop-In: /etc/systemd/system/redis.service.d
??limit.conf
Active: active (running) since Thu 2017-11-23 11:06:01 CET; 2 days ago
Main PID: 395 (redis-server)
Tasks: 3 (limit: 512)
CGroup: /system.slice/redis.service
??395 /usr/bin/redis-server 127.0.0.1:0
> -----Original Message-----
> From: Openvas-discuss
> [mailto:[email protected]]
> On Behalf Of Reindl Harald
> Sent: Sunday, November 26, 2017 11:19 AM
> To: [email protected]
> Subject: Re: [Openvas-discuss] REDIS-SERVER SOCKET PROBLEM
>
> * and *does it run* or could it be crashed?
> * did you simply try to restart redis
> * did you raed your systemlogs (OOM killer and freinds maybe)
>
> http://www.catb.org/esr/faqs/smart-questions.html#beprecise
>
> Am 26.11.2017 um 07:14 schrieb Παναγιώτης Λεόντιος:
>> Just after updated the openvas database (NVDs, etc.) via its standard
>> method, and trying to run *openvas-start*, I got an error message and
>> services didn?t start.
>>
>> The *openvas-check-setup*, came up with the following error message:
>>
>> *ERROR*: redis-server is not running or not listening on socket:
>> /var/run/redis/redis.sock
>>
>> *FIX*: You should start the redis-server or configure it to listen on
>> socket: /var/run/redis/redis.sock
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
---
This email has been checked for viruses by AVG.
http://www.avg.com
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
