Hello mate,
To work around it I simply changed one setting in /etc/postgresql/8.3/main/postgresql.conf:
ssl = true
I changed to:
ssl = false
That is it!
I just put a fresh install of Backtrack 4 on my computer and after updating everything I got an error. To test if this was due to me updating fast track I ran another install and did not update the sql section.
still the same result.
Any way I can solve this? Backtrack run perfectly fine in the past.
Output:
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:1613:in `db_create_postgresql'
/pentest/exploits/framework3/lib/msf/ui/console/command_dispatcher/db.rb:1165:in `send'
/pentest/exploits/framework3/lib/msf/ui/console/command_dispatcher/db.rb:1165: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:97
msf > db_nmap 192.168.1.18
[-] Unknown command: db_nmap.
msf > db_autopwn -p -t -e -r
[-] Unknown command: db_autopwn.
msf > sleep 5
msf > jobs -K
Stopping all jobs...
msf >
msf >
msf >
msf >
msf > sessions -l
Active sessions
===============
No active sessions.
msf > echo "If it states No sessions, then you were unsuccessful. Simply type sessions -i <id> to jump into a shell"[*] exec: echo "If it states No sessions, then you were unsuccessful. Simply type sessions -i <id> to jump into a shell"
If it states No sessions, then you were unsuccessful. Simply type sessions -i <id> to jump into a shell
msf >
Hello mate,
To work around it I simply changed one setting in /etc/postgresql/8.3/main/postgresql.conf:
ssl = true
I changed to:
ssl = false
That is it!
There are two active threads discussing this very issue at the moment...
http://www.backtrack-linux.org/forum...ostgresql.html
http://www.backtrack-linux.org/forum...ion-earth.html
I got 99 problems but the bits ain't one...
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.