I found the solution, or I should say I’m able to run the tasks now. The answer
lies in the following:
http://openvas-discuss.wald.intevation.narkive.com/40QcF1xA/openvasmd-regular-tasks-db-corruption-issue
I ran the sqlite command “sqlite3 tasks.db "PRAGMA integrity_check;"
And it came
Update. I just decided to run openvasmd --rebuild --progress --verbose
The bar rotated for a few moments, but it been handing at the following for
close to an hour:
Updating NVT cache... /
I ran across a similar thread on Kali that was just updated yesterday:
Thanks Brandon, but it doesn’t appear this is ever going to finish. I had
started the rebuild immediately upon receipt of your email, and 40 minutes
later it is still rebuilding.
From: Brandon Perry [mailto:bperry.volat...@gmail.com]
Sent: Wednesday, September 14, 2016 2:50 PM
To: Allyn
Rebuilding takes a while. In the future —update is also a viable option, but I
usually just run rebuild.
> On Sep 14, 2016, at 3:31 PM, Allyn Baskerville wrote:
>
> Thanks Brandon, but it doesn’t appear this is ever going to finish. I had
> started the rebuild immediately
Please run openvasmd --rebuild and restart the manager (latter probably not
needed).
> On Sep 14, 2016, at 2:41 PM, Allyn Baskerville wrote:
>
> The scans were running fine for a few weeks, but they stopped a couple days
> ago. OpenVAS 8 is running on CentOS 7. I created a
The scans were running fine for a few weeks, but they stopped a couple days
ago. OpenVAS 8 is running on CentOS 7. I created a script to automatically
update the NVTs as follows:
#!/bin/sh
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
/usr/sbin/openvas-nvt-sync | mail
Thanks Reindl, and actually I agree with you given the number of stupid
issues I've struggled with since using Kali. But unfortunately, for
pentesting, I don't see any alternatives to kali.
Anyway thanks for posting your scripts, I'm using yours now. For
reference, the default logrotate files
Am 14.09.2016 um 14:42 schrieb tatooin:
Yes, I understand that. But the point is; why is this broken logrotate
script shipped by default with OpenVas (and actually, GSA) on kali ?
because "kali" without ever used it seems to be a broken distribution
when they are even not capable to write a
On Wed, 2016-09-14 at 13:26 +0200, Christian Fischer wrote:
> Hi,
>
> On 09/14/2016 01:19 PM, tatooin wrote:
> > I can actually witness the same situation with openvas. Whenever the
> > logfile is rotated, the new logfile remain empty.
>
> which is expected depending on your logrotate script.
Am 14.09.2016 um 13:19 schrieb tatooin:
GSA crashed again, but unfortunately the /var/log/openvas/gsad.log file
is empty. It was rotated yesterday, and the new logfile is empty
so why don't you just look in the old one?
what says "ls -lh /var/log/openvas/"
and if it's .xz, .gz or .bz2 use
Hi Fabio,
GSA crashed again, but unfortunately the /var/log/openvas/gsad.log file
is empty. It was rotated yesterday, and the new logfile is empty.
I can actually witness the same situation with openvas. Whenever the
logfile is rotated, the new logfile remain empty.
However, I checked gsa this
Hi Fabio,
I'm not sure how to actually do this. Could you give an example of such
command ?
Thank you !
On Tue, 2016-09-06 at 15:12 +0100, Fábio Fernandes wrote:
> That is to enable overrides i was trying to say to add the override
> with amp CLI but it is just an idea.
>
>
Hi,
On 09/07/2016 06:00 PM, Christian Fischer wrote:
> On 09/07/2016 05:02 PM, Jiri K. wrote:
>> the "Directories used for CGI Scanning" NVT does not detect that folder,
>> but it's easy to add it manually in the Scan Config, so it would solve
>> the problem for me if the PHP detection NVT tried
13 matches
Mail list logo