Feed Sync Issues #264
Replies: 9 comments
-
Hi Scott, Can you please help me with command to start the container with sync command |
Beta Was this translation helpful? Give feedback.
-
There are lots of options, but you can find the full docs here:
This should start up and be accessible in a few minutes on port 8080, and ready to scan in under 15 minutes. The default credentials are admin:admin, so make sure you change it right away. -Scott |
Beta Was this translation helpful? Give feedback.
-
Thank you so much, it seems the issue resolved.
Now we can access the openvas.
Regards,
Arunkumar A
From: GE Scott Knauss ***@***.***>
Sent: Friday, March 29, 2024 5:51 PM
To: immauss/openvas ***@***.***>
Cc: Arunkumar Adhipathi ***@***.***>; Comment ***@***.***>
Subject: Re: [immauss/openvas] Feed Sync Issues (Discussion #264)
External Mail. Do not click or open attachments unless you recognize the sender.
There are lots of options, but you can find the full docs here:
https://immauss.github.io/openvas/
OR
For a quick start, without persistent storage and no synchronization:
docker run --detach --publish 8080:9392 -e SKIPSYNC=true --name openvas immauss/openvas
This should start up and be accessible in a few minutes on port 8080, and ready to scan in under 15 minutes. The default credentials are admin:admin, so make sure you change it right away.
…-Scott
-
Reply to this email directly, view it on GitHub<#264 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBHZ7XDNG4FIFT3BETPEDLLY2VFBHAVCNFSM6AAAAABFKRWS3CVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJRGE2DO>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
Disclaimer
This communication is confidential and may be privileged and / or contain copyright material. If you are not the intended recipient of this email, any use, forwarding, printing or reproduction of it or any attachment is prohibited. If you have received this communication in error, please contact us by return email to ***@***.*** and then delete the mail and any attachment. You should check for virus or any harmful components before opening any attachment of this email. The company accepts no liability for any damage caused by any virus transmitted by this email.
? Please consider the environment before printing this email
|
Beta Was this translation helpful? Give feedback.
-
Hi, This issue still be active, right? I cannot restart the existing container as picture below. |
Beta Was this translation helpful? Give feedback.
-
@tpaiii3 -Scott |
Beta Was this translation helpful? Give feedback.
-
This problem is still active as of 7/15/2024, right? Trying to acquire lock on /var/lib/openvas/feed-update.lock ⠇ Downloading NASL files from rsync://feed.community.greenbone.net/community/vulnerability-feed/22.04/vt-data/nasl/ to /var/lib/openvas/plugins Releasing lock on /var/lib/openvas/feed-update.lock Trying to acquire lock on /var/lib/gvm/feed-update.lock ⠇ Downloading CERT-Bund data from rsync://feed.community.greenbone.net/community/vulnerability-feed/22.04/cert-data/ to /var/lib/gvm/cert-data ⠇ Downloading gvmd data from rsync://feed.community.greenbone.net/community/data-feed/22.04/ to /var/lib/gvm/data-objects/gvmd/22.04 Releasing lock on /var/lib/gvm/feed-update.lock |
Beta Was this translation helpful? Give feedback.
-
@juanmachadoathens -Scott |
Beta Was this translation helpful? Give feedback.
-
Hi I’m new to the openvas and I want to fully understand a few things |
Beta Was this translation helpful? Give feedback.
-
@Mxlkommarz |
Beta Was this translation helpful? Give feedback.
-
All,
Please know that there is currently an issue with Greenbone's Feed sync system. This issue cause the initial feed-sync on container start to fail, which causes the container to fail. Until they workout the issue, you can start the contianer using:
-e SKIPSYNC=true
Until they manage to workout their issues, I'll shift my cron to rebuild the image on a daily basis. To keep track of what's going on, you can follow the thread over on their forum:
https://forum.greenbone.net/t/community-feed-connection-reset-by-peer/17136
There is a refresh running now to update the feeds on the public image on docker hub, so it should be up-to-date with the hour.
Thanks,
Scott
Beta Was this translation helpful? Give feedback.
All reactions