That sounds like syntax error in configuration file. -- Eero
2015-12-05 18:51 GMT+02:00 Elias Pereira <[email protected]>: > I tried these commands. > > *root@elias-pc:~# systemctl enable redis-server.service* >> Synchronizing state for redis-server.service with sysvinit using >> update-rc.d... >> Executing /usr/sbin/update-rc.d redis-server defaults >> Executing /usr/sbin/update-rc.d redis-server enable > > > *root@elias-pc:~# systemctl restart redis-server.service* >> Job for redis-server.service failed. See "systemctl status >> redis-server.service" and "journalctl -xe" for details. > > > *root@elias-pc:~# systemctl status redis-server.service* >> ● redis-server.service - Advanced key-value store >> Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; >> vendor preset: enabled) >> Active: failed (Result: start-limit) since Sáb 2015-12-05 14:45:38 >> BRST; 1min 41s ago >> Process: 12030 ExecStop=/usr/bin/redis-cli shutdown (code=exited, >> status=1/FAILURE) >> Process: 12027 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf >> (code=exited, status=0/SUCCESS) >> Main PID: 12028 (code=exited, status=1/FAILURE) >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service: control >> process exited, code=exited status=1 >> Dez 05 14:45:38 elias-pc systemd[1]: Unit redis-server.service entered >> failed state. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service failed. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service holdoff time >> over, scheduling restart. >> Dez 05 14:45:38 elias-pc systemd[1]: start request repeated too quickly >> for redis-server.service >> Dez 05 14:45:38 elias-pc systemd[1]: Failed to start Advanced key-value >> store. >> Dez 05 14:45:38 elias-pc systemd[1]: Unit redis-server.service entered >> failed state. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service failed. > > > *root@elias-pc:~# journalctl -xe* >> -- A unidade redis-server.service está sendo iniciada. >> Dez 05 14:45:38 elias-pc systemd[1]: Started Advanced key-value store. >> -- Subject: Unidade redis-server.service concluiu a inicialização >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- A unidade redis-server.service concluiu a inicialização. >> -- >> -- The start-up result is done. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service: main process >> exited, code=exited, status=1/FAILURE >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service: control >> process exited, code=exited status=1 >> Dez 05 14:45:38 elias-pc systemd[1]: Unit redis-server.service entered >> failed state. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service failed. >> Dez 05 14:45:38 elias-pc redis-cli[12030]: Could not connect to Redis at >> 127.0.0.1:6379: Connection refused >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service holdoff time >> over, scheduling restart. >> Dez 05 14:45:38 elias-pc systemd[1]: start request repeated too quickly >> for redis-server.service >> Dez 05 14:45:38 elias-pc systemd[1]: Failed to start Advanced key-value >> store. >> -- Subject: A unidade redis-server.service falhou >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- A unidade redis-server.service falhou. >> -- >> -- O resultado é failed. >> Dez 05 14:45:38 elias-pc systemd[1]: Unit redis-server.service entered >> failed state. >> Dez 05 14:45:38 elias-pc systemd[1]: redis-server.service failed. > > > > On Sat, Dec 5, 2015 at 6:25 AM, Eero Volotinen <[email protected]> > wrote: > >> You need to restart/start redis using tools provided by ubuntu. I think >> it's like systemctl restart service-name.service and systemctl enable >> service-name.service >> >> >> -- >> Eero >> >> 2015-12-04 23:11 GMT+02:00 Elias Pereira <[email protected]>: >> >>> Hi Chris, >>> >>> In /etc/redis/redis.conf file have a configuration. >>> >>> #Added by openvas-scanner post installation >>>> unixsocket /var/run/redis/redis.sock >>>> #Added by openvas-scanner post installation >>>> unixsocketperm 770 >>> >>> >>> I run in root mode: root@user# redis-server, and it's run in standalone >>> mode. >>> >>> But in other terminal I run openvas-check-setup and the error still >>> occurs. >>> >>> On Fri, Dec 4, 2015 at 6:44 PM, Chris <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> have you checked what the message is suggesting: >>>> >>>> >> 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 >>>> >>> >>> >>> >>> -- >>> Elias Pereira >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> [email protected] >>> >>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >>> >> >> > > > -- > Elias Pereira >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
