View Issue Details

IDProjectCategoryView StatusLast Update
0008961Kali LinuxKali Package Bugpublic2024-10-21 10:11
Reportermajhealth Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Fixed in Version2024.4 
Summary0008961: GVM-SETUP fails with Creating Database Error
Description

During the initial install of OpenVas/GVM on a new kali VM as of 10/15/24 I receive the following error regarding the package install.

createdb: error: database creation failed: ERROR: template database "template1" has a collation version mismatch
Detail: The template database was created using collation version 2.38, but the operating system provides version 2.40.
Hint: Rebuild all objects in the template database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Activities

kali-bugreport

kali-bugreport

2024-10-16 15:03

reporter   ~0019931

Isn't the message already stating what to do? Otherwise probably better for PostgreSQL support.

majhealth

majhealth

2024-10-16 15:11

reporter   ~0019932

Last edited: 2024-10-16 16:02

The message does state how to resolved, but please take note it isnt talking about my active database. it is talking about the template housed within your repo install package. I submitted this so that the repo could be updated with a fresh template that works out of the box.

This is a fresh attempt on a brand new VM and Install of GVM.

majhealth

majhealth

2024-10-16 16:04

reporter   ~0019933

kali-bugreport

kali-bugreport

2024-10-16 16:19

reporter   ~0019934

Not my repo, not my template and probably also not a template of Kali :-)

majhealth

majhealth

2024-10-16 17:26

reporter   ~0019935

Understood, Hopefully it is someone else's here as GVM points people from their site directly here to report bugs.

See this link or the attached screenshot:
https://greenbone.github.io/docs/latest/22.4/kali/index.html#

kali-bugreport

kali-bugreport

2024-10-16 19:43

reporter   ~0019936

That seems be valid for the installation of that GVM software, but issue here is about the PostgreSQL database packages which are probably getting pulled directly from Debian by Kali.

sbrun

sbrun

2024-10-17 08:07

manager   ~0019940

Thanks for the report. I'm currently working on the update of the GVM packages and I identified this issue.
I will let you know when the fix is available in kali-rolling

sbrun

sbrun

2024-10-18 08:18

manager   ~0019943

All the updated packages are now in kali-rolling. Please update and let us know if you have any issue

majhealth

majhealth

2024-10-19 16:16

reporter   ~0019947

Last edited: 2024-10-20 18:04

I was able to go back in and upgrade PG to 17 and then run the GVM setup. It all went flawless. I am now running my first vuln scans. Thanks!

Issue History

Date Modified Username Field Change
2024-10-16 13:13 majhealth New Issue
2024-10-16 15:03 kali-bugreport Note Added: 0019931
2024-10-16 15:11 majhealth Note Added: 0019932
2024-10-16 16:02 majhealth Note Edited: 0019932
2024-10-16 16:04 majhealth Note Added: 0019933
2024-10-16 16:04 majhealth File Added: Screenshot 2024-10-16 120437.png
2024-10-16 16:19 kali-bugreport Note Added: 0019934
2024-10-16 17:26 majhealth Note Added: 0019935
2024-10-16 17:26 majhealth File Added: Screenshot 2024-10-16 132345.png
2024-10-16 19:43 kali-bugreport Note Added: 0019936
2024-10-17 08:01 sbrun Assigned To => sbrun
2024-10-17 08:01 sbrun Status new => assigned
2024-10-17 08:07 sbrun Note Added: 0019940
2024-10-18 08:18 sbrun Note Added: 0019943
2024-10-19 16:16 majhealth Note Added: 0019947
2024-10-20 18:04 majhealth Note Edited: 0019947
2024-10-21 10:11 sbrun Status assigned => resolved
2024-10-21 10:11 sbrun Resolution open => fixed
2024-10-21 10:11 sbrun Fixed in Version => 2024.4