[prev in list] [next in list] [prev in thread] [next in thread]
List: openvas-discuss
Subject: Re: [Openvas-discuss] GSA crashes / OpenVAS hungs
From: tatooin <tatooin () free ! fr>
Date: 2017-02-03 16:38:33
Message-ID: 1486139913.2995.24.camel () wisukind
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have 4Gb memory so it should be ok I guess. As for Kali, I am capable
of installing every tools on my own (it's what I did in the past
actually), but the main benefit of Kali is that it centralize all
hacking tools in one plateform with some level of integration. So from a
management perspective, it's easier and you gain time. I am actually
more or less "testing" Kali since two years now, and I must confess that
I am considering building my own plateform based on a more robust distro
such as ubuntu or debian. But this is a highly time consuming task, and
in the meantime my duties must go on... not speaking about having the
feeling to reinvent the wheel, though.. :-)
Anyway thanks for your quick help. Currently my scans still go on.. :)
Best,
-----Original Message-----
From: Reindl Harald <h.reindl@thelounge.net>
To: openvas-discuss@wald.intevation.org
Subject: Re: [Openvas-discuss] GSA crashes / OpenVAS hungs
Date: Fri, 3 Feb 2017 17:06:21 +0100
Am 03.02.2017 um 16:57 schrieb tatooin:
> Hi Reindl,
>
> And thanks for your answer. Actually your questions made me find out
> that for some reason my swap partition wasn't mounted. So perhaps it
> explains the issues I'm facing in the end.
> I have mounted my swap back, restarted gsa/redis/openvas and resumed my
> scans.
you should assign at least 3 GB pyhisal RAM to your openvas machine,
otherwise there is a butcher called OOM killer which will sooner or
later slaughter your kittens
> Let's see if it fix the issue.
>
> As for Kali, I can unfortunately only agree with your statement. This
> distrib is just buggy as hell but unfortunately there is no particular
> alternative at the moment when you need a dedicated plateform for
> ethical hacking, which is my case...
don't get me wrong but OpenVAS doe snot only run on Kali and when you
want to become a hacker you should first become capable to install the
tools at your own, Kali is no magic, it's just a distribution
> -----Original Message-----
> *From*: Reindl Harald <h.reindl@thelounge.net
> <mailto:Reindl%20Harald%20%3ch.reindl@thelounge.net%3e>>
> *To*: openvas-discuss@wald.intevation.org
> <mailto:openvas-discuss@wald.intevation.org>
> *Subject*: Re: [Openvas-discuss] GSA crashes / OpenVAS hungs
> *Date*: Fri, 3 Feb 2017 16:17:53 +0100
>
>
> Am 03.02.2017 um 16:04 schrieb tatooin:
>> I can resume works for some times. But again, as soon as the load
>> becomes significant, gsa crashes and openvassd becomes unresponsive.
>>
>> It's not a load problem are purging/restarting redis is the key.
>>
>> Apart from commenting out all save options in redis.conf, is there
>> anything I am missing with redis to get it work properly ?
>>
>> I have the following error logs when gsa crashes in openvassd.messages:
>> /[Fri Feb 3 14:40:18 2017][7333] Client abruptly closed the communication/
>> /[Fri Feb 3 14:40:18 2017][7333] Test complete/
>> /[Fri Feb 3 14:40:18 2017][15974] Process 16844 (OID:
>> 1.3.6.1.4.1.25623.1.0.805139) seems to have died too early/
>> /[Fri Feb 3 14:40:18 2017][15968] Process 7400 (OID:
>> 1.3.6.1.4.1.25623.1.0.105211) seems to have died too early/
>> /[Fri Feb 3 14:40:18 2017][15970] Process 16513 (OID:
>> 1.3.6.1.4.1.25623.1.0.805927) seems to have died too early/
>> /[....continuing....]/
>> /openvassd: testing 10.169.74.94(sighand_segv+0x7c)[0x56176464e10c]/
>> /openvassd: testing 10.169.74.91(sighand_segv+0x7c)[0x56176464e10c]/
>> //lib/x86_64-linux-gnu/libc.so.6(+0x33040)[0x7f574a5a0040]/
>> //lib/x86_64-linux-gnu/libc.so.6(+0x33040)[0x7f574a5a0040]/
>
> these are segfaults
>
> how many RAM has the machine?
> what does dmesg say?
> what doe sthe global syslog say?
> how have you installed openvas?
> did you ask on a kali linux channel?
>
> each and every time kali linux is mentioned on this than becuse nothing
> works as expeted....
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
I have 4Gb memory so it should be ok I guess. As for Kali, I am capable of installing \
every tools on my own (it's what I did in the past actually), but the main benefit of \
Kali is that it centralize all hacking tools in one plateform with some level of \
integration. So from a management perspective, it's easier and you gain time. I am \
actually more or less "testing" Kali since two years now, and I must \
confess that I am considering building my own plateform based on a more robust distro \
such as ubuntu or debian. But this is a highly time consuming task, and in the \
meantime my duties must go on... not speaking about having the feeling to reinvent \
the wheel, though.. :-)<BR> <BR>
Anyway thanks for your quick help. Currently my scans still go on.. :)<BR>
<BR>
Best,<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
<B>From</B>: Reindl Harald <<A \
HREF="mailto:Reindl%20Harald%20%3ch.reindl@thelounge.net%3e">h.reindl@thelounge.net</A>><BR>
<B>To</B>: <A HREF="mailto:openvas-discuss@wald.intevation.org">openvas-discuss@wald.intevation.org</A><BR>
<B>Subject</B>: Re: [Openvas-discuss] GSA crashes / OpenVAS hungs<BR>
<B>Date</B>: Fri, 3 Feb 2017 17:06:21 +0100<BR>
<BR>
<PRE>
Am 03.02.2017 um 16:57 schrieb tatooin:
<FONT COLOR="#737373">> Hi Reindl,</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">> And thanks for your answer. Actually your questions made \
me find out</FONT> <FONT COLOR="#737373">> that for some reason my swap partition \
wasn't mounted. So perhaps it</FONT> <FONT COLOR="#737373">> explains the issues \
I'm facing in the end.</FONT> <FONT COLOR="#737373">> I have mounted my swap back, \
restarted gsa/redis/openvas and resumed my</FONT> <FONT COLOR="#737373">> \
scans.</FONT>
you should assign at least 3 GB pyhisal RAM to your openvas machine,
otherwise there is a butcher called OOM killer which will sooner or
later slaughter your kittens
<FONT COLOR="#737373">> Let's see if it fix the issue.</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">> As for Kali, I can unfortunately only agree with your \
statement. This</FONT> <FONT COLOR="#737373">> distrib is just buggy as hell but \
unfortunately there is no particular</FONT> <FONT COLOR="#737373">> alternative at \
the moment when you need a dedicated plateform for</FONT> <FONT COLOR="#737373">> \
ethical hacking, which is my case...</FONT>
don't get me wrong but OpenVAS doe snot only run on Kali and when you
want to become a hacker you should first become capable to install the
tools at your own, Kali is no magic, it's just a distribution
<FONT COLOR="#737373">> -----Original Message-----</FONT>
<FONT COLOR="#737373">> *From*: Reindl Harald <<A \
HREF="mailto:h.reindl@thelounge.net">h.reindl@thelounge.net</A></FONT> <FONT \
COLOR="#737373">> <<A \
HREF="mailto:Reindl%20Harald%20%3ch.reindl@thelounge.net">mailto:Reindl%20Harald%20%3ch.reindl@thelounge.net</A>%3e>></FONT>
<FONT COLOR="#737373">> *To*: <A \
HREF="mailto:openvas-discuss@wald.intevation.org">openvas-discuss@wald.intevation.org</A></FONT>
<FONT COLOR="#737373">> <<A \
HREF="mailto:openvas-discuss@wald.intevation.org">mailto:openvas-discuss@wald.intevation.org</A>></FONT>
<FONT COLOR="#737373">> *Subject*: Re: [Openvas-discuss] GSA crashes / OpenVAS \
hungs</FONT> <FONT COLOR="#737373">> *Date*: Fri, 3 Feb 2017 16:17:53 +0100</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">> Am 03.02.2017 um 16:04 schrieb tatooin:</FONT>
<FONT COLOR="#737373">>> I can resume works for some times. But again, as soon \
as the load</FONT> <FONT COLOR="#737373">>> becomes significant, gsa crashes \
and openvassd becomes unresponsive.</FONT> <FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> It's not a load problem are purging/restarting redis \
is the key.</FONT> <FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> Apart from commenting out all save options in \
redis.conf, is there</FONT> <FONT COLOR="#737373">>> anything I am missing with \
redis to get it work properly ?</FONT> <FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> I have the following error logs when gsa crashes in \
openvassd.messages:</FONT> <FONT COLOR="#737373">>> /[Fri Feb 3 14:40:18 \
2017][7333] Client abruptly closed the communication/</FONT> <FONT \
COLOR="#737373">>> /[Fri Feb 3 14:40:18 2017][7333] Test complete/</FONT> <FONT \
COLOR="#737373">>> /[Fri Feb 3 14:40:18 2017][15974] Process 16844 (OID:</FONT> \
<FONT COLOR="#737373">>> 1.3.6.1.4.1.25623.1.0.805139) seems to have died too \
early/</FONT> <FONT COLOR="#737373">>> /[Fri Feb 3 14:40:18 2017][15968] \
Process 7400 (OID:</FONT> <FONT COLOR="#737373">>> \
1.3.6.1.4.1.25623.1.0.105211) seems to have died too early/</FONT> <FONT \
COLOR="#737373">>> /[Fri Feb 3 14:40:18 2017][15970] Process 16513 (OID:</FONT> \
<FONT COLOR="#737373">>> 1.3.6.1.4.1.25623.1.0.805927) seems to have died too \
early/</FONT> <FONT COLOR="#737373">>> /[....continuing....]/</FONT>
<FONT COLOR="#737373">>> /openvassd: testing \
10.169.74.94(sighand_segv+0x7c)[0x56176464e10c]/</FONT> <FONT \
COLOR="#737373">>> /openvassd: testing \
10.169.74.91(sighand_segv+0x7c)[0x56176464e10c]/</FONT> <FONT \
COLOR="#737373">>> \
//lib/x86_64-linux-gnu/libc.so.6(+0x33040)[0x7f574a5a0040]/</FONT> <FONT \
COLOR="#737373">>> \
//lib/x86_64-linux-gnu/libc.so.6(+0x33040)[0x7f574a5a0040]/</FONT> <FONT \
COLOR="#737373">></FONT> <FONT COLOR="#737373">> these are segfaults</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">> how many RAM has the machine?</FONT>
<FONT COLOR="#737373">> what does dmesg say?</FONT>
<FONT COLOR="#737373">> what doe sthe global syslog say?</FONT>
<FONT COLOR="#737373">> how have you installed openvas?</FONT>
<FONT COLOR="#737373">> did you ask on a kali linux channel?</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">> each and every time kali linux is mentioned on this than \
becuse nothing</FONT> <FONT COLOR="#737373">> works as expeted....</FONT>
_______________________________________________
Openvas-discuss mailing list
<A HREF="mailto:Openvas-discuss@wald.intevation.org">Openvas-discuss@wald.intevation.org</A>
<A HREF="https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss">https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss</A>
</PRE>
</BODY>
</HTML>
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic