Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: call stack error with both metasploit drivers.

  1. #1
    Junior Member
    Join Date
    Dec 2008
    Posts
    31

    Default call stack error with both metasploit drivers.

    I am having a hell of a time concerning issues with metasploit on BT5. I recieve call stack errors when trying to create databases with both drivers mysql and postgresql. below is metasploit's output. If someone could help me out, I'd appreciate it. Also, off-topic but what are the commands to install sqlite?

    Code:
                         888                           888        d8b888
                         888                           888        Y8P888
                         888                           888           888
    88888b.d88b.  .d88b. 888888 8888b. .d8888b 88888b. 888 .d88b. 888888888
    888 "888 "88bd8P  Y8b888       "88b88K     888 "88b888d88""88b888888
    888  888  88888888888888   .d888888"Y8888b.888  888888888  888888888
    888  888  888Y8b.    Y88b. 888  888     X88888 d88P888Y88..88P888Y88b.
    888  888  888 "Y8888  "Y888"Y888888 88888P'88888P" 888 "Y88P" 888 "Y888
                                               888
                                               888
                                               888
    
    
           =[ metasploit v3.8.0-dev [core:3.8 api:1.0]
    + -- --=[ 687 exploits - 357 auxiliary - 39 post
    + -- --=[ 217 payloads - 27 encoders - 8 nops
           =[ svn r12582 updated today (2011.05.11)
    
    msf > db_driver[*]    Active Driver: postgresql[*]        Available: postgresql, mysql
    
    msf > db_driver mysql[*] Using database driver mysql
    msf > db_connect root:toor@127.0.0.1/home/hax/metasplot/cnk
    [-] Error while running command db_connect: Failed to connect to the database: uninitialized constant MysqlCompat::MysqlRes
    
    Call stack:
    /opt/framework3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1850:in `db_connect_mysql'
    /opt/framework3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1733:in `cmd_db_connect'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:331:in `run_command'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:293:in `block in run_single'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:287:in `each'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:287:in `run_single'
    /opt/framework3/msf3/lib/rex/ui/text/shell.rb:143:in `run'
    /opt/framework3/msf3/msfconsole:130:in `<main>'
    msf > db_driver postgresql[*] Using database driver postgresql
    msf > db_connect root:toor@127.0.0.1/home/hax/metasplot/cnk
    [-] Error while running command db_connect: 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/framework3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:2030:in `db_connect_postgresql'
    /opt/framework3/msf3/lib/msf/ui/console/command_dispatcher/db.rb:1733:in `cmd_db_connect'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:331:in `run_command'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:293:in `block in run_single'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:287:in `each'
    /opt/framework3/msf3/lib/rex/ui/text/dispatcher_shell.rb:287:in `run_single'
    /opt/framework3/msf3/lib/rex/ui/text/shell.rb:143:in `run'
    /opt/framework3/msf3/msfconsole:130:in `<main>'
    RIP SHIRLEY 10/11/2008

  2. #2
    Just burned his ISO
    Join Date
    Dec 2010
    Posts
    23

    Default Re: call stack error with both metasploit drivers.

    Hi,

    Me too. I posted earlier when I couldn't open my BT4 MSF database on BT5. I've just checked and I can't create a NEW database without getting the same error.

    Any help would be much appreciated.

  3. #3
    Just burned his ISO
    Join Date
    Feb 2011
    Location
    SLC, UT
    Posts
    2

    Default Re: call stack error with both metasploit drivers.

    Exact same story here.

    The MySQL gem was working out of the box in BT4R2.

    Edit: Looks like another thread stating this exact same issue was closed all because it had the string 'BT4' in it. Tell the forum users to read, read, read. -- Then fail to do it themselves. Lovely.
    Last edited by wtmh144; 05-11-2011 at 08:26 PM. Reason: Passive-Aggressive jab at over zealous moderator.

  4. #4
    Member dustyboner's Avatar
    Join Date
    Jan 2010
    Posts
    98

    Default Re: call stack error with both metasploit drivers.

    I was already connected to a db when i started up.
    I ran nmap and saved the scan to as x.nmap.
    Then ran
    Code:
    root@bt:~# msfconsole
    
    msf > db_import /root/x.namp
    it was imported without any problems

    i didn't need to use the db_driver or db_connect commands

  5. #5
    Just burned his ISO
    Join Date
    Feb 2011
    Location
    SLC, UT
    Posts
    2

    Default Re: call stack error with both metasploit drivers.

    No s@!t. Well... That shut me up. We're already connected.

    Happy to see it honestly. I had to script that connection in in the previous version.

    Not too friendly to those who want to use different DBMS's though.

  6. #6
    Just burned his ISO
    Join Date
    Dec 2010
    Posts
    23

    Default Re: call stack error with both metasploit drivers.

    He's correct - it's already connected. However if you disconnect then switch to mysql and try to load or create a new DB it gives the same error.

  7. #7
    Junior Member
    Join Date
    Dec 2008
    Posts
    31

    Default Re: call stack error with both metasploit drivers.

    Quote Originally Posted by wtmh144 View Post
    Exact same story here.

    The MySQL gem was working out of the box in BT4R2.

    Edit: Looks like another thread stating this exact same issue was closed all because it had the string 'BT4' in it. Tell the forum users to read, read, read. -- Then fail to do it themselves. Lovely.
    Yep...I saw that one.
    RIP SHIRLEY 10/11/2008

  8. #8
    Just burned his ISO
    Join Date
    Dec 2010
    Posts
    23

    Default Re: call stack error with both metasploit drivers.

    Does anyone have an idea of how to fix this?

    I have limited knowledge, but have removed and reinstalled MSF3 but it's still the same.

    Thanks

  9. #9
    Junior Member dec1bel's Avatar
    Join Date
    Dec 2010
    Location
    US
    Posts
    36

    Default Re: call stack error with both metasploit drivers.

    Same story here. I can't destroy the default-connected database when I'm done either which isn't world crashing but it's frustrating. I like to use different databases on different jobs.

    Anyone have any luck yet?

    This is happening on the VM instance of BT5 and two different laptops running the x86 Gnome BT5 versions. I'm also having occasional call stack error troubles with msfrpc and msfrpcd.
    Last edited by dec1bel; 05-12-2011 at 11:50 PM. Reason: update

  10. #10
    Just burned his ISO
    Join Date
    Dec 2010
    Posts
    23

    Default Re: call stack error with both metasploit drivers.

    The same thing happens on KDE.

Page 1 of 2 12 LastLast

Similar Threads

  1. dpkg subprocess returned error(1) -> nvidia-drivers
    By inf_437 in forum OLD Newbie Area
    Replies: 0
    Last Post: 06-12-2009, 08:39 AM
  2. make error - help with installing drivers for WG111v2
    By mewoshh in forum OLD Newbie Area
    Replies: 4
    Last Post: 02-23-2009, 08:45 PM
  3. metasploit -msfupdate error - svn : PROFIND request error
    By aisketui in forum OLD BT3beta Software related issues
    Replies: 2
    Last Post: 02-11-2009, 03:23 AM
  4. Error in script that calls IPW3945 drivers
    By browners in forum OLD BT3beta Bugs and Fixes
    Replies: 1
    Last Post: 03-11-2008, 09:22 PM
  5. Command not found error, since installing alfa drivers
    By bertje in forum OLD Newbie Area
    Replies: 5
    Last Post: 10-12-2007, 04:25 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •