I used the official Kali Linux AMI on AWS EC2 and all I did was:
#############
sudo su
apt update -y
apt upgrade -y
apt install gvm net-tools -y
apt autoremove -y
gvm-setup
gvm-check-setup
systemctl enable gsad
reboot
########
I’ve worked with the software all day, did scans, exported pdf report, etc.
I did many iteration of scan/producing reports all day while I was fixing stuff…
Then, I started seeing errors during scan in the interface
**Error while loading Report 4a17aacd-cbfd-40cb-89fd-f9fbe69f5e25** Please try again.
Hide Error Details
### Rejection: An internal error occurred while getting a report. The report could not be delivered. Diagnostics: Failure to receive response from manager daemon.
Error at new _Rejection (https://10.255.0.250/assets/index-Dh8yFcKu.js:69:407308) at https://10.255.0.250/assets/index-Dh8yFcKu.js:69:411037
I tried so many things to try to clean it, that I decided in the end to reinstall everything from scratch.
And now, on my first scan, I get the same error…
Is it possible a new version of something was pushed today that breaks something ?
When I check in /var/log/gvm/gvmd.log, I see a segmentation fault…
What is dmesg saying ? Normally you get more details on dmesg like “illegal instruction”, etc … The kernel ended the task due to any error, you need to find out why.
Hi Lukas, I am experiencing the same issue. I will past the last few mines from dmesg:
460.281684] systemd-sysv-generator[6023]: SysV service ‘/etc/init.d/stunnel4’ lacks a native systemd unit file, automatically generating a unit file for compatibility.
[ 460.281689] systemd-sysv-generator[6023]: Please update package to include a native systemd unit file.
[ 460.281692] systemd-sysv-generator[6023]: ! This compatibility logic is deprecated, expect removal soon. !
[ 460.281714] systemd-sysv-generator[6023]: SysV service ‘/etc/init.d/ptunnel’ lacks a native systemd unit file, automatically generating a unit file for compatibility.
[ 460.281716] systemd-sysv-generator[6023]: Please update package to include a native systemd unit file.
[ 460.281718] systemd-sysv-generator[6023]: ! This compatibility logic is deprecated, expect removal soon. !
[ 460.283464] systemd-sysv-generator[6023]: SysV service ‘/etc/init.d/inetsim’ lacks a native systemd unit file, automatically generating a unit file for compatibility.
[ 460.283466] systemd-sysv-generator[6023]: Please update package to include a native systemd unit file.
[ 460.283468] systemd-sysv-generator[6023]: ! This compatibility logic is deprecated, expect removal soon. !
[ 460.287780] systemd-sysv-generator[6023]: SysV service ‘/etc/init.d/dns2tcp’ lacks a native systemd unit file, automatically generating a unit file for compatibility.
[ 460.287784] systemd-sysv-generator[6023]: Please update package to include a native systemd unit file.
[ 460.287787] systemd-sysv-generator[6023]: ! This compatibility logic is deprecated, expect removal soon. !
This started recently so must be related to a change. FWIW this scanner is running gvmd v24.1.2 and I don’t have the issue on a similar scanner running v24.0.0
If you are able to pinpoint the component and version of that component the problem started it is usually the best to raise an issue for the development team over at the issue tracker of the component question at GitHub:
Otherwise there is no guarantee that such problems are getting noticed.
Your binaries are NOT working and got a Segmentation fault signal.
You need to gdb why does this happens, or you need to try a other platform and installation.
Is there any solution regarding the segmentation fault signal or suggestions I can do on my installation to solve this error?
I’m receiving the same error while loading reports.
As shown in the output there are quite outdated versions (e.g. the gvmd version 24.0.0 was released 5 months ago and is currently at 25.1.3) of the Greenbone Community Edition stack components shipped by / within Kali which is out of the control of Greenbone.
Please keep an eye on the following issue below as a community user had requested an update of the Kali packages from the Kali packaging team a few days ago:
Today I updated gvmd to 25.2.1-1. The error in the report is gone, I can download it, but it is empty, weighs 0 bytes. The old reports are also empty when downloaded
gvm-check-setup 23.11.0
Test completeness and readiness of GVM-23.11.0
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 23.16.1.
OK: Notus Scanner is present in version 22.6.4.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 93690 NVTs.
OK: The notus directory /var/lib/notus/products contains 498 NVTs.
Checking that the obsolete redis database has been removed
Could not connect to Redis at /var/run/redis-openvas/redis-server.sock: No such file or directory
OK: No old Redis DB
Starting ospd-openvas service
Waiting for ospd-openvas service
OK: ospd-openvas service is active.
OK: ospd-OpenVAS is present in version 22.8.2.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 25.2.1.
Step 3: Checking Certificates ...
OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ...
OK: SCAP data found in /var/lib/gvm/scap-data.
OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ...
OK: Postgresql version and default port are OK.
gvmd | _gvm | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
16390|pg-gvm|10|2200|f|22.6||
md main:MESSAGE:2025-04-15 12h48.11 utc:4068: Greenbone Vulnerability Manager version 25.2.1 (DB revision 259)
md manage: INFO:2025-04-15 12h48.11 utc:4068: Getting users.
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version 24.2.3~git.
Step 7: Checking if GVM services are up and running ...
Starting gvmd service
Waiting for gvmd service
OK: gvmd service is active.
Starting gsad service
Waiting for gsad service
OK: gsad service is active.
Step 8: Checking few other requirements...
OK: nmap is present.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.
Step 9: Checking greenbone-security-assistant...
OK: greenbone-security-assistant is installed
It seems like your GVM-23.11.0 installation is OK.