View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009490Kali LinuxKali Package Bugpublic2026-01-09 18:472026-02-06 21:46
Reporterbackrow Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0009490: Since 12/22, gvmd contuously updating never finishes
Description

Since a Kali update on 12/22/25, the gvmd program on kali continuously updates, never finishing to allow a scan

Log (attached) contains
sql_exec_internal: PQexec failed: ERROR: schema "scap3" already exists
(7)md manage:WARNING:2026-01-09 18h36.53 utc:513849: sql_exec_internal: SQL: ALTER SCHEMA scap RENAME TO scap3;
md manage:WARNING:2026-01-09 18h36.53 utc:513849: sqlv: sql_exec_internal failed

Following this there is a backtrace and update starts again.

Please help!

Attached Files
ex.txt (2,262 bytes)    
manage:   INFO:2026-01-09 18h36.19 utc:513849: Updating placeholder CPEs
md manage:WARNING:2026-01-09 18h36.53 utc:513849: sql_exec_internal: PQexec failed: ERROR:  schema "scap3" already exists
 (7)
md manage:WARNING:2026-01-09 18h36.53 utc:513849: sql_exec_internal: SQL: ALTER SCHEMA scap RENAME TO scap3;
md manage:WARNING:2026-01-09 18h36.53 utc:513849: sqlv: sql_exec_internal failed
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x13e5b9) [0x556f442695b9]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(+0x40590) [0x7f5687040590]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(+0x9569c) [0x7f568709569c]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x12) [0x7f5687040462]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(abort+0x22) [0x7f56870284ac]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x58a29) [0x556f44183a29]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x11b0be) [0x556f442460be]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x122d9f) [0x556f4424dd9f]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x125cf9) [0x556f44250cf9]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0xa3636) [0x556f441ce636]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x13f1fb) [0x556f4426a1fb]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x141cdf) [0x556f4426ccdf]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(+0x29f68) [0x7f5687029f68]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: /usr/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f568702a025]
md   main:MESSAGE:2026-01-09 18h36.53 utc:513849: BACKTRACE: gvmd: Syncing (+0x58a91) [0x556f44183a91]
md manage:MESSAGE:2026-01-09 18h36.53 utc:513849: Received Aborted signal
md manage:   INFO:2026-01-09 18h36.53 utc:513844: Assigning EPSS scores to VTs
ex.txt (2,262 bytes)   

Activities

backrow

backrow

2026-01-09 18:59

reporter   ~0021216

Baremetal, 64GB mem, root+92G, var=234G, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz
backrow

backrow

2026-01-30 21:04

reporter   ~0021305

Feed never finishes updating. Please help!
kali-bugreport

kali-bugreport

2026-01-31 08:40

reporter   ~0021306

Last edited: 2026-02-02 17:21

https://pkg.kali.org/pkg/gvmd (26.13.0) vs. https://github.com/greenbone/gvmd/releases/ (26.15.0) maybe requires an update?
sbrun

sbrun

2026-02-06 11:19

manager   ~0021315

I don't reproduce the issue.
Did you run gvm-check-setup?
backrow

backrow

2026-02-06 14:57

reporter   ~0021316

Thank you. I run gvm-check-setup after every gvm-related update:

gvm-check-setup 25.04.0
This script is provided and maintained by Debian and Kali.
Test completeness and readiness of GVM-25.04.0
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 23.38.0.
OK: Notus Scanner is present in version 22.7.2.
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 95080 NVTs.
OK: The notus directory /var/lib/notus/products contains 512 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-openvas service is active.
OK: ospd-OpenVAS is present in version 22.10.0.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 26.15.0.
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||
: INFO:2026-02-06 14h56.19 utc:965372: Getting users.
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version Deamon 24.12.2~git.
Step 7: Checking if GVM services are up and running ...
OK: gvmd service is active.
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-25.04.0 installation is OK.
backrow

backrow

2026-02-06 21:46

reporter   ~0021317

I just did a fresh install, I will let you know if I can reproduce

Issue History

Date Modified Username Field Change
2026-01-09 18:47 backrow New Issue
2026-01-09 18:47 backrow File Added: ex.txt
2026-01-09 18:59 backrow Note Added: 0021216
2026-01-30 21:04 backrow Note Added: 0021305
2026-01-31 08:40 kali-bugreport Note Added: 0021306
2026-02-02 09:08 daniruiz Assigned To => sbrun
2026-02-02 09:08 daniruiz Status new => assigned
2026-02-02 17:21 kali-bugreport Note Edited: 0021306
2026-02-06 11:19 sbrun Status assigned => feedback
2026-02-06 11:19 sbrun Note Added: 0021315
2026-02-06 14:57 backrow Note Added: 0021316
2026-02-06 14:57 backrow Status feedback => assigned
2026-02-06 21:46 backrow Note Added: 0021317