0008145: Metasploit and PostgreSQL doesn't work on Kali Linux properly - Kali Linux Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0008145	Kali Linux	General Bug	public	2023-01-14 14:01	2023-08-25 16:20

Reporter	SkullZ_	Assigned To
Priority	normal	Severity	block	Reproducibility	always
Status	closed	Resolution	open
Product Version	2022.4

Summary	0008145: Metasploit and PostgreSQL doesn't work on Kali Linux properly
Description	Hi Guys, Another issue on Kali Linux I found lately. Metasploit + PosgreSQL doesnt work. I try the configuration according to your manual: https://www.offensive-security.com/metasploit-unleashed/using-databases/ And it doesn't work. What's more it breaks the Metaspolout + PostgreSQL permanently. msfconsole is "f...ed" after the first two lines from your manual on Kali Linux and Metasploit doesn't work at all now. Screens attached. Kali Linux version is 5.15.0-kali3-amd64, SMP Debian 5.15.15-2kali1 (2022-01-31_ x86_64. I could update it to the higher version the problem is the higher version of Kali Linux like 2022.4 (kernel 6) doesn't work at all itself as an OS with GUI GNOME - what I reported previously. The only fix I found is to remove the Kali Linux completely (purge the whole VM with all settings) and build a new VM from the scratch or what I did next take a checkpoint/snapshot of the VM and revert the VM back to the state from using Kali Linux Metasploit + Postgres manual (https://www.offensive-security.com/metasploit-unleashed/using-databases/) and just run Metasploit without PostgreSQL. Any idea if there is some fix for that?
Steps To Reproduce	systemctl start postgresql msfdb init
Additional Information	Additionally I get an error on system start as in the attachment. Sorry I cannot add any text logs but it's Linux not Windows so copy from the screen as a text to the clipboard doesn't work. That is why I put screenshots.

SkullZ_ 2023-01-14 14:01 reporter	20230114 kali metasploit postgre error.JPG (114,296 bytes) 20230114 kali metasploit postgre error.JPG (114,296 bytes) 20230114 kali metasploit postgre error2.JPG (99,553 bytes) 20230114 kali metasploit postgre error2.JPG (99,553 bytes) 20230114 kali metasploit postgre error3.JPG (122,562 bytes) 20230114 kali metasploit postgre error3.JPG (122,562 bytes) 20230114 kali metasploit postgre error3-2.JPG (122,562 bytes) 20230114 kali metasploit postgre error3-2.JPG (122,562 bytes) 20230114 kali metasploit postgre error4.JPG (93,295 bytes) 20230114 kali metasploit postgre error4.JPG (93,295 bytes) 20230114 kali start error.png (17,981 bytes) 20230114 kali start error.png (17,981 bytes)

kali-bugreport 2023-01-15 07:01 reporter ~0017397	Probably just a bug in either Metasploit or the db ruby gem. Could be reported upstream or already fixend in newer upstream packages shipped in newer Kali releases.

g0tmi1k 2023-08-25 16:20 administrator ~0018389	This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

Date Modified	Username	Field	Change
2023-01-14 14:01	SkullZ_	New Issue
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali metasploit postgre error.JPG
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali metasploit postgre error2.JPG
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali metasploit postgre error3.JPG
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali metasploit postgre error3-2.JPG
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali metasploit postgre error4.JPG
2023-01-14 14:01	SkullZ_	File Added: 20230114 kali start error.png
2023-01-15 07:01	kali-bugreport	Note Added: 0017397
2023-08-25 16:20	g0tmi1k	Note Added: 0018389
2023-08-25 16:20	g0tmi1k	Status	new => closed