Re: [Openvas-discuss] Openvas scanner won't start

2018-02-26 Thread Christian Fischer
Hi,

just a clarification on the following:

On 22.02.2018 19:38, Yohan Pipereau wrote:
> If you drop everything, on redis, you will need to retrieve the vulnerability
> and it should be done by openvas automatically causing the first scan to be a
> bit longer.

there is currently no persistent data saved into redis across e.g.
different scans against the same host. As long as no scan is running you
can flush the redis database without any negative effects / drawbacks or
longer scan times on the next scan run.

Regards,

-- 

Christian Fischer | PGP Key: 0x54F3CE5B76C597AD
Greenbone Networks GmbH | http://greenbone.net
Neumarkt 12, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460
Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2018-02-22 Thread Yohan Pipereau
Hi there,

I am not really aware of the news on OpenVAS since October 2017 when I
ended working on it.
I hoped it would be patched in the newest version.

Le 22/02/2018 à 01:41, Scott Knauss a écrit :

> Second, a questions: any reason not to flush redis once a week? 

Actually, it depends on how many times you SIGKILL OpenVAS every week ;).

As far as I remember, the redis database on the version I was working on
(OpenVAS Scanner 5.1.1 with openvas-libraries
9.0.1) contained the following informations:
  - path to Vulnerability files (NVT)  [if I remember well]
  - scan data during scan run.
  - scan data if scan SIGKILL

Thus it depends on how you plan to flush your database. If you drop
everything, on redis, you will need to retrieve the vulnerability and it
should be done by openvas automatically causing the first scan to be a
bit longer.

If you have some redis knowledge do not hesitate to dig into the
database, this could have changed and I'm not sure about some infos.

Good Luck :),

Sincerely,

Yohan Pipereau



signature.asc
Description: OpenPGP digital signature
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2018-02-21 Thread Scott Knauss
Ran into this problem today and found this thread.

First wanted to thank you. I was actually in the process of rebuilding on a
new VM when I came across this thread. (This is the second time I've hit
this issue, the last time mid summer 2017 before you posted this thread.)

Second, a questions: any reason not to flush redis once a week?

Thanks,
Scott



Scott Knauss
sc...@immauss.com

*ITS*
*Immauss Technology Solutions*
*It's about solutions*
*https://www.immauss.com <https://www.immauss.com/>*



On Fri, Aug 25, 2017 at 5:56 AM, Ebert, Christian 
wrote:

> Hi,
>
>
>
> I know they read the list. Sometimes it takes some time, but they read it.
>
>
>
> Best regards
>
>
>
> Christian Ebert
>
> Chief Security Analyst, CISM, T.I.S.P.
>
> Head of Penetration Testing
>
>
>
> QSC AG
>
> Mathias-Brüggen-Straße 55
>
> 50829 Köln
>
>
>
> T  +49 221 669-8950 <+49%20221%206698950>
>
> F  +49 221 669-85950 <+49%20221%2066985950>
>
> M  +49 163 6698950 <+49%20163%206698950>
>
> christian.eb...@qsc.de
>
> http://www.qsc.de
>
>
>
> Besuchen Sie unsere Blogs:
> Corporate Blog unter *http://blog.qsc.de <http://blog.qsc.de/>*
> Themen-Blog zur Digitalisierung unter *http://digitales-wirtschaftswunder.de
> <http://digitales-wirtschaftswunder.de/>*
>
>
>
> Bitte finden Sie hier die handelsrechtlichen Pflichtangaben:
>
> http://www.qsc.de/pflichtangaben
>
>
>
> *Von:* Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org]
> *Im Auftrag von *Yohan Pipereau
> *Gesendet:* Freitag, 25. August 2017 10:33
> *An:* openvas-discuss@wald.intevation.org
> *Betreff:* Re: [Openvas-discuss] Openvas scanner won't start
>
>
>
> No problem :).
>
> This is a bug I reported last week and it happens in a very particular
> situation.
>
> Here are the details:
>
> http://lists.wald.intevation.org/pipermail/openvas-discuss/
> 2017-August/011380.html
>
> By the way, does anyone know how I could report this bug to openVAS
> developpers?
> I am not sure they read this ML.
>
> Yohan
>
> On 25/08/2017 01:47, Tyler Doman wrote:
>
> That fixed it! Thanks a ton!
>
>
>
>
>
>
>
>
> ___
>
> Openvas-discuss mailing list
>
> Openvas-discuss@wald.intevation.org
>
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
>
>
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2017-08-25 Thread Ebert, Christian
Hi,

I know they read the list. Sometimes it takes some time, but they read it.

Best regards

Christian Ebert
Chief Security Analyst, CISM, T.I.S.P.
Head of Penetration Testing

QSC AG
Mathias-Brüggen-Straße 55
50829 Köln

T  +49 221 669-8950
F  +49 221 669-85950
M  +49 163 6698950
christian.eb...@qsc.de<mailto:christian.eb...@qsc.de>
http://www.qsc.de

Besuchen Sie unsere Blogs:
Corporate Blog unter http://blog.qsc.de<http://blog.qsc.de/>
Themen-Blog zur Digitalisierung unter 
http://digitales-wirtschaftswunder.de<http://digitales-wirtschaftswunder.de/>

Bitte finden Sie hier die handelsrechtlichen Pflichtangaben:
http://www.qsc.de/pflichtangaben

Von: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] Im 
Auftrag von Yohan Pipereau
Gesendet: Freitag, 25. August 2017 10:33
An: openvas-discuss@wald.intevation.org
Betreff: Re: [Openvas-discuss] Openvas scanner won't start


No problem :).

This is a bug I reported last week and it happens in a very particular 
situation.

Here are the details:

http://lists.wald.intevation.org/pipermail/openvas-discuss/2017-August/011380.html
By the way, does anyone know how I could report this bug to openVAS developpers?
I am not sure they read this ML.

Yohan
On 25/08/2017 01:47, Tyler Doman wrote:
That fixed it! Thanks a ton!






___

Openvas-discuss mailing list

Openvas-discuss@wald.intevation.org<mailto:Openvas-discuss@wald.intevation.org>

https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2017-08-25 Thread Yohan Pipereau
No problem :).

This is a bug I reported last week and it happens in a very particular
situation.

Here are the details:

http://lists.wald.intevation.org/pipermail/openvas-discuss/2017-August/011380.html

By the way, does anyone know how I could report this bug to openVAS
developpers?
I am not sure they read this ML.

Yohan

On 25/08/2017 01:47, Tyler Doman wrote:
>
> That fixed it! Thanks a ton!
>
>  
>
>  
>
>
>
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss



signature.asc
Description: OpenPGP digital signature
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2017-08-24 Thread Tyler Doman
That fixed it! Thanks a ton!


___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] Openvas scanner won't start

2017-08-24 Thread yohan.pipereau
Hi ,
I m not sure but i faced a similar problem.

You can try to connect to the redis socket and run:redis-cli -s  
flushall
The  is the unixsocket path you can find in /etc/redis.conf.It should 
return OK.
Then restart the openvas scanner with:systemctl restart openvas-scanner.
It will retrieve all the nvt infos and put them back in redis.You can check 
that by running redis-cli -s  info keyspaces
You should have one database with lot of data.
Then, try to launch a new scan.
 Message d'origine De : Tyler Doman 
 Date : 24/08/2017  23:38  (GMT+01:00) À : 
openvas-discuss@wald.intevation.org Objet : [Openvas-discuss] Openvas scanner 
won't start 


Openvas was scanning fine for several days then suddenly stopped. The greenbone 
gui was running fine but wouldn't let me initiate new scans since it said the 
service was down.
 I ran openvas-check-setup and it said everything was ok except the scanner 
service was down. So I ran /etc/init.d/openvas-scanner start and it returned, 
"openvas-scanner.service failed because a timeout was exceeded. See 'systemctl  
status openvas-scanner.service'
 and 'journalctl  -xe' for details."
 
When I run 'systemctl  status openvas-scanner.service', it says, 'load Failed 
to start Open Vulnerability Assessment System Scanner Daemon.'
 
I tried purging openvas, rebooting, reinstalling, running openvas-setup but it 
hangs up and freezes at the end of the process. Are there any other options 
besides wiping out
 Kali and restoring a new Kali image? I really want to avoid doing that if 
possible.
 

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss