Error while loading Report

Linux Distribution and External Repo Discussion
1

Hi,

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…

event task:MESSAGE:2024-12-09 03h46.33 utc:1352: Status of task Internal Penetration Test (e8c02d38-f952-4893-b67b-4b2517af173c) has changed to Running
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0x6e915) [0x55f7b21cd915]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x3fd20) [0x7fcf4a20fd20]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_utf8_validate+0x10) [0x7fcf4a53e150]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (strescape_check_utf8+0x1c) [0x55f7b2274b6c]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (get_certificate_info+0x532) [0x55f7b21d68d2]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0x8b944) [0x55f7b21ea944]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0xd6e81) [0x55f7b2235e81]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (manage_send_report+0x275) [0x55f7b2241be5]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0x135075) [0x55f7b2294075]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x60ad2) [0x7fcf4a505ad2]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_markup_parse_context_parse+0xc12) [0x7fcf4a5067d2]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (process_gmp_client_input+0x4f) [0x55f7b22aca3f]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (serve_gmp+0x3fc) [0x55f7b21d201c]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0x6eb21) [0x55f7b21cdb21]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (+0x6f201) [0x55f7b21ce201]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (gvmd+0x1c13) [0x55f7b21d1213]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x29d68) [0x7fcf4a1f9d68]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fcf4a1f9e25]
md   main:MESSAGE:2024-12-09 05h27.55 utc:97923: BACKTRACE: gvmd: Serving (_start+0x21) [0x55f7b21cd791]
md manage:MESSAGE:2024-12-09 05h27.55 utc:97923: Received Segmentation fault signal

Anyone knows how to fix this ?

Thanks in advance

2

Anyone has an idea ? Otherwise, is there a better place to ask ?

Considering this is a clean install on an official image with no modification, I can’t believe I’m the only one having this issue ??

3

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.

4

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. !

5

That is not complete related to GVM, you need to silence the dmesg noise first before you get any meaningful logs.

6

I am experiencing the same issue. There is nothing in my dmesg output related to killing of any processes…

md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0x6e974) [0x5c04aa47a974]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x74ee67cf3050]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_utf8_validate+0xc) [0x74ee67ffd22c]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(strescape_check_utf8+0x1a) [0x5c04aa51344a]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(get_certificate_info+0x4f2) [0x5c04aa483412]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0x8b314) [0x5c04aa497314]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0xcb102) [0x5c04aa4d7102]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(manage_send_report+0x25d) [0x5c04aa4e0a1d]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0x126606) [0x5c04aa532606]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x57fa2) [0x74ee67fcafa2]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_markup_parse_context_parse+0xc22) [0x74ee67fcbcc2]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(process_gmp_client_input+0x4b) [0x5c04aa54a29b]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(serve_gmp+0x41c) [0x5c04aa47ef5c]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0x6eb83) [0x5c04aa47ab83]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(+0x6f231) [0x5c04aa47b231]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(gvmd+0x1b4f) [0x5c04aa47e16f]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x74ee67cde24a]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x74ee67cde305]
md   main:MESSAGE:2025-01-07 14h02.32 utc:2661: BACKTRACE: gvmd(_start+0x21) [0x5c04aa47a7f1]
md manage:MESSAGE:2025-01-07 14h02.32 utc:2661: Received Segmentation fault signal

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

Working:

gvmd=v24.0.0
gvm_libs=v22.14.0
openvas=v23.9.0
openvas_smb=v22.5.6
notus_scanner=v22.6.4
gsa=v24.0.1
gsad=v24.0.0
ospd=v21.4.4
ospd_openvas=v22.7.1
pg_gvm=v22.6.5
python_gvm=v24.8.0
gvm_tools=v24.8.0
greenbone_feed_sync=v24.9.0

Not working:

gvmd=v24.1.2
gvm_libs=v22.15.0
openvas=v23.13.2
openvas_smb=v22.5.6
notus_scanner=v22.6.5
gsa=v24.1.0
gsad=v24.1.0
ospd=v21.4.4
ospd_openvas=v22.7.1
pg_gvm=v22.6.6
python_gvm=v24.12.0
gvm_tools=v24.12.1
greenbone_feed_sync=v24.9.0

7

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.

8

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.

1 Like