WeBWorK Main Forum

constituency_hash error

constituency_hash error

by Dennis Keeler -
Number of replies: 2
Hello all. After a semester away from WeBWorK, I just upgraded my server from 2.3.0 to 2.3.2, via CVS. I also updated all the Database Problems (I'm not using the File Based problems). Now whenever I try to access a page which would show me a problem or problems (such as asking to see problems in the Library Browser or clicking on an old HW assignment) I get the following error. Thanks for your help. -Dennis

P.S. I just created a new course. Here, the error message is not appearing, but when I hit View Problems in the Library Browser, the Firefox just spins its wheels, waiting for the server to give a new page. Maybe this is some kind of first time generation issue.

Error messages

"constituency_hash" is not exported by the WeBWorK::Utils module
Can't continue after import errors at /opt/webwork/webwork2/lib/WeBWorK/Utils/DelayedMailer.pm line 23
BEGIN failed--compilation aborted at /opt/webwork/webwork2/lib/WeBWorK/Utils/DelayedMailer.pm line 23.
Compilation failed in require at /opt/webwork/webwork2/lib/WeBWorK/PG/Local.pm line 45.
BEGIN failed--compilation aborted at /opt/webwork/webwork2/lib/WeBWorK/PG/Local.pm line 45.
Compilation failed in require at (eval 485) line 1.

Call stack

The information below can help locate the source of the problem.

  • in WeBWorK::Utils::runtime_use called at line 50 of /opt/webwork/webwork2/lib/WeBWorK/PG.pm
  • in WeBWorK::PG::new called at line 242 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator/ProblemSet.pm
  • in WeBWorK::ContentGenerator::ProblemSet::info called at line 152 of /opt/webwork/webwork2/lib/WeBWorK/Template.pm
  • in WeBWorK::Template::template called at line 480 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm
  • in WeBWorK::ContentGenerator::content called at line 188 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm
  • in WeBWorK::ContentGenerator::go called at line 338 of /opt/webwork/webwork2/lib/WeBWorK.pm

Request information

Method GET
URI /webwork2/muohio_mth153h/3pt7plus/
HTTP Headers
Keep-Alive 300
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
User-Agent Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: Gecko/20070725 Firefox/
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Connection keep-alive
Referer http://webwork.muohio.edu/webwork2/muohio_mth153h/
Accept-Encoding gzip,deflate
Accept-Language en-us,en;q=0.5
Cookie SaneID=
Host webwork.muohio.edu

In reply to Dennis Keeler

Re: constituency_hash error

by Gavin LaRose -
Hi Dennis,

That seems like an odd error to me. It looks as if there's something weird with how the Utils.pm file in your distribution is being pulled down from the CVS. The version of the file in the 2.3.2 branch of the code appears to include constituency_hash, which makes it seem strange that you are getting the error you report.

Can you try getting a new version of that file to make sure that you have the version that is expected for the 2.3.2 branch? The brute force way that I'd try that would be by moving the file that you have and then doing an update from the cvs (e.g., cd /opt/www/webwork2/lib/WeBWorK/; mv Utils.pm Utils.pm.bak; cvs up;). With any luck that should get a new (clean) copy of Utils.pm, and restarting the apache server thereafter will solve the problem.

In reply to Gavin LaRose

Re: constituency_hash error

by Dennis Keeler -
Thanks for the advice. It's hard to say what was going wrong. My server got so messed up, I couldn't even SSH to it. I had to wait until I was back at work to reboot it. Now everything seems to work fine.

I didn't follow Gavin's advice exactly, but I did a CVS update from rel-2-3-dev before rebooting. That didn't touch Utils.pm, but maybe something else got fixed. Or maybe I just needed to reboot after upgrading. I didn't even restart Apache the first time around, though I should have thought of that.

Perhaps the upgrade instructions should mention that rel-2-3-dev is the preferred option (the new install instructions do; saw that tip later). If Apache needs to be restarted, that could be mentioned also. I was too anxious to look at the new problems, so I didn't think to do any restarts. Also, I don't use Apache enough to remember the command off the top of my head, but I saw it mentioned elsewhere.

Thanks again! -Dennis