Problem with database

[Paradigma]

Hey, I've been searching around for hours trying to find anything to shed light on a problem I am having importing data into the mysql database, with zero success.

I don't see what I'm doing wrong here, but first I /etc/init.d/mysql start, and it starts up fine, I'm using db_driver mysql, and when I run db_connect root:toor@127.0.0.1/msf3 it executes without problem.

So far so good, when I enter db_import /root/test.nessus I get:

msf > db_import /root/test.nessus[*] Importing 'Nessus XML (v2)' data[*] Importing host 127.0.0.1[*] Successfully imported /root/test.nessus

Then I run:
msf > db_hosts

Hosts
=====

address mac name os_name os_flavor os_sp purpose info comments
------- --- ---- ------- --------- ----- ------- ---- --------

I'm completely lost...

[sickness]

Try it using something else like nmap or NeXpose report see if it works, I think it has something to do with the Nessus XML.

[WARCRY]

How did you start you msfconsole from menu or from Kconsole?

[Paradigma]

Interesting. Yeah, it worked. Is there anyway to fix the formatting of the xml or am I stuck doing exploits without a DB? Seems kind of odd that it would work with some people and not with others...

[WARCRY]

Try and add a host to your db manually. See if it works.
I'm new to bt too, but starting msfconsole from KDE menu instead of launching it from your Konsole may cause this problem. Don't now why though.

[sickness]

Interesting. Yeah, it worked. Is there anyway to fix the formatting of the xml or am I stuck doing exploits without a DB? Seems kind of odd that it would work with some people and not with others...

Try exporting it in another format or use the following command:

db_import_nessus_xml

[Paradigma]

It was originally exported as a OpenVAS .nbe file, which did not work in the same way as the .nessus. db_nmap works fine so I doubt it is a problem with the database, maybe just metasploits handling of the nessus xml format because don't OpenVAS and Nessus use the same engine for xml?

Whats even more interesting is that when I tried to use the postgresql driver (I thought it might just be mysql at the time), it doesn't even build the base properly, any call after db_connect returns typical SQL errors...