Hi Brandon: Thanks for the quick response. However I tried the openvasmd --update as well as reboot the machine, but the problem remains. Do you think I can find the clue somewhere else? Is there a way to debug further this problem? Thanks!
On Tue, Nov 19, 2013 at 2:19 PM, Brandon Perry <[email protected]>wrote: > I hAve resolved a similar issue by running openvasmd --update and restart > (computer or openvasmd) iirc. If you run omp with full verbosity, you will > see the xml gets cut off, so it is no longer well formed. > > Sent from a computer > > > On Nov 19, 2013, at 13:10, Shang Wang <[email protected]> wrote: > > > > Dear all: > > > > I installed openvas and found out one of the commands does not return > any result: > > > > '<get_nvts config_id="04d2667f-792d-45e6-90e0-48eebd7e5599"/>' > > > > This is supposed to give all the families and the plugin ids belong to > that family. However, openvas returned "Failed to read response", and in > the openvasmd.log shows: > > > > main:CRITICAL:2013-11-19 19h04.15 UTC:10426: handle_sigabrt: abort > > > > However, if I query for each family like the following, it works just > fine: > > > > '<get_nvts config_id="04d2667f-792d-45e6-90e0-48eebd7e5599" family="Port > scanners"/>' > > > > Can anybody help with above error? Thanks! > > _______________________________________________ > > 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
