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, [email protected] 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" <[email protected]> > À: [email protected] > Cc: "Reindl Harald" <[email protected]>, > [email protected] > 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, [email protected] 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 >> <get_settings setting_id="20f3[...] >> lib serv: DEBUG:2016-09-26 13h40.29 CEST:5476: => <get_settings >> setting_id="20f3034c-e709-11e1-87e7-406186ea4fc5"/> >> 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: <= <get_settings_response >> status="200" status_text="OK"><filters><term></term></filters><settings >> start="1" max="-1"/><setting >> id="20f3034c-e709-11e1-87e7-406186ea4fc5"><name>Wizard >> Rows</name><comment>If the number of rows in a listing is above this any >> wizard be hidden.</comment><value>3</value></setting><setting >> id="20f3034c-e709-11e1-87e7-406186ea4fc5"><name>Wizard >> Rows</name><comment>If the number of rows in a listing is above this any >> wizard be >> hidden.</comment><value>3</value></setting><setting_count><filtered>46</filtered><page>2</page></setting_count></get_settings_response> >> >> The crash time and last log time are consistent. But I don't see anything >> wrong. >> >> Any idea ? >> >> Thanks >> >> ----- Mail original ----- >> De: "tatooin" <[email protected]> >> À: "Reindl Harald" <[email protected]> >> Cc: [email protected] >> 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 >>> [email protected] >>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
