as often discussed you need a specific version if libmicrohttpd and "exclude=libmicrohttpd" in any active repo with a newer version http://lists.wald.intevation.org/pipermail/openvas-discuss/2011-November/003613.html
even on CentOS6: libmicrohttpd-0.9.7-1.el6.art.x86_64 and "exclude=libmicrohttpd" in CentOS-repos but i had no luck at all on Fedora 16/17 and switched to CentOS6 since a securiyt scanner should always run on a dedicated machine what makes it no longer matter which OS you run for it Am 05.04.2013 21:29, schrieb smkr: > Using packages from Atomic F17: > > [root@pc96 ~]# rpm -qa | grep -e openvas -e greenbone > openvas-cli-1.1.5-3.fc17.art.x86_64 > openvas-1.0-7.fc17.art.noarch > openvas-manager-3.0.5-7.fc17.art.x86_64 > openvas-libraries-5.0.4-5.fc17.art.x86_64 > openvas-scanner-3.3.1-4.fc17.art.x86_64 > openvas-administrator-1.2.1-2.fc17.art.x86_64 > greenbone-security-assistant-3.0.3-3.fc17.art.x86_64 > > First I thought to have hit this: > > > http://lists.wald.intevation.org/pipermail/openvas-discuss/2011-December/003699.html > > > as it worked fine before I pushed the sleep button last night. Proceeded with > testing with both upgrading to latest limbmicrothttpd (0.9.26) and > downgrading > to oldest (0.9.16). No luck though. > > Then found: > > > http://www.backtrack-linux.org/wiki/index.php/OpenVas#Starting_OpenVAS_with_a_web_browser_as_the_scanning_interface > > > and noticed '--httpd-only'. Hmm, that did it. > > > Since I don't need https changing the service files did the trick for me but > I'd like to know what's causing it to hang, how to troubleshoot and if there > is > a solution to it. > > Any thoughts? > Much thanks
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
