Metasploit Postgresql database connection eror
Hey guys -
I've been using metasploit for several weeks and utilizing the default database connection. Metasploit comes with postgresql and would automatically start and connect to its default database on port 7175 . I have no idea what changed, but now it will not start postgres and connect to it. I can manually start postgresql through /etc/init.d/postgresql-8.4 on port 5432 and create and connect with databases, but they are not the one I have been using.
My /opt/framework/config/database.yml file points to a database named msf3 on localhost:7175, but i can't connect to it, nor seem to start postgres on 7175. Even manually starting ctl.sh in /opt/framework/postgresql/scripts does not start the service.
Do you have any ideas? It went from seamlessly starting the postgres service and connecting when i ran msfconsole, to not starting at all. I don't necessarily mind creating a new database and starting my own postgresql server, but I've been using msf3 on 7175 for weeks and it has all my hosts and info.
Any suggestions welcome. Thanks!
Re: Metasploit Postgresql database connection eror
i'm (re)testing now:
Thu Oct 6 11:42:17 CEST 2011
root@bt:~# uname -a
Linux bt 18.104.22.168 #1 SMP Thu Aug 18 13:38:02 NZST 2011 i686 GNU/Linux
root@bt:~# ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]
| 3Kom SuperHack II Logon |
| User Name: [ security ] |
| Password: [ ] |
| [ OK ] |
=[ metasploit v4.0.1-dev [core:4.0 api:1.0]
+ -- --=[ 737 exploits - 378 auxiliary - 84 post
+ -- --=[ 228 payloads - 27 encoders - 8 nops
=[ svn r13812 updated 3 days ago (2011.10.03)
msf > db_driver[*] Active Driver: postgresql[*] Available: postgresql, mysql
msf > db_driver postgresql[*] Using database driver postgresql
msf > db_status[*] postgresql connected to msf3 :)
msf > db_autopwn -e -p -q -R great 192.168.1.253[*] (1/17 [0 sessions]): Launching exploit/windows/dcerpc/ms03_026_dcom against 192.168.1.253:135...[*] (2/17 [0 sessions]): Launching exploit/freebsd/samba/trans2open against 192.168.1.253:139...[*] (3/17 [0 sessions]): Launching exploit/linux/samba/trans2open against 192.168.1.253:139...[*] (4/17 [0 sessions]): Launching exploit/multi/samba/usermap_script against 192.168.1.253:139...[*] (5/17 [0 sessions]): Launching exploit/solaris/samba/trans2open against 192.168.1.253:139...
.............FOR ME WORK FINE! bye!