Bug#889065: marked as done (openvas-setup lib kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock')

Debian Bug Tracking System owner at bugs.debian.org
Tue Jul 10 15:21:06 BST 2018


Your message dated Tue, 10 Jul 2018 16:16:39 +0200
with message-id <20180710141639.GA18227 at home.ouaza.com>
and subject line Re: Bug#889065: openvas-setup lib  kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock'
has caused the Debian Bug report #889065,
regarding openvas-setup lib  kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
889065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889065
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: ilovesusu <0x73757375 at gmail.com>
Subject: openvas-setup lib  kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock'
Date: Fri, 02 Feb 2018 00:56:36 +0800
Size: 3223
URL: <http://alioth-lists.debian.net/pipermail/pkg-security-team/attachments/20180710/aa9e3c7d/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Raphael Hertzog <hertzog at debian.org>
Subject: Re: Bug#889065: openvas-setup lib  kb_redis-CRITICAL **: redis_new: cannot access redis at '/tmp/redis.sock'
Date: Tue, 10 Jul 2018 16:16:39 +0200
Size: 2539
URL: <http://alioth-lists.debian.net/pipermail/pkg-security-team/attachments/20180710/aa9e3c7d/attachment-0001.mht>


More information about the Pkg-security-team mailing list