yu210148 / gvm_install

A script to install GVM 20 or 21 on Ubuntu 20.04 or Debian 10.
GNU General Public License v3.0
143 stars 72 forks source link

GVMD_DATA not updating. #72

Closed marchwicki closed 2 years ago

marchwicki commented 2 years ago

I'm getting "Too old (68 days) Please check the automatic synchronization of your system" for the the GVMD_DATA. I thought it was them not updating it but on a different install it's updating. Any ideas how I can update or troubleshoot this? Apologies I don't have more information for you. I'm kind of a noob with this product and am not sure where to look to troubleshoot.

marchwicki commented 2 years ago

The GUI is saying my GVMD_DATA version is 20220128T1556

yu210148 commented 2 years ago

Humm, I have the same thing and also thought it was just something that didn't change all that often on their end. I'll check into it when I get a chance.

Kev.

On Thu, Apr 7, 2022, 12:26 PM marchwicki @.***> wrote:

I'm getting "Too old (68 days) Please check the automatic synchronization of your system" for the the GVMD_DATA. I thought it was them not updating it but on a different install it's updating. Any ideas how I can update or troubleshoot this? Apologies I don't have more information for you. I'm kind of a noob with this product and am not sure where to look to troubleshoot.

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/72, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4PCQ4MYOAZCKJUCL6DVD4EEHANCNFSM5SZ5YAQA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

yu210148 commented 2 years ago

Was the other install where it is updating done with this script or another way?

On Thu, Apr 7, 2022, 12:28 PM marchwicki @.***> wrote:

The GUI is saying my GVMD_DATA version is 20220128T1556

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/72#issuecomment-1091957152, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4IMASTJSRRCAEF4XXTVD4EKXANCNFSM5SZ5YAQA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

marchwicki commented 2 years ago

Same install and update scripts for your repo.

yu210148 commented 2 years ago

Okay, cool. Very odd indeed; two instances, same script one good, one not.

The thing uses the random number generator to set up the cron jobs that do the updates so perhaps they're clobbering eachother on our non working setups. I'll have a look at mine when I get a sec. Could you post the crontab of the gvm user for your non working one vs the working one and we can compare?

Kev.

On Thu, Apr 7, 2022, 12:43 PM marchwicki @.***> wrote:

Same install and update scripts for your repo.

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/72#issuecomment-1091971266, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4JY7E45FZW4QABOSRLVD4GEPANCNFSM5SZ5YAQA . You are receiving this because you commented.Message ID: @.***>

yu210148 commented 2 years ago

Here's mine:

gvm@gvm21:~$ crontab -l 50 21 /opt/gvm/sbin/greenbone-feed-sync --type SCAP 51 14 /opt/gvm/bin/greenbone-nvt-sync 3 4 /opt/gvm/sbin/greenbone-feed-sync --type CERT 47 0 /opt/gvm/sbin/greenbone-feed-sync --type GVMD_DATA 44 8 * /usr/bin/sudo /opt/gvm/sbin/openvas --update-vt-info

It doesn't look like it should be getting clobbered by any of the other jobs so there may be something else going on.

yu210148 commented 2 years ago

Just so I've got this written down somewhere here's the output I'm getting when I run the update manually:

gvm@gvm21:~$ /opt/gvm/sbin/greenbone-feed-sync --type GVMD_DATA Greenbone community feed server - http://feed.community.greenbone.net/ This service is hosted by Greenbone Networks - http://www.greenbone.net/

All transactions are logged.

If you have any questions, please use the Greenbone community portal. See https://community.greenbone.net for details.

By using this service you agree to our terms and conditions.

Only one sync per time, otherwise the source ip will be temporarily blocked.

receiving incremental file list timestamp 13 100% 12.70kB/s 0:00:00 (xfr#1, to-chk=0/1)

sent 43 bytes received 108 bytes 60.40 bytes/sec total size is 13 speedup is 0.09

yu210148 commented 2 years ago

Well, Here's someone else with this posting on the greenbone forms. The accepted answer there is that the feed isn't updated that often. What's the version of the GVMD_DATA on the one that's working for you?

kev.

yu210148 commented 2 years ago

Kept digging and found that one of the moderators of the greenbone forum confirms that 202201281556 was the current feed version as of March 1st:

https://community.greenbone.net/t/gvmd-data-too-old-34-days-please-check-the-automatic-synchronization-of-your-system/7565/21

marchwicki commented 2 years ago

My second instance must have something else going on with it. In the GUI it was showing a different feed version but also said it was up to date after I ran the 5 feed syncs . I ran your update_gvm.sh script from the repo and now it's showing the same thing as my home instance. My second instance is in a more locked down environment and I am only able to hit the GUI on an old Windows Server VM with an outdated IE browser. I wonder if it was something as simple as a browser cache issue.

yu210148 commented 2 years ago

Humm, I'm not sure either. The update script isn't something I've touched in a long time and it doesn't do anything useful yet. It's more just there as a reminder that it's something the project could use at some point in the future.

I'm going to close this off for now; it sounds like you've got it working as expected. We can reopen it later if we need to.

vrracerx commented 2 years ago

is there no way to do a mock update so that this error clears on a monthly basis? it just bugs me that this looks broken 95% of the time

yu210148 commented 2 years ago

Not from my end that I'm aware of. As far as I know it would have to come from Greenbone in their community feed.

Kev.

On Thu, Apr 21, 2022, 1:01 PM vrracerx @.***> wrote:

is there no way to do a mock update so that this error clears on a monthly basis? it just bugs me that this looks broken 95% of the time

— Reply to this email directly, view it on GitHub https://github.com/yu210148/gvm_install/issues/72#issuecomment-1105473379, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKFY4PMAI3PLDIS5KZGERTVGGCWVANCNFSM5SZ5YAQA . You are receiving this because you modified the open/close state.Message ID: @.***>