View Issue Details

IDProjectCategoryView StatusLast Update
0008549Kali LinuxKali Package Bugpublic2024-01-18 08:29
Reporterabu79 Assigned Tosteev  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0008549: due to package issue on kali 6.5.0-kali3-amd64 can't install openvas
Description

ERROR: extension “pg-gvm” is not available
DETAIL: Could not open extension control file “/usr/share/postgresql/16/extension/pg-gvm.control”: No such file or directory.

Activities

steev

steev

2023-12-04 01:18

manager   ~0018667

Can you give the full output please? The command you're running, why you think it's the kernel?

abu79

abu79

2023-12-04 03:03

reporter   ~0018668

.I run the command "gvm-check-setup" and got the following Error:

ERROR: The new extension pgcrypto does not exist for gvmd database
FIX: Run 'sudo runuser -u postgres -- /usr/share/gvm/create-postgresql-database'

Then i run the command 'runuser -u postgres -- /usr/share/gvm/create-postgresql-database''
and got the following error:

ERROR: extension "pg-gvm" is not available
DETAIL: Could not open extension control file "/usr/share/postgresql/16/extension/pg-gvm.control": No such file or directory
HINT: The extension must first be installed on the system where PostgreSQL is running

steev

steev

2023-12-04 19:59

manager   ~0018670

Last edited: 2023-12-04 20:00

Did you upgrade your postgresql cluster to 16 like the instructions said to when the update came in?

sudo pg_dropcluster 16 main --stop
sudo pg_upgradecluster 15 main

?

abu79

abu79

2023-12-05 01:15

reporter   ~0018671

yes, i did that.

DS7

DS7

2023-12-06 16:47

reporter   ~0018672

Hi, same issue here. Any updates or workarounds? Thanks

abu79

abu79

2023-12-06 16:57

reporter   ~0018673

Hello, Same issue, Still not working.May i expect a solution soon?

DS7

DS7

2023-12-07 14:07

reporter   ~0018694

Hi, I got it working by uninstalling pg 16 and updating pg 15, setting version 15 under /usr/share/gvmd/postgresql-version, a few reboots in between and voila, it works :). I will try to exactly reproduce and document the steps on another identical machine that had the same problem.

DS7

DS7

2023-12-07 14:57

reporter   ~0018695

Hi, as promised, the issue was resolved on the second machine and the steps I followed are:

Check pg Version
sudo cat /usr/share/gvmd/postgresql-version

Check pg listening on port 5342
pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }'

Check cluster online
sudo pg_lsclusters

Stop pg16
sudo pg_dropcluster 16 main --stop

Check cluster online
sudo pg_lsclusters

Start pg 15
sudo pg_ctlcluster 15 main restart

Check cluster online
sudo pg_lsclusters

Set pg version 15 under:
sudo vim /usr/share/gvmd/postgresql-version

Check pg Status
sudo systemctl status postgresql

Change pg 15 listening port under:
sudo vi /etc/postgresql/15/main/postgresql.conf

Restart pg
sudo systemctl restart postgresql

Check listening port
pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }'

Start gvm setup
sudo gvm-setup

Some of the steps with the inbetween checks can be skipped :)

abu79

abu79

2023-12-07 15:07

reporter   ~0018696

Dear Concern,
Thank you very much for resolving the proble.Please can you make sure one thing i,e do i need to keep pg15 or i need to upgrade it to pg16.
Regards
Abu Sufian Sharif

kali-bugreport

kali-bugreport

2023-12-08 07:24

reporter   ~0018697

Don't stick/use the pg 15 package. These usually are not getting updates anymore which poses a security risk to your system.

steev

steev

2023-12-27 05:08

manager   ~0018756

This sounds like postgresql 16 was installed, and 15 wasn't updated properly. I was able to get the initial message of "The default PostgreSQL version (15) is not 16 that is required by libgvmd" and then ran sudo pg_dropcluster 16 main -stop and then sudo pg_upgradecluster 15 main and as soon as I did, sudo gvm-setup worked. Are you absolutely sure that you actually ran those two commands like you said you did? Because it sounds like you didn't if you're still trying to use postgresql 15.

kocurc

kocurc

2024-01-14 22:43

reporter   ~0018787

Hi steev,
I had the same problem. It was solved with your steps.

Issue History

Date Modified Username Field Change
2023-12-03 23:13 abu79 New Issue
2023-12-04 01:18 steev Note Added: 0018667
2023-12-04 03:03 abu79 Note Added: 0018668
2023-12-04 19:59 steev Note Added: 0018670
2023-12-04 20:00 steev Note Edited: 0018670
2023-12-05 01:15 abu79 Note Added: 0018671
2023-12-06 16:47 DS7 Note Added: 0018672
2023-12-06 16:57 abu79 Note Added: 0018673
2023-12-07 14:07 DS7 Note Added: 0018694
2023-12-07 14:57 DS7 Note Added: 0018695
2023-12-07 15:07 abu79 Note Added: 0018696
2023-12-08 07:24 kali-bugreport Note Added: 0018697
2023-12-27 05:08 steev Note Added: 0018756
2024-01-14 22:43 kocurc Note Added: 0018787
2024-01-18 08:29 daniruiz Assigned To => steev
2024-01-18 08:29 daniruiz Status new => assigned