Fast-track can not connect to database after updating

[nedgb]

i have the feeling i am the only one with that problem. fast-track works great after a fresh install of backtrack but when i update my system it suddenly stops working and gives me the following error - Database not connected. Here is the output -

=[ metasploit v3.4.1-dev [core:3.4 api:1.0]
+ -- --=[ 556 exploits - 267 auxiliary
+ -- --=[ 209 payloads - 23 encoders - 8 nops
=[ svn r9452 updated today (2010.06.08)

msf > db_destroy pentest
dropdb: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
msf > db_create pentest
[-]
[-] Warning: The db_create command is deprecated, use db_connect instead.
[-] The database and schema will be created automatically by
[-] db_connect. If db_connect fails to create the database, create
[-] it manually with your DBMS's administration tools.
[-]
createdb: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
[-] Error while running command db_create: Failed to connect to the database: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?


Call stack:
/pentest/exploits/framework3/lib/msf/ui/console/command_dispatcher/db.rb:1670:in `db_create_postgresql'
/pentest/exploits/framework3/lib/msf/ui/console/command_dispatcher/db.rb:1222:in `send'
/pentest/exploits/framework3/lib/msf/ui/console/command_dispatcher/db.rb:1222:in `cmd_db_create'
/pentest/exploits/framework3/lib/rex/ui/text/dispatcher_shell.rb:246:in `send'
/pentest/exploits/framework3/lib/rex/ui/text/dispatcher_shell.rb:246:in `run_command'
/pentest/exploits/framework3/lib/rex/ui/text/dispatcher_shell.rb:208:in `run_single'
/pentest/exploits/framework3/lib/rex/ui/text/dispatcher_shell.rb:202:in `each'
/pentest/exploits/framework3/lib/rex/ui/text/dispatcher_shell.rb:202:in `run_single'
/pentest/exploits/framework3/lib/rex/ui/text/shell.rb:141:in `run'
/pentest/exploits/framework3/msfconsole:112
msf > db_nmap 192.168.0.101
[-] Database not connected
msf > db_autopwn -p -t -e -r
[-] Database not connected
msf > sleep 5
msf > jobs -K
Stopping all jobs...
msf >
msf >
msf >
msf >
msf > sessions -l

Active sessions
===============

No active sessions.


I searched the forums for a solution but could not find one.

[pigtail23]

use sqlite3 as db_driver or search for the howto pgsql thread from sickness.

[ding444]

I'm having the same issue. I've tried updating several different packages many different times with the same result. Can anybody advise?

There seems to be a problem where a server.crt file is preventing postgresql from launching properly.

Try editing the conf file and disabling SSL

nano /etc/postgresql/8.3/main/postgresql.conf

and comment out the following line:

#ssl = true

Then restart postgresql and poof - a temporary workaround.

/etc/init.d/postresql restart

[bigbadlou]

I too, have this same issue. I have looked and looked all over google and elsewhere....no luck
I hope that this was not already addressed, and we missed out on the fix?
If so could someone please post a link.

I know that the newer version will break the process, but how to get the old one back?

Oh Wise Gods of BT, please shine your light of wisdom on this matter.

[randomut]

Same problem here..... running BT4 persistent from usb drive
after a major update via fast-track, postgresql fails to start

i tried ding444's method of disabling SSL but that didnt work either
this is my console output after the restart of postgre

Restarting PostgreSQL 8.3 database server: main*
The PostgreSQL server failed to start. Please check the log output:
2010-06-19 21:30:54 EDT FATAL: could no t create lock file "/var/run/postgresql/ .s.PGSQL.5432.lock": No such file or directory

help plz, i really dont wanna re-do another persistent usb install

lol what a dumbass I am, pigtail23 had the right idea by changing the db_driver.. works great now, and to those that dont know how to change the driver its easy...
console output:

msf > db_driver sqlite3[*] Using database driver sqlite3
msf > db_destroy pentest[*] Deleting pentest...
[-] The specified database does not exist
msf > db_create pentest
[-]
[-] Warning: The db_create command is deprecated, use db_connect instead.
[-] The database and schema will be created automatically by
[-] db_connect. If db_connect fails to create the database, create
[-] it manually with your DBMS's administration tools.
[-][*] Creating a new database instance...[*] Successfully connected to the database[*] File: pentest

[mdlheur]

I have the same problem as the first note. It worked fine after fresh install, then when I updated and ran an nmap, it went downhill from there.

msf > db_create test1
[-]
[-] Warning: The db_create command is deprecated, use db_connect instead.
[-] The database and schema will be created automatically by
[-] db_connect. If db_connect fails to create the database, create
[-] it manually with your DBMS's administration tools.
[-]
createdb: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
[-] Error while running command db_create: Failed to connect to the database: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?


Call stack:
/opt/metasploit3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1684:in `db_create_postgresql'
/opt/metasploit3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1236:in `send'
/opt/metasploit3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1236:in `cmd_db_create'
/opt/metasploit3/msf3/lib/rex/ui/text/dispatcher_shell.rb:246:in `send'
/opt/metasploit3/msf3/lib/rex/ui/text/dispatcher_shell.rb:246:in `run_command'
/opt/metasploit3/msf3/lib/rex/ui/text/dispatcher_shell.rb:208:in `run_single'
/opt/metasploit3/msf3/lib/rex/ui/text/dispatcher_shell.rb:202:in `each'
/opt/metasploit3/msf3/lib/rex/ui/text/dispatcher_shell.rb:202:in `run_single'
/opt/metasploit3/msf3/lib/rex/ui/text/shell.rb:141:in `run'
./msfconsole:112

[mdlheur]

If you haven't found the fix, here it is. mezo36 noted it on another thread:

msf> db_driver sqlite3

[sickness]

Omg read your errors next time it clearly sais postgreSQL, and I've made a tutorial on how to make postgreSQL work.

createdb: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
[-] Error while running command db_create: Failed to connect to the database: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?

[Archangel-Amael]

Not a BT bug.
Moved.
I don't believe rel1k even maintains or updates fasttrack any more.

[jibi1705]

Omg read your errors next time it clearly sais postgreSQL, and I've made a tutorial on how to make postgreSQL work.

createdb: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
[-] Error while running command db_create: Failed to connect to the database: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?

can u plz paste ur totorial url here abt how to make postgresql!! im new to the form n need time to understand its where abouts !!