No dia 11/10/2016, às 09:52, Παναγιώτης Λεόντιος
<[email protected]> escreveu:
Dear Michael,
Following my last email below, I run a new task with everything left
to default (Scan config: discovery) and it stuck to "Requested";
never continued to a percentage.
Of course, when requested the current report, it produced the known
internal error :(
P.S. One more thing; when I run "openvas-start" in my command line
before GSA, it produces an error saying that manager daemon cannot
run.
After running "openvasmd" and then "openvas-start", everything is OK
(checked by "openvas-check-setup" and "systemctl status
openvas-manager.service").
Panagiotis Leontios
Business Engineer | Project Manager | Consultant
BEng, DIC, MSc, MBA
M: +30 6977 976269
E: [email protected]
B: pleontios.wordpress.com [1]
L: www.linkedin.com/in/leontios [2]
T: @pleontios
-----Original Message-----
From: Παναγιώτης Λεόντιος
[mailto:[email protected]]
Sent: Tuesday, October 11, 2016 11:17 AM
To: '[email protected]'
Cc: '[email protected]'
Subject: RE: [Openvas-discuss] INTERNAL ERROR IN GSA
Dear Michael, thanks again for your response.
Actually, in the screenshot was the error message:
“INTERNAL ERROR: GET_REPORT:12102 (GSA 6.0.10) ...
Diagnostics: Failure to receive response from Manager Daemon"
The target IPs, Portlist, AliveCheck is set to default; Scan is set
to Fast and Full. Actually, just created a new task with defaults;
Only Fast and Full was set differently.
YES, I run it on Vbox (5.1.6) with default configuration as provided
by official .ova file (kali-linux-i686) -ram 2048, 2 CPUs, etc.
(*) I don’t understand that htop thing though.
(*) I will try to run the task starting by " Full and Very Deep
Ultimate scan configuration " according to your link and let you
know.
(*) I have all the updates, dist-upgrades done, as well as openvas
recent install, and check-setup resulted OK.
Panos
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Monday, October 10, 2016 7:01 PM
To: Παναγιώτης Λεόντιος
Cc: [email protected]
Subject: RE: [Openvas-discuss] INTERNAL ERROR IN GSA
Dear Panos,
i am sorry, but unfortunately i am unable to view your screenshots
as something (probably on my side, limited environment) breaks them.
If they contain no further sensitive information, you could maybe
upload them at an imagehoster (directupload.net [3] i.e.) and send
me the link?
Just to be clear about that- could you maybe be affected by this
Problem: https://bugs.kali.org/view.php?id=3055 [4] ?
If yes, use a different Scanconfig (start minimalistic with
"Discovery"
for example, then go with "Full and Fast").
In general, some more details about how you have setup your scan
could be of help.
(i.e. how many target ip's are scanned, what Portlist is being used,
what AliveCheck, Scanconfig, etc.).
Please also provide the following: a screenshot of htop, which has
been filtered before to "openvas" (you can filter in htop by hitting
the "F4"
key).
If you run this as a VirtualMachine, ensure that you have allocated
enough hardware ressources to the vm.
Kind Regards,
Michael Eissele.
On 10.10.2016 17:05, Παναγιώτης Λεόντιος wrote:
Thank you Michael.
Yes, I have run "openvas-check-setup" script and it reported OK.
Also, please see below my current state of the problem:
Well, I have successfully completed an installation of Kali 32 in
Vbox, installed openvas, checked its setup and run GSA.
When running my first task, it freezes in requested mode and
additionally, when pressing on the bar to get a report the following
error message is produced
Thank you in advance.
P.S. I have installed kali 32 perfectly OK on a USB (in persistence
mode), and also the demo in the same VB.
But this one……
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Monday, October 10, 2016 6:00 PM
To: Παναγιώτης Λεόντιος
Cc: [email protected]
Subject: RE: [Openvas-discuss] INTERNAL ERROR IN GSA
Dear Panos,
thank you for reaching back.
From what you have reported, it seems that your installation may be
in an inconsistant state in general.
Is this the first time you run scans on this installation, or had
this
installation already been running for some time?
Nevertheless, we should go back and asure basic functionality as
this
seems messed up a bit.
Please visit: http://www.openvas.org/setup-and-start.html [5] [1]
You will find the "openvas-check-setup" script. Please run this and
follow possible occuring fixing advices.
We should only continue here if this script tells that everything is
ok, otherwise it won't make much sense.
Let us know after, thanks a lot.
Kind Regards,
Michael Eissele.
On 10.10.2016 13:06, Παναγιώτης Λεόντιος wrote:
And now I notice that the task does not move forward to a
percentage;
it has stuck to “requested” state…
Sth is wrong with the manager daemon?
FROM: Παναγιώτης Λεόντιος
[mailto:[email protected]]
SENT: Monday, October 10, 2016 1:58 PM
TO: '[email protected]'
SUBJECT: RE: [Openvas-discuss] INTERNAL ERROR IN GSA
I get this message again in a new task running (requested mode),
when
trying to get the report.
Panos
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Monday, October 10, 2016 1:41 PM
To: Παναγιώτης Λεόντιος
Subject: RE: [Openvas-discuss] INTERNAL ERROR IN GSA
Dear Pano,
this may occur because the affected report is appearing in the list
that loads when selecting report view.
Please go the way over Taskview, from there on you can check through
the reports and limit the trouble causing source to atleast to one
task maybe.
Once you have figured out the name of that report, you could try (as
mentioned in the previous reply) and delete this report with an
Admin
or Superadmin user.
If this doesn't work out, then let us know, we then have to remove
the
report manually from the machine.
Kind Regards,
Michael Eissele.
On 10.10.2016 12:30, Παναγιώτης Λεόντιος wrote:
Dear Michael,
