search

sxiii / opendlp

Automatically exported from code.google.com/p/opendlp
0 stars 0 forks source link

DBD::mysql::st execute failed: Unknown column 'metahost' in 'field list' #74

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
-----------------------------------------

   1. Manually install OpenDLP-0.5.1.tar.bz2, following the    instructions in README-0.5.1
   2. Create a profile
   3. Start a scan

What is the expected output? What do you see instead?
--------------------------------------------------------

I expect the scan to start.

Instead I see the error message in the web app: -

Could not get profile information. Ensure the profile exists and try to deploy 
your scan again.

In apache's error.log I see: -

[Fri Aug 31 14:22:42 2012] [error] [client 5.5.41.6] DBD::mysql::st execute 
failed: Unknown column 'metahost' in 'field list' at 
/var/www/OpenDLP/web/bin/start-verify.html line 135., referer: 
http://5.5.41.5/OpenDLP/startscan.html
[Fri Aug 31 14:22:42 2012] [error] [client 5.5.41.6] DBD::mysql::st 
fetchrow_arrayref failed: fetch() without execute() at 
/var/www/OpenDLP/web/bin/start-verify.html line 136., referer: 
http://5.5.41.5/OpenDLP/startscan.html

What version of the product are you using? On what operating system?
------------------------------------------------------------------------
OpenDLP 0.5.1
Ubuntu 10.04.2 LTS (Based off BT5R1)
Linux 2.6.39.4 (2.6.39.4-10.00.Custom)
Perl v5.10.1 (5.10.1-8ubuntu2.1)
apache 2.2.14-5ubuntu8.4
CPU is x86_64

Please provide any additional information below.
-----------------------------------------------------

I don't see a 'metahost' field in the profiles table. In the instructions I see 
it for the upgrade instructions to add it with the ALTER TABLE command, but 
it's not in the 5. MySQL Configuration instructions (specifically step 4).

My guess is that step 4 is slightly wrong and should include metahost before 
metaport. Am I right?

I'm also guessing that the order of the columns is important (as in an expected 
order when processing result sets from SELECT * and similar). Am I right?

Original issue reported on code.google.com by abuse...@gmail.com on 30 Aug 2012 at 6:50

GoogleCodeExporter commented 8 years ago 
You are right on all accounts. Step 4 is slightly wrong, and the order of the 
columns is important.

I will fix this in the next release, thanks.

Original comment by andrew.O...@gmail.com on 30 Aug 2012 at 6:58