Since openvas-scapdata-sync didn't help, deleting and recreating /var/lib/openvas/scap-data fixed the issue.
Thanks, Helmut 05.08.2014----14:30:48"Openvas-discuss" <[email protected]> wrote on 05.08.2014 14:30:48: > From: Rene Behring < [email protected]>> To: Openvas Mailingliste Englisch <openvas-discuss @wald.intevation.org>, > Date: 05.08.2014 14:31> Subject: Re: [Openvas-d iscuss] Number of Feeds> Sent by: "Openvas-discuss" <openvas-discuss-bounc [email protected]>> > well, i think the openvas-scapdata-sync is building the scap.db. > if you haven’t tried a openvas-scapdata-sync try that or try > openvas-scapdata-sync —help to see what else is possible. > > i just testet if it has something to do with an openvas --rebuild. > so i backed up and deleted the hole /var/lib/openvas/scap-data, > after that the manager wasn’t running anymore. > then i run openvas-scapdata-sync and everything was fixed. > all without a rebuild or something else. > so you only need to refresh the cache and rebuild when there are new NVTs. > > Rene > > > Am 05.08.2014 um 14:14 schrieb Helmut Koers <[email protected]>: > > > I am not sure if CVEs and CPEs have anything to do with rebuild, I was > > just expecting. In case they are not part of the NVT cache, you are right. > > > > I am updating Feeds exactly the way you described: > > > > 1) openvas-nvt-sync, openvas-scapdata-sync, openvas-certdata-sync > > 2) service openvas-scanner restart > > 3) openvasmd --rebuild > > > > Can/must I build the SCAP DB from scratch? > > > > Helmut > > > > > > 05.08.2014----11:47:32"Openvas-discuss" > > <[email protected]> wrote on 05.08.2014 > > 11:47:32: > > > >> From: Rene Behring < > > [email protected]>> To: Openvas Mailingliste Englisch > > <openvas-discuss > > @wald.intevation.org>, > > > Date: 05.08.2014 11:47> Subject: Re: [Openvas-d > > iscuss] Number of Feeds> Sent by: "Openvas-discuss" <openvas-discuss-bounc > > [email protected]>> > >> The CVEs and CPEs (scap data) doesn’t have anything to do with the > >> rebuild as far as i know… please correct me if i am wrong... > >> > >> how do you update them normally? > >> > >> Well, normally you just have to do it like this: > >> 1. sync all the feeds (openvas-nvt-sync, openvas-certdata-sync, > >> openvas-scapdata-sync) > >> 2. restart the scanner, that loads the new feeds into the cache (a > >> openvassd —only-cache should be enough if the scanner is running...) > >> 3. when the scanner is finished loading and is still running(!) you > >> can start the „openvasmd —rebuild“ > >> finish > >> > >> Rene > >> > >> Am 05.08.2014 um 11:29 schrieb Helmut Koers <[email protected]>: > >> > >>> Hi, > >>> Ia have two OpenVAS 6 systems running, which unfortunately do have a > >>> different ammonut of feeds as you can see below: > >>> > >>> SecInfo Management: > >>> equal number of: NVTs (35685), OVAL Definitions (24012) and DFN-VERT > >>> Advisories (9820) > >>> unequal number of: CVEs (63475 / 63575) and CPEs (185242 / 185660) > >>> > >>> I have rebooted the systems and run openvasmd --rebuild a couple of > > time, > >>> but with no effect. > >>> > >>> Any idea why that happend and how I can sort this out? > >>> > >>> Thanks, Helmut > >>> _______________________________________________ > >>> 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
