subject:"\[Openvas\-discuss\] GSA crashes, no log"

Re: [Openvas-discuss] GSA crashes, no log

2016-09-28 Thread Fábio Fernandes

Try to use a version where it is not upgraded and see if that behavior persists 
maybe it’s a bug in the new version or try the Virtual Appliance from the 
OpenVAS site.

Fabio

> No dia 28/09/2016, às 08:20, tato...@free.fr escreveu:
> 
> Actually the GSAD is still running, but refusing connections to the service, 
> like if the port was no longer open. 
> 
> Tracing the process don't show any activity. It's just stalling... like it's 
> frozen. 
> 
> - Mail original -
> De: "Fábio Fernandes" <fabiogfernan...@gmail.com>
> À: tato...@free.fr
> Cc: "Reindl Harald" <h.rei...@thelounge.net>, 
> openvas-discuss@wald.intevation.org
> Envoyé: Mercredi 28 Septembre 2016 01:25:43
> Objet: Re: [Openvas-discuss] GSA crashes, no log
> 
> I don’t see anything in the log. What kind of crash is it? GSAD terminates or 
> the website gets unresponsive? 
> You said that you upgraded GSAD maybe you can try to use a version where it 
> is not upgraded and see if that behavior persists.
> 
> Fabio.
> 
>> No dia 26/09/2016, às 13:21, tato...@free.fr escreveu:
>> 
>> Hello,
>> 
>> Crash just happened again. Now I have logs but I'm afraid it won't help. 
>> Here are the last lines:
>> 
>> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476:send 65 from 
>> 
>> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476: => done
>> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476:asking for 1048576
>> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476: <= > status="200" status_text="OK">> start="1" max="-1"/>> id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard 
>> RowsIf the number of rows in a listing is above this any 
>> wizard be hidden.3> id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard 
>> RowsIf the number of rows in a listing is above this any 
>> wizard be 
>> hidden.3462
>> 
>> The crash time and last log time are consistent. But I don't see anything 
>> wrong. 
>> 
>> Any idea ?
>> 
>> Thanks
>> 
>> - Mail original -
>> De: "tatooin" <tato...@free.fr>
>> À: "Reindl Harald" <h.rei...@thelounge.net>
>> Cc: openvas-discuss@wald.intevation.org
>> Envoyé: Mercredi 14 Septembre 2016 16:33:56
>> Objet: Re: [Openvas-discuss] GSA crashes, no log
>> 
>> 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 shipped with kali contains:
>> 
>> 
>> /var/log/openvas/gsad.log {
>> missingok
>> notifempty
>> create 640 root adm
>> daily
>> rotate 7
>> compress
>> postrotate
>>   if [ -s /var/run/gsad.pid ]; then kill -1 `cat /var/run/gsad.pid`;
>> fi
>>   openvaslogs=`ls /var/log/openvas/gsad.log.*`
>>   if [ -n "$openvaslogs" ]; then
>>   chown root:adm $openvaslogs
>>   chmod 640 $openvaslogs
>>   fi
>> endscript
>> }
>> 
>> Same for openvas manager and scanner...
>> 
>> On Wed, 2016-09-14 at 16:14 +0200, Reindl Harald wrote:
>>> 
>>> 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 working logrotate script which 
>>> sends a SIGHUP to the process to actually get the filehandle closed
>>> 
>>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
>>> # logrotate for openvas-manager
>>> /var/log/openvas/openvas-gsa.log {
>>>rotate 4
>>>weekly
>>>compress
>>>delaycompress
>>>missingok
>>>postrotate
>>>/usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
>>>endscript
>>> }
>>> 
>>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
>>> # logrotate for openvas-manager
>>> /var/log/openvas/openvasmd.log {
>>>rotate 4
>>>weekly
>>>compress
>>>delaycompress
>>>missingok
>>>postrotate
>>>/usr/b

Re: [Openvas-discuss] GSA crashes, no log

2016-09-28 Thread tatooin

Actually the GSAD is still running, but refusing connections to the service, 
like if the port was no longer open. 

Tracing the process don't show any activity. It's just stalling... like it's 
frozen. 

- Mail original -
De: "Fábio Fernandes" <fabiogfernan...@gmail.com>
À: tato...@free.fr
Cc: "Reindl Harald" <h.rei...@thelounge.net>, 
openvas-discuss@wald.intevation.org
Envoyé: Mercredi 28 Septembre 2016 01:25:43
Objet: Re: [Openvas-discuss] GSA crashes, no log

I don’t see anything in the log. What kind of crash is it? GSAD terminates or 
the website gets unresponsive? 
You said that you upgraded GSAD maybe you can try to use a version where it is 
not upgraded and see if that behavior persists.

Fabio.

> No dia 26/09/2016, às 13:21, tato...@free.fr escreveu:
> 
> Hello,
> 
> Crash just happened again. Now I have logs but I'm afraid it won't help. Here 
> are the last lines:
> 
> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476:send 65 from 
> 
> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476: => done
> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476:asking for 1048576
> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476: <=  status="200" status_text="OK"> start="1" max="-1"/> id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard RowsIf 
> the number of rows in a listing is above this any wizard be 
> hidden.3 id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard RowsIf 
> the number of rows in a listing is above this any wizard be 
> hidden.3462
> 
> The crash time and last log time are consistent. But I don't see anything 
> wrong. 
> 
> Any idea ?
> 
> Thanks
> 
> - Mail original -----
> De: "tatooin" <tato...@free.fr>
> À: "Reindl Harald" <h.rei...@thelounge.net>
> Cc: openvas-discuss@wald.intevation.org
> Envoyé: Mercredi 14 Septembre 2016 16:33:56
> Objet: Re: [Openvas-discuss] GSA crashes, no log
> 
> 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 shipped with kali contains:
> 
> 
> /var/log/openvas/gsad.log {
>  missingok
>  notifempty
>  create 640 root adm
>  daily
>  rotate 7
>  compress
>  postrotate
>if [ -s /var/run/gsad.pid ]; then kill -1 `cat /var/run/gsad.pid`;
> fi
>openvaslogs=`ls /var/log/openvas/gsad.log.*`
>if [ -n "$openvaslogs" ]; then
>chown root:adm $openvaslogs
>chmod 640 $openvaslogs
>fi
>  endscript
> }
> 
> Same for openvas manager and scanner...
> 
> On Wed, 2016-09-14 at 16:14 +0200, Reindl Harald wrote:
>> 
>> 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 working logrotate script which 
>> sends a SIGHUP to the process to actually get the filehandle closed
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
>> # logrotate for openvas-manager
>> /var/log/openvas/openvas-gsa.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
>> # logrotate for openvas-manager
>> /var/log/openvas/openvasmd.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP openvasmd > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-scanner
>> # logrotate for openvas
>> /var/log/openvas/openvassd.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP openvassd > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>>> Probably a question best posted to Kali forums, though
>> 
>> yes
>> ___
>> Openvas-

Re: [Openvas-discuss] GSA crashes, no log

2016-09-27 Thread Fábio Fernandes

I don’t see anything in the log. What kind of crash is it? GSAD terminates or 
the website gets unresponsive? 
You said that you upgraded GSAD maybe you can try to use a version where it is 
not upgraded and see if that behavior persists.

Fabio.

> No dia 26/09/2016, às 13:21, tato...@free.fr escreveu:
> 
> Hello,
> 
> Crash just happened again. Now I have logs but I'm afraid it won't help. Here 
> are the last lines:
> 
> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476:send 65 from 
> 
> lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476: => done
> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476:asking for 1048576
> lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476: <=  status="200" status_text="OK"> start="1" max="-1"/> id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard RowsIf 
> the number of rows in a listing is above this any wizard be 
> hidden.3 id="20f3034c-e709-11e1-87e7-406186ea4fc5">Wizard RowsIf 
> the number of rows in a listing is above this any wizard be 
> hidden.3462
> 
> The crash time and last log time are consistent. But I don't see anything 
> wrong. 
> 
> Any idea ?
> 
> Thanks
> 
> - Mail original -
> De: "tatooin" <tato...@free.fr>
> À: "Reindl Harald" <h.rei...@thelounge.net>
> Cc: openvas-discuss@wald.intevation.org
> Envoyé: Mercredi 14 Septembre 2016 16:33:56
> Objet: Re: [Openvas-discuss] GSA crashes, no log
> 
> 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 shipped with kali contains:
> 
> 
> /var/log/openvas/gsad.log {
>  missingok
>  notifempty
>  create 640 root adm
>  daily
>  rotate 7
>  compress
>  postrotate
>if [ -s /var/run/gsad.pid ]; then kill -1 `cat /var/run/gsad.pid`;
> fi
>openvaslogs=`ls /var/log/openvas/gsad.log.*`
>if [ -n "$openvaslogs" ]; then
>chown root:adm $openvaslogs
>chmod 640 $openvaslogs
>fi
>  endscript
> }
> 
> Same for openvas manager and scanner...
> 
> On Wed, 2016-09-14 at 16:14 +0200, Reindl Harald wrote:
>> 
>> 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 working logrotate script which 
>> sends a SIGHUP to the process to actually get the filehandle closed
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
>> # logrotate for openvas-manager
>> /var/log/openvas/openvas-gsa.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
>> # logrotate for openvas-manager
>> /var/log/openvas/openvasmd.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP openvasmd > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>> [root@openvas:~]$ cat /etc/logrotate.d/openvas-scanner
>> # logrotate for openvas
>> /var/log/openvas/openvassd.log {
>> rotate 4
>> weekly
>> compress
>> delaycompress
>> missingok
>> postrotate
>> /usr/bin/killall -HUP openvassd > /dev/null 2>&1 || true
>> endscript
>> }
>> 
>>> Probably a question best posted to Kali forums, though
>> 
>> yes
>> ___
>> 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

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

Re: [Openvas-discuss] GSA crashes, no log

2016-09-26 Thread tatooin

Hello,

Crash just happened again. Now I have logs but I'm afraid it won't help. Here 
are the last lines:

lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476:send 65 from 
lib  serv:  DEBUG:2016-09-26 13h40.29 CEST:5476: => done
lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476:asking for 1048576
lib   xml:  DEBUG:2016-09-26 13h40.29 CEST:5476: <= Wizard RowsIf 
the number of rows in a listing is above this any wizard be 
hidden.3Wizard RowsIf 
the number of rows in a listing is above this any wizard be 
hidden.3462

The crash time and last log time are consistent. But I don't see anything 
wrong. 

Any idea ?

Thanks

- Mail original -
De: "tatooin" <tato...@free.fr>
À: "Reindl Harald" <h.rei...@thelounge.net>
Cc: openvas-discuss@wald.intevation.org
Envoyé: Mercredi 14 Septembre 2016 16:33:56
Objet: Re: [Openvas-discuss] GSA crashes, no log

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 shipped with kali contains:


/var/log/openvas/gsad.log {
  missingok
  notifempty
  create 640 root adm
  daily
  rotate 7
  compress
  postrotate
if [ -s /var/run/gsad.pid ]; then kill -1 `cat /var/run/gsad.pid`;
fi
openvaslogs=`ls /var/log/openvas/gsad.log.*`
if [ -n "$openvaslogs" ]; then
chown root:adm $openvaslogs
chmod 640 $openvaslogs
fi
  endscript
}

Same for openvas manager and scanner...

On Wed, 2016-09-14 at 16:14 +0200, Reindl Harald wrote:
> 
> 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 working logrotate script which 
> sends a SIGHUP to the process to actually get the filehandle closed
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
> # logrotate for openvas-manager
> /var/log/openvas/openvas-gsa.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
>  endscript
> }
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
> # logrotate for openvas-manager
> /var/log/openvas/openvasmd.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP openvasmd > /dev/null 2>&1 || true
>  endscript
> }
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-scanner
> # logrotate for openvas
> /var/log/openvas/openvassd.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP openvassd > /dev/null 2>&1 || true
>  endscript
> }
> 
> > Probably a question best posted to Kali forums, though
> 
> yes
> ___
> 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] GSA crashes, no log

2016-09-14 Thread tatooin

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 shipped with kali contains:


/var/log/openvas/gsad.log {
  missingok
  notifempty
  create 640 root adm
  daily
  rotate 7
  compress
  postrotate
if [ -s /var/run/gsad.pid ]; then kill -1 `cat /var/run/gsad.pid`;
fi
openvaslogs=`ls /var/log/openvas/gsad.log.*`
if [ -n "$openvaslogs" ]; then
chown root:adm $openvaslogs
chmod 640 $openvaslogs
fi
  endscript
}

Same for openvas manager and scanner...

On Wed, 2016-09-14 at 16:14 +0200, Reindl Harald wrote:
> 
> 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 working logrotate script which 
> sends a SIGHUP to the process to actually get the filehandle closed
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
> # logrotate for openvas-manager
> /var/log/openvas/openvas-gsa.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
>  endscript
> }
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
> # logrotate for openvas-manager
> /var/log/openvas/openvasmd.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP openvasmd > /dev/null 2>&1 || true
>  endscript
> }
> 
> [root@openvas:~]$ cat /etc/logrotate.d/openvas-scanner
> # logrotate for openvas
> /var/log/openvas/openvassd.log {
>  rotate 4
>  weekly
>  compress
>  delaycompress
>  missingok
>  postrotate
>  /usr/bin/killall -HUP openvassd > /dev/null 2>&1 || true
>  endscript
> }
> 
> > Probably a question best posted to Kali forums, though
> 
> yes
> ___
> 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] GSA crashes, no log

2016-09-14 Thread Reindl Harald




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 working logrotate script which 
sends a SIGHUP to the process to actually get the filehandle closed


[root@openvas:~]$ cat /etc/logrotate.d/openvas-gsa
# logrotate for openvas-manager
/var/log/openvas/openvas-gsa.log {
rotate 4
weekly
compress
delaycompress
missingok
postrotate
/usr/bin/killall -HUP gsad > /dev/null 2>&1 || true
endscript
}

[root@openvas:~]$ cat /etc/logrotate.d/openvas-manager
# logrotate for openvas-manager
/var/log/openvas/openvasmd.log {
rotate 4
weekly
compress
delaycompress
missingok
postrotate
/usr/bin/killall -HUP openvasmd > /dev/null 2>&1 || true
endscript
}

[root@openvas:~]$ cat /etc/logrotate.d/openvas-scanner
# logrotate for openvas
/var/log/openvas/openvassd.log {
rotate 4
weekly
compress
delaycompress
missingok
postrotate
/usr/bin/killall -HUP openvassd > /dev/null 2>&1 || true
endscript
}


Probably a question best posted to Kali forums, though


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

Re: [Openvas-discuss] GSA crashes, no log

2016-09-14 Thread tatooin


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. You need to reload
> all services after logrotating. If this is not done the new logfile
> remains empty. See an example here:
> 
> https://stackoverflow.com/questions/36325214/how-does-nginx-restart-after-being-killed-by-log-rotate
> 

Yes, I understand that. But the point is; why is this broken logrotate
script shipped by default with OpenVas (and actually, GSA) on kali ?

Probably a question best posted to Kali forums, though.

Best,

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

Re: [Openvas-discuss] GSA crashes, no log

2016-09-14 Thread Reindl Harald




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
xzcat
zcat
bzcat
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] GSA crashes, no log

2016-09-14 Thread tatooin

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 morning and it was working fine, while the
logfile was rotated yesterday, so I'm not sure it's related. 

Any clue ?

Thanks

On Tue, 2016-09-13 at 11:00 +0100, Fábio Fernandes wrote:
> I’m not using OpenVAS Kali version anymore but you could try to increase the 
> log level at "/etc/openvas/gsad_log.conf”.
> 
> [*]
> prepend=%t %p
> prepend_time_format=%Y-%m-%d %Hh%M.%S %Z
> file=/var/log/openvas/gsad.log
> level=0
> 
> Change level to “level=128” and restart GSAD then see what happens.
> 
> Fabio
> 
> > No dia 13/09/2016, às 10:21, tatooin  escreveu:
> > 
> > Hello,
> > 
> > Since I upgraded to GSA 6.0.10-0kali1, using standard Kali repos, GSA is
> > crashing from times to times; in general 2 or 3 times a week. I just
> > have to restart the service and it's working again. 
> > 
> > The logfile is empty. Is there anything I could configure on GSA side to
> > check what's going on ? I don't see any particular loggings directives
> > nor options if I run the daemon in the foreground with --help.
> > 
> > Thank you
> > 
> > ___
> > 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] GSA crashes, no log

2016-09-13 Thread tatooin

Done. Thank you Fabio. Let's see what happens now..

Best,

On Tue, 2016-09-13 at 11:00 +0100, Fábio Fernandes wrote:
> I’m not using OpenVAS Kali version anymore but you could try to increase the 
> log level at "/etc/openvas/gsad_log.conf”.
> 
> [*]
> prepend=%t %p
> prepend_time_format=%Y-%m-%d %Hh%M.%S %Z
> file=/var/log/openvas/gsad.log
> level=0
> 
> Change level to “level=128” and restart GSAD then see what happens.
> 
> Fabio
> 
> > No dia 13/09/2016, às 10:21, tatooin  escreveu:
> > 
> > Hello,
> > 
> > Since I upgraded to GSA 6.0.10-0kali1, using standard Kali repos, GSA is
> > crashing from times to times; in general 2 or 3 times a week. I just
> > have to restart the service and it's working again. 
> > 
> > The logfile is empty. Is there anything I could configure on GSA side to
> > check what's going on ? I don't see any particular loggings directives
> > nor options if I run the daemon in the foreground with --help.
> > 
> > Thank you
> > 
> > ___
> > 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] GSA crashes, no log

2016-09-13 Thread Fábio Fernandes

I’m not using OpenVAS Kali version anymore but you could try to increase the 
log level at "/etc/openvas/gsad_log.conf”.

[*]
prepend=%t %p
prepend_time_format=%Y-%m-%d %Hh%M.%S %Z
file=/var/log/openvas/gsad.log
level=0

Change level to “level=128” and restart GSAD then see what happens.

Fabio

> No dia 13/09/2016, às 10:21, tatooin  escreveu:
> 
> Hello,
> 
> Since I upgraded to GSA 6.0.10-0kali1, using standard Kali repos, GSA is
> crashing from times to times; in general 2 or 3 times a week. I just
> have to restart the service and it's working again. 
> 
> The logfile is empty. Is there anything I could configure on GSA side to
> check what's going on ? I don't see any particular loggings directives
> nor options if I run the daemon in the foreground with --help.
> 
> Thank you
> 
> ___
> 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] GSA crashes, no log

2016-09-13 Thread tatooin

Hello,

Since I upgraded to GSA 6.0.10-0kali1, using standard Kali repos, GSA is
crashing from times to times; in general 2 or 3 times a week. I just
have to restart the service and it's working again. 

The logfile is empty. Is there anything I could configure on GSA side to
check what's going on ? I don't see any particular loggings directives
nor options if I run the daemon in the foreground with --help.

Thank you

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

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

Re: [Openvas-discuss] GSA crashes, no log

[Openvas-discuss] GSA crashes, no log

12 matches

Site Navigation

Mail list logo

Footer information