I have a scan running for some time, but every time when it reaches 70%, the scan is stopped by a automatic feed sync. Is there a way, that I can schedule this feed sync? It starts like, every 1 hour, stopping the scan, and it can’t be resumed. I tried on a fresh new install in Kali purple with community edition and with greenbone ova free edition.
The versions are: Greenbone OS 24.10.6 and Version 26.17.0 for Kali purple.
On the Greenbone OS, I found an option to disable sync, but even using this option it syncs on the start. But the problem on scans, aparently are resolved on the Greenbone OS.
The problem continues on Kali purple, because I can’t find a similar option.
But what I truly want to achieve is to schedule the sync, so the scans can continue, and I don’t need to interrupt the actualization. Can you please help me to achieve that? Is there a way?
@gperes I assume that it runs feed via systemd timers on kali. ask more help from copilot or chatgpt.
Just disable them. you need the feedsync manually before scans
Eero
I have seen all the schedule forms, but it doesn’t have anything schedule. I think that is something on the app. I tried chatgpt, gemini, copilot but none of them have more ideas, they enter on a loop trying to resolve the problem.
After reviewing the setup, I’m confident that Greenbone on Kali doesn’t perform any automatic sync. Make sure the system has enough memory available (16 GB) — if it crashes, it will reload the NVTs. As an extra precaution, you can also rename the Greenbone‑sync scripts.
Eero
This is the problem I didn’t find anything about this schedule, but still it stops the scan, the machine have enough memory, because it was doing the scans, but on last friday, after the update from the last sync started this behavior. I installed on the kali VM on monday and the behavior repeated itself, without any schedules made by me. I really don’t understand what happened. I really prefer the manual updates.
I’m certain that one of your OpenVAS components is crashing, restarting, and reloading the NVTs. Add more memory and make sure you have sufficient swap. The Kali packages are also quite old. Check the kernel logs (dmesg) to see if there are any indications of processes crashing. As a last resort, you could manually compile the latest version (I have scripts for that myself).
Eero
I remember seeing this exact issue once, and it happened in my development environment where I only had 8 GB of RAM. One of the components — I think it was ospd or whatever it was called — kept crashing and then reloading all the NVTs again.
Eero
Can you send me the scripts to compile? I will try and post the results. Thanks in advance!
I can send you the scripts you need to compile a newer version, but before that, please make sure your machine or virtual machine meets at least the following specs: 16 GB RAM, 4 (v)CPU cores, and either an SSD or RAID 10 if you’re using mechanical drives (SSD strongly recommended for performance).
Eero
that´s the configuration of the kali that I have
This repository is a fork of: https://github.com/Kastervo/OpenVAS-Installation.
I forked the original project and addressed several shortcomings, including adding support for Debian 13 and Kali Linux.
For Kali Linux, a minimal installation is strongly recommended to avoid package conflicts, particularly with the distribution’s preinstalled GVM packages.
The script builds the latest version directly from GitHub. Keep in mind that “latest” does not necessarily mean “stable”—it simply means newer.
Have fun testing it! And if it somehow ends up eating your last sandwich… well, you were warned in advance. 
My script temporary source: #!/bin/bash# OpenVAS installation script for Debian 13+ and Kali systems, fo - Pastebin.com
Eero
Thanks, I will test and post the results later.
Don’t forget to become root with sudo -i or su -. If you skip that, the root environment won’t be applied and things will go sideways fast.
Eero
@gperes So, did that resolved your issue?
Still trying to install with the script, I received a lot of errors, I’m using AI to try to resolve.
@gperes please send output via private message
Eero
I ran a quick test with Kali Linux Purple, and it works smoothly once you disable the Elastic repository. Kali Linux and Kali Linux Purple are nearly identical, with only small package differences. Just be aware that if you hit the GitHub API too frequently, it will eventually throttle or temporarily block your IP. I installed Kali using the minimal setup with only the XFCE desktop environment.
Eero