after new git pull msfdb error postgresql not in the path

[lacroutelacroute]

Steps to reproduce

after git pull

:~/metasploit-framework$ ./msfdb reinit
Missing requirement: PostgreSQL does not appear to be installed or is not in the environment path

but Nightly build work fine

everything worked very well some time ago

kali rolling up to date
How'd you do it?

1. ...
2. ...

This section should also tell us any relevant information about the
environment; for example, if an exploit that used to work is failing,
tell us the victim operating system and service versions.

Expected behavior

What should happen?

Current behavior

What happens instead?

You might also want to check the last ~1k lines of
/opt/metasploit/apps/pro/engine/config/logs/framework.log or
~/.msf4/logs/framework.log for relevant stack traces

System stuff

Metasploit version

Get this with the version command in msfconsole (or git log -1 --pretty=oneline for a source install).

I installed Metasploit with:

• Kali package via apt
• Omnibus installer (nightly)
• Commercial/Community installer (from http://www.rapid7.com/products/metasploit/download.jsp)
• Source install (please specify ruby version)

OS

What OS are you running Metasploit on?

[mkienow-r7]

If I understand correctly you are attempting to use msfdb from a source install ("after git pull"). The nightly installer build is currently from the 4.x branch, while the master branch is 5.x. In addition, the nightly installer build packages its own copy of PostgreSQL which it adds to the path dynamically.

If you would like to use the source from GitHub I would suggest reviewing the wiki on Setting Up a Metasploit Development Environment. Depending on your current setup, you may only need to install PostgreSQL on your system to get up and running.

[lacroutelacroute]

./msfdb not work but ./msfconsole work fine correct postgresql connexion Le 13/11/2018 à 20:50, Matthew Kienow a écrit :

…

If I understand correctly you are attempting to use |msfdb| from a source install ("after git pull"). The nightly installer build is the 4.x branch, while the master branch is 5.x. In addition, the nightly installer build packages its own copy of PostgreSQL which it adds to the path dynamically. If you would like to use the source from GitHub I would suggest reviewing the wiki on Setting Up a Metasploit Development Environment <https://github.com/rapid7/metasploit-framework/wiki/Setting-Up-a-Metasploit-Development-Environment>. Depending on your current setup, you may only need to install PostgreSQL on your system to get up and running. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10939 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWVcF8glOCUu7phRzJIkRXJP3SqCi-QVks5uuyKEgaJpZM4YWxn->.

[mkienow-r7]

The reason you are getting the message "PostgreSQL does not appear to be installed or is not in the environment path" from msfdb is one or more of the following commands is not found on in your path: psql, pg_ctl, initdb, createdb. ./msfconsole can start and work without a database. Are you certain the ./msfconsole from the repo is connected to a database?

Would you provide the output from the following commands:

1. From your terminal: postgresql_cmds=( psql pg_ctl initdb createdb ); for i in "${postgresql_cmds[@]}"; do which $i; done
2. From inside ./msfconsole: db_status and db_connect -l

[lacroutelacroute]

terminal :~$ postgresql_cmds=( psql pg_ctl initdb createdb ); for i in "${postgresql_cmds[@]}"; do which $i; done /usr/bin/psql /usr/bin/createdb inside ./msfconsole msf5 > db_status [*] Connected to msf. Connection type: postgresql. msf5 > db_connect -l Data Services ============= current name url default? ------- ---- --- -------- msf5 > Le 13/11/2018 à 22:13, Matthew Kienow a écrit :

…

The reason you are getting the message "PostgreSQL does not appear to be installed or is not in the environment path" from |msfdb | is one or more of the following commands is not found on in your path: |psql|, |pg_ctl|, |initdb|, |createdb|. |./msfconsole| can start and work without a database. Are you certain the |./msfconsole| from the repo is connected to a database? Would you provide the output from the following commands: 1. From your terminal: |postgresql_cmds=( psql pg_ctl initdb createdb ); for i in "${postgresql_cmds[@]}"; do which $i; done| 2. From inside |./msfconsole|: |db_status| and |db_connect -l| 3. From — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10939 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWVcFwYcVcSRnIZhfyLPLtclMXKBkPldks5uuzYLgaJpZM4YWxn->.

[mkienow-r7]

I'm not familiar with how Kali handles their PostgreSQL installation, but the reason msfdb is not working as you expect is because a few PostgreSQL binaries used by msfdb are not found in your path. Do the following files exist: /usr/bin/pg_ctl and /usr/bin/initdb? If so, ensure they are a part of your path and msfdb should start as expected.

[rhertzog]

Debian (and thus Ubuntu and Kali as well) do not provide pg_ctl and initdb in the default PATH. Those binaries are only available in the versioned directories /usr/lib/postgresql/XX (eg /usr/lib/postgresql/11 for PostgreSQL 11).

See #11369 for my request to better handle this case.

[mkienow-r7]

@rhertzog I agree having looked into this further since this issue was opened. We have a ticket on our backlog to address using the postgresql-common package included in Debian / Kali. Closing this issue.