Thread: [Codestriker-user] Receiving configuration error while installing version 1.9.1
Brought to you by:
sits
|
From: Keith L. <the...@gm...> - 2005-08-16 22:40:29
|
I am receiving the following error when try to run the bin/install.pl scrip= t=20 in version 1.9.1: The database configuration variable $db has not been set. Please edit the codestriker.conf file and run this command again. I know I have the $db variable set, here's the value of my config file: $db =3D 'DBI:mysql:dbname=3Dcodestrikerdb'; I've checked the permissions on the files and everything looks OK. I've run= =20 the script as both root and the directory owner, but to no avail.=20 I've checked the mailing list and have 'Googled' the error msg, but haven't= =20 found anything that will help me correct this issue. Any ideas?=20 Thanks, Keith Levy |
|
From: Jason R. <jre...@ya...> - 2005-08-17 02:16:53
|
Hi,
I just updated to 1.9.1 and ran install.pl ok. The only way I could get it to fail was to run
install.pl from another directory besides bin. Did you cd into bin when you ran the script?
Here is the code that sends out the error from install.pl
# Make sure the $db configuration variable has been set, and if not
# complain and exit.
if (! defined $Codestriker::db) {
print STDERR
"The database configuration variable \$db has not been set.\n";
print STDERR
"Please edit the codestriker.conf file and run this command again.\n";
exit -1;
}
I think it is OK. So, if you where in the bin directory, please send out what OS and version of
perl you are using. I tested it under debian sarge, with perl 5.8.4.
Thanks
Jason.
--- Keith Levy <the...@gm...> wrote:
> I am receiving the following error when try to run the bin/install.pl script
> in version 1.9.1:
>
> The database configuration variable $db has not been set.
> Please edit the codestriker.conf file and run this command again.
>
>
> I know I have the $db variable set, here's the value of my config file:
>
> $db = 'DBI:mysql:dbname=codestrikerdb';
>
>
> I've checked the permissions on the files and everything looks OK. I've run
> the script as both root and the directory owner, but to no avail.
>
> I've checked the mailing list and have 'Googled' the error msg, but haven't
> found anything that will help me correct this issue. Any ideas?
>
>
> Thanks,
> Keith Levy
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
|
From: David S. <si...@us...> - 2005-08-17 04:05:33
|
On Wed, 17 Aug 2005 08:39, Keith Levy wrote: > I am receiving the following error when try to run the bin/install.pl > script in version 1.9.1: > > The database configuration variable $db has not been set. > Please edit the codestriker.conf file and run this command again. That seems strange - either the configuration file is badly formatted (ie, extra hanging quote) or apache couldn't access it. Is there anything in the apache error logs? Could you send me your codestriker.conf file? -- Cheers, David |
|
From: David S. <si...@us...> - 2005-08-17 04:08:13
|
On Wed, 17 Aug 2005 08:39, Keith Levy wrote: > I am receiving the following error when try to run the bin/install.pl > script in version 1.9.1: > > The database configuration variable $db has not been set. > Please edit the codestriker.conf file and run this command again. Whoops - I answered this too quickly, this is when you are running install.pl... I don't have this issue - can you send me your codestriker.conf file? I take it you are running install.pl in the bin sub-directory, and not as bin/install.pl from the root directory? -- Cheers, David |
|
From: David S. <si...@us...> - 2005-08-18 17:03:45
|
Hi Keith,
On Thu, 18 Aug 2005 00:59, Keith Levy wrote:
> Attached is my copy of the config file ...
I can see what the problem is, it has nothing to do with the 1.9.1 as such,
but is a problem in the actual configuation file. If you go right down to
the bottom, to your $comment_state_metrics definition, it reads:
# Four metrics defined: Status, Level, Mode and Type.
$comment_state_metrics =
[
{ name=>'Status', values=>['Submitted', 'Invalid', 'Completed'],
default_value=>'Submitted' },
( name=>'Level', values=>['Major', 'Minor'] },
{ name=>'Mode', values=>['Missing', 'Wrong', 'Unclear',
'Suggestion'] },
{ name=>'Type', values=>['Logic', 'Data Handling', 'Interface',
'Error Handling', 'Performance', 'Comments',
'Standards'] }
];
You can see for the 'Level' metric, you are starting the definition with an
open bracket '(', not a curly brace '{'. This has effectively caused a
syntax error in the configuration file, which has caused the "$db has not
been set" error. Its a shame we don't get a more helpful error message,
I'll look into that.
The standard configuration file which ships with codestriker doesn't have
this defect in it, so perhaps you accidently changed this?
Anyway - changing it to a brace should fix the issue, ie:
{ name=>'Level', values=>['Major', 'Minor'] },
--
Cheers,
David
|
|
From: Keith L. <the...@gm...> - 2005-08-18 17:17:37
|
Thanks!
On 8/18/05, David Sitsky <si...@us...> wrote:
>=20
> Hi Keith,
>=20
> On Thu, 18 Aug 2005 00:59, Keith Levy wrote:
> > Attached is my copy of the config file ...
>=20
> I can see what the problem is, it has nothing to do with the 1.9.1 as=20
> such,
> but is a problem in the actual configuation file. If you go right down to
> the bottom, to your $comment_state_metrics definition, it reads:
>=20
> # Four metrics defined: Status, Level, Mode and Type.
> $comment_state_metrics =3D
> [
> { name=3D>'Status', values=3D>['Submitted', 'Invalid', 'Completed'],
> default_value=3D>'Submitted' },
> ( name=3D>'Level', values=3D>['Major', 'Minor'] },
> { name=3D>'Mode', values=3D>['Missing', 'Wrong', 'Unclear',
> 'Suggestion'] },
> { name=3D>'Type', values=3D>['Logic', 'Data Handling', 'Interface',
> 'Error Handling', 'Performance', 'Comments',
> 'Standards'] }
> ];
>=20
> You can see for the 'Level' metric, you are starting the definition with=
=20
> an
> open bracket '(', not a curly brace '{'. This has effectively caused a
> syntax error in the configuration file, which has caused the "$db has not
> been set" error. Its a shame we don't get a more helpful error message,
> I'll look into that.
>=20
> The standard configuration file which ships with codestriker doesn't have
> this defect in it, so perhaps you accidently changed this?
>=20
> Anyway - changing it to a brace should fix the issue, ie:
>=20
> { name=3D>'Level', values=3D>['Major', 'Minor'] },
>=20
>=20
> --
> Cheers,
> David
>=20
>
|