problem with setting up the metasploit database correctly.

[G0DS3RA]

after launching metasploit for the first time and using it i saw that the db was not usable after trying the "vulns" command. after verification on forums i can't find any solution. when i do "msfdb init" everything is set automatically and it tell me "Overridding user environment variable 'OPENSSL_CONF' to enable legacy functions." then when i do db_status it tells me that postgresql is selected but there is no connection. same after i try the "db start" command. help me

[gwillcox-r7]

There is a lack of information here. Specifically you haven't told us what OS you are using and what steps you have taken and their order, as well as what version of PostgreSQL you are trying to use for testing and the version of Metasploit that you are using. Please provide this information you we can better assist you.

You can run db_connect from within the console after you have started Metasploit to attempt to connect to a PostgreSQL database after Metasploit has started. Have you tried this, and if so, did you encounter any issues?

[G0DS3RA]

i'm on kali linux, vmware version. i already tried that command with the user:pass that was in the database.yml file. after restarting postgresql and doing the db init, the db_status command tells me that it is connected to msf with postgresql. but when i try to use db_nmap it tells me that the database is not connected, and sometimes the scan works but it is when i try the vulns command that it tells me again that the database isn't connected.

[gwillcox-r7]

Going to need to see console output or pictures of the steps you have taken to root cause this further. Unfortunately its not possible to reproduce the issue given the information you have sent over so far. The database is notoriously a fiddly bit of software to debug when it goes awry so this is why I really need to see this level of detail in order to determine what is potentially missing.

[github-actions[bot]]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[gwillcox-r7]

Closing issue due to lack of info provided. If more information is provided I can reopen this issue.