Closed Bug 307726 Opened 19 years ago Closed 19 years ago

No value for param user_verify_class

Categories

(Bugzilla :: Installation & Upgrading, defect)

Product:
Bugzilla
Component:
Installation & Upgrading
Version:
2.20
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: xq0948, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; FunWebProducts; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: 

We have a inernal Bugzilla v2.16.7. I downloaded the dev version bugzilla-
2.20rc2. When I launched its website, I got the following error:

No value for param user_verify_class (try running checksetup.pl again) at 
Bugzilla/Config.pm line 163.

I never see the param user_verify_class in our previous version. What's the 
value should I give and should I edit it directly in params file under data 
directory?

Thanks in advance for your help!

Jean
 



Reproducible: Always
Did you run checksetup? That sounds like the error that happens normally when
you don't run checksetup.pl after the upgrade.
Assignee: administration → installation
Component: Administration → Installation & Upgrading
I did run checksetup.pl script without any issue.
what about this bug? reporter, can you still reproduce the problem?
yes.  I got the following error when I lauched the web server:

Software error:
No value for param user_verify_class (try running checksetup.pl again) at 
Bugzilla/Config.pm line 163.
BEGIN failed--compilation aborted at Bugzilla/Auth.pm line 43.
Compilation failed in require at Bugzilla.pm line 28.
BEGIN failed--compilation aborted at Bugzilla.pm line 28.
Compilation failed in require at Bugzilla/Bug.pm line 39.
BEGIN failed--compilation aborted at Bugzilla/Bug.pm line 39.
Compilation failed in require at CGI.pl line 48.
BEGIN failed--compilation aborted at CGI.pl line 48.


Someone reported the same problem when upgrading from 2.18 to 2.20. Retargetting
to keep this bug in our radar.
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.20
This error usually means that "data/params" wasn't created, since
user_verify_class is the first param that Bugzilla tries to use (in the
Bugzilla::Auth BEGIN block).

Reporter, can you confirm that your data/params file actually exists?
I'm doing updates and I copied all data dir from 2.16.7 into the new version 
2.20. So, yes, data/params file does exist. I do suspect there's something 
missing in params but I don't know what?

Here's the content of data/params file:

$::param{'allowbugdeletion'} = '0';
$::param{'allowemailchange'} = '0';
$::param{'allowuserdeletion'} = '0';
$::param{'bannerhtml'} = '';
$::param{'blurbhtml'} = 'This is <B>Bugzilla</B>: the Mozilla bug system.  For 
more 
information about what Bugzilla is and what it can do, see 
<A HREF="http://www.mozilla.org/">mozilla.org</A>\'s
<A HREF="http://www.mozilla.org/bugs/"><B>bug pages</B></A>.';
$::param{'bodyhtml'} = 'BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000EE" 
VLINK="#551A8B" ALINK="#FF0000"';
$::param{'browserbugmessage'} = 'this may indicate a bug in your browser.
';
$::param{'capitalizelists'} = '0';
$::param{'commentonaccept'} = '1';
$::param{'commentonclearresolution'} = '1';
$::param{'commentonclose'} = '1';
$::param{'commentonconfirm'} = '1';
$::param{'commentonduplicate'} = '1';
$::param{'commentonreassign'} = '1';
$::param{'commentonreassignbycomponent'} = '1';
$::param{'commentonreopen'} = '1';
$::param{'commentonresolve'} = '1';
$::param{'commentonverify'} = '1';
$::param{'cookiepath'} = '/';
$::param{'curmilestone'} = '1';
$::param{'defaultpriority'} = 'P2';
$::param{'defaultquery'} 
= 'bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=%22Importance%
22';
$::param{'despotbaseurl'} = 'http://cvs-
mirror.mozilla.org/webtools/despot/despot.cgi';
$::param{'emailregexp'} = '^[^@]*@[^@]*\\.[^@]*$';
$::param{'emailregexpdesc'} = 'A legal address must contain exactly one \'@\', 
and at least one \'.\' after the @.';
$::param{'emailsuffix'} = '';
$::param{'entryheaderhtml'} = '<A HREF="bugwritinghelp.html">Bug writing 
guidelines</A>';
$::param{'errorhtml'} = '<TABLE CELLPADDING=20><TR><TD BGCOLOR="#ff0000">
<FONT SIZE="+2">%errormsg%</FONT></TD></TR></TABLE>
<P>Please press <B>Back</B> and try again.<P>';
$::param{'expectbigqueries'} = '0';
$::param{'footerhtml'} = '<TABLE BORDER="0"><TR><TD BGCOLOR="#000000" 
VALIGN="TOP">
<TABLE BORDER="0" CELLPADDING="10" CELLSPACING="0" WIDTH="100%" 
BGCOLOR="lightyellow">
<TR><TD>
%blurbhtml%
<BR>
%commandmenu%
</TD></TR></TABLE></TD></TR></TABLE>';
$::param{'headerhtml'} = '<table border=0 cellpadding=0 cellspacing=0><tr>
 <td><A href="http://bioinformatics.gsk.com"><img border="0" 
src="http://phu645.um.us.sbphrd.com:3084/bixlaf/images/logos/bix_DARK_BLUE.jpg">
</A></td>
            <td width=100% bgcolor="#336699" nowrap><A 
href="http://bugdev.gsk.com:8006"><font color=white font=arial 
size=6>Bugzilla</font></A></td>
</tr></table>';
$::param{'LDAPBaseDN'} = 'dc=gsk,dc=com';
$::param{'LDAPmailattribute'} = 'mail';
$::param{'LDAPserver'} = 'rtpsedpool.gsk.com:389';
$::param{'letsubmitterchoosepriority'} = '1';
$::param{'maintainer'} = 'ww.bixhelp@gsk.com';
$::param{'maxattachmentsize'} = '1000';
$::param{'maxpatchsize'} = '1000';
$::param{'mostfreqhtml'} = '<br><p>

<b>What are "most frequent bugs"?</b>

<blockquote>The Most Frequent Bugs page lists the known open bugs which 
are reported most frequently in recent builds of Mozilla. It is automatically
generated from the Bugzilla database every 24 hours, by counting the number
of direct and indirect duplicates of bugs.
This information is provided in order to assist in minimizing
the amount of duplicate bugs entered into Bugzilla which in turn cuts down
on development time.
</blockquote>

<b>How do I use this list?</b>

<ul>
<li>Review the most frequent bugs list.</li>
<li>If problem is listed:</li>

<ul>
<li>Click on Bug # link to confirm that you have found the same bug and comment
if you have additional information. Or move on with your testing
of the product.</li>
</ul>

<li>If problem not listed:</li>

<ul>
<li>Go to the <a href="query.cgi">Bugzilla Query/Search</a>
page to try and locate a similar bug that has already been written.</li>
<li>If you find your bug in Bugzilla, feel free to comment with any new or
additional data you may have.</li>
<li>If you cannot find your problem already documented in Bugzilla, go to the
<a href="http://www.mozilla.org/quality/help/bug-form.html">Bugzilla Helper</a> 
and post a new bug.</li>
</ul>

</ul>
<br>
';
$::param{'mostfreqthreshold'} = '2';
$::param{'move-button-text'} = 'Move To Bugscape';
$::param{'move-enabled'} = '0';
$::param{'move-to-address'} = 'bugzilla-import';
$::param{'move-to-url'} = '';
$::param{'moved-default-component'} = '';
$::param{'moved-default-product'} = '';
$::param{'moved-from-address'} = 'bugzilla-admin';
$::param{'movers'} = '';
$::param{'musthavemilestoneonaccept'} = '0';
$::param{'mybugstemplate'} = 'buglist.cgi?
bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=%userid%
&emailtype1=exact&emailassigned_to1=1&emailreporter1=1';
$::param{'newchangedmail'} = 'From: bugzilla-daemon
To: %to%
Subject: [Bug %bugid%] %neworchanged%%summary%
X-Bugzilla-Reason: %reasonsheader%

%urlbase%show_bug.cgi?id=%bugid%

%diffs%



%reasonsbody%';
$::param{'nummilestones'} = '10';
$::param{'passwordmail'} = 'From: bugzilla-daemon
To: %mailaddress%
Subject: Your Bugzilla password.

To use the wonders of Bugzilla, you can use the following:

 E-mail address: %login%
       Password: %password%

 To change your password, go to:
 %urlbase%userprefs.cgi
';
$::param{'preferlists'} = '1';
$::param{'queryagainstshadowdb'} = '0';
$::param{'sendmailnow'} = '0';
$::param{'shadowdb'} = '';
$::param{'shutdownhtml'} = '';
$::param{'strictvaluechecks'} = '0';
$::param{'supportwatchers'} = '1';
$::param{'urlbase'} = 'http://bugdev.gsk.com:8070/';
$::param{'usebrowserinfo'} = '1';
$::param{'usebuggroups'} = '0';
$::param{'usebuggroupsentry'} = '0';
$::param{'usedependencies'} = '1';
$::param{'usedespot'} = '0';
$::param{'useLDAP'} = '1';
$::param{'useqacontact'} = '1';
$::param{'usequip'} = '0';
$::param{'usestatuswhiteboard'} = '0';
$::param{'usetargetmilestone'} = '0';
$::param{'usevotes'} = '1';
$::param{'voteremovedmail'} = 'From: bugzilla-daemon
To: %to%
Subject: [Bug %bugid%] Some or all of your votes have been removed.

Some or all of your votes have been removed from bug %bugid%.

%votesoldtext%

%votesnewtext%

Reason: %reason%

%urlbase%show_bug.cgi?id=%bugid%
';
$::param{'webdotbase'} = 'http://www.research.att.com/~north/cgi-
bin/webdot.cgi/%urlbase%';
$::param{'whinedays'} = '0';
$::param{'whinemail'} = 'From: %maintainer%
To: %email%
Subject: Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (%urlbase%) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in %whinedays% days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it\'s INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn\'t belong to you, and you reassign it to someone
    else.  (Hint: if you don\'t know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can\'t solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    %urlbase%buglist.cgi?bug_status=NEW&assigned_to=%userid%

Or, you can use the general query page, at
%urlbase%query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven\'t been touched for a week or more.

You will get this message once a day until you\'ve dealt with these bugs!

';
1;
Keywords: qawanted
This is not the correct format for data/params in 2.20. I suspect this file is read only. Reporter, could you remove this file from data/ and let checksetup.pl recreate it? And then tell us if Bugzilla is still reporting this error message.
mkanat, wicked found something interesting in checksetup.pl:

line 1205:

# WriteParams will only write out still-valid entries
WriteParams();

line 1383:

fixPerms("$datadir/params", $<, $webservergid, 017);


So when WriteParams() tries to update data/params, the write access may not be set correctly yet. Could this (partially) explains the problem encountered here?
Jean, have you installed Bugzilla using a RPM package?

It looks like RPM packages have a different $datadir than the tarball downloaded from bugzilla.org. So it's possible that your data/param config file is ignored as Bugzilla now looks somewhere else.

Could you make sure where $datadir is pointing to? $datadir is defined in Bugzilla/Config.pm and is based on $libdir, so you should also look at this variable.
Hi Bugzilla support folks:

Thank you so much for following up this issue. Here's the part of Config.pm

our $libpath = '.';
our $localconfig = "$libpath/localconfig";
our $datadir = "$libpath/data";


actually, I did get it to work (index page and query page). params file is created with incorrect values. I'll have to manually edit it.
Jean, could you make sure that data/params is not read only? As I said in comment 8, this is not the correct format so it looks like checksetup.pl didn't update it.
the file was created as rw. Here's the content. The problem I have at the moment is the authorization. I couldn't login to setup params.

*******************

%param = (
           'LDAPBaseDN' => 'dc=gsk,dc=com',
           'LDAPbinddn' => '',
           'LDAPfilter' => '',
           'LDAPmailattribute' => 'mail',
           'LDAPserver' => 'rtpsedpool.gsk.com:389',
           'LDAPuidattribute' => 'uid',
           'allowbugdeletion' => 0,
           'allowemailchange' => 0,
           'allowuserdeletion' => 0,
           'auth_env_email' => '',
           'auth_env_id' => '',
           'auth_env_realname' => '',
           'bonsai_url' => '',
           'browserbugmessage' => 'this may indicate a bug in your browser.',
           'chartgroup' => 'editbugs',
           'commentonaccept' => 1,
           'commentonclearresolution' => 1,
           'commentonclose' => 1,
           'commentonconfirm' => 1,
           'commentoncreate' => 1,
           'commentonduplicate' => 1,
           'commentonreassign' => 1,
           'commentonreassignbycomponent' => 1,
           'commentonreopen' => 1,
           'commentonresolve' => 1,
           'commentonverify' => 1,
           'confirmuniqueusermatch' => 1,
           'cookiedomain' => '',
           'cookiepath' => '/',
           'createemailregexp' => '.*',
           'cvsroot' => '',
           'cvsroot_get' => '',
           'defaultlanguage' => 'en',
           'defaultopsys' => '',
           'defaultplatform' => '',
           'defaultpriority' => 'P2',
           'defaultquery' => 'bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailqa_contact2=1&order=Importance&long_desc_type=substring',
           'defaultseverity' => 'normal',
           'emailregexp' => '^[\\w\\.\\+\\-=]+@[\\w\\.\\-]+\\.[\\w\\-]+$',
           'emailregexpdesc' => 'A legal address must contain exactly one \'@\', and at least one \'.\' after the @.',
           'emailsuffix' => '',
           'insidergroup' => '',
           'languages' => 'en',
           'letsubmitterchoosemilestone' => 1,
           'letsubmitterchoosepriority' => 1,
           'loginnetmask' => '32',
           'lxr_root' => '',
           'lxr_url' => '',
           'mail_delivery_method' => 'sendmail',
           'maintainer' => 'ww.bixhelp@gsk.com',
           'makeproductgroups' => 0,
           'maxattachmentsize' => '1000',
           'maxlocalattachment' => '0',
           'maxpatchsize' => '1000',
           'maxusermatches' => '1000',
           'mostfreqthreshold' => '2',
           'move-button-text' => 'Move To Bugscape',
           'move-enabled' => 0,
           'move-to-address' => 'bugzilla-import',
           'move-to-url' => '',
           'moved-default-component' => '',
           'moved-default-product' => '',
           'moved-from-address' => 'bugzilla-admin',
           'movers' => '',
           'musthavemilestoneonaccept' => 0,
           'mybugstemplate' => 'buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=%userid%&amp;emailtype1=exact&amp;emailassigned_to1=1&amp;emailreporter1=1',
           'newchangedmail' => 'From: bugzilla-daemon
To: %to%
Subject: [Bug %bugid%] %neworchanged%%summary%
%threadingmarker%
X-Bugzilla-Reason: %reasonsheader%
X-Bugzilla-Product: %product%
X-Bugzilla-Component: %component%

%urlbase%show_bug.cgi?id=%bugid%

%diffs%

--%space%
Configure bugmail: %urlbase%userprefs.cgi?tab=email
%reasonsbody%',
           'noresolveonopenblockers' => 0,
           'passwordmail' => 'From: bugzilla-daemon
To: %mailaddress%
Subject: Your Bugzilla password.

To use the wonders of Bugzilla, you can use the following:

 E-mail address: %login%
       Password: %password%

 To change your password, go to:
 %urlbase%userprefs.cgi
',
           'quip_list_entry_control' => 'open',
           'rememberlogin' => 'on',
           'requirelogin' => '0',
           'sendmailnow' => 1,
           'shadowdb' => '',
           'shadowdbhost' => '',
           'shadowdbport' => '3306',
           'shadowdbsock' => '',
           'showallproducts' => 0,
           'shutdownhtml' => '',
           'smtpserver' => 'localhost',
           'ssl' => 'never',
           'sslbase' => '',
           'supportwatchers' => 0,
           'timetrackinggroup' => '',
           'timezone' => '',
           'urlbase' => 'http://bugdev.gsk.com/',
           'usebugaliases' => 0,
           'useclassification' => 0,
           'useentrygroupdefault' => 0,
           'usemenuforusers' => '0',
           'useqacontact' => 1,
           'user_info_class' => 'CGI',
           'user_verify_class' => 'DB',
           'usermatchmode' => 'off',
           'usestatuswhiteboard' => 0,
           'usetargetmilestone' => 0,
           'usevisibilitygroups' => 0,
           'usevotes' => 1,
           'voteremovedmail' => 'From: bugzilla-daemon
To: %to%
Subject: [Bug %bugid%] Some or all of your votes have been removed.

Some or all of your votes have been removed from bug %bugid%.

%votesoldtext%

%votesnewtext%

Reason: %reason%

%urlbase%show_bug.cgi?id=%bugid%
',
           'webdotbase' => 'http://www.research.att.com/~north/cgi-bin/webdot.cgi/%urlbase%',
           'whinedays' => 7,
           'whinemail' => 'From: %maintainer%
To: %email%
Subject: Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (%urlbase%) that require
attention.

All of these bugs are in the NEW or REOPENED state, and have not
been touched in %whinedays% days or more.  You need to take a look
at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it\'s INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn\'t belong to you, and you reassign it to someone
    else.  (Hint: if you don\'t know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    default assignee of selected component" option.)
(3) You decide the bug belongs to you, but you can\'t solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark
it if you like!):

 %urlbase%buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=%userid%

Or, you can use the general query page, at
%urlbase%query.cgi

Appended below are the individual URLs to get to all of your NEW bugs that
haven\'t been touched for a week or more.

You will get this message once a day until you\'ve dealt with these bugs!

'
         );

'user_verify_class' => 'DB',

I thought you didn't have this param? ;)

Now that you have it, and without more information, I don't see what we could do.
I found out one of perl module doen't meet the minimum version requirement. Once that's resolved, setcheckup created a params file. I'll have to figure out the login issue before I can do anything else. Thanks for your help! 
Is this a duplicate of bug 289742?
No, this is INVALID. If checksetup doesn't get past the module checks, of course the params file is bad.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Target Milestone: Bugzilla 2.20 → ---
Version: unspecified → 2.20
Status: RESOLVED → VERIFIED
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.