Hello all,
We are having an issue with our WeBWorK server where if you go to a course, access an assessment and view a question, an error page shows up which isn't always the same. See attached screenshot of one error page.
Here is some of the stuff that shows up in the Apache error log:
[Thu Sep 01 21:08:18 2011] [error] [client] [/webwork2/FMTH201E/HH_Precalc2/3/] Software caused connection abort at /opt/webwork/webwork2/lib/WeBWorK/ContentGen
erator/Problem.pm line 1135.\n * in WeBWorK::ContentGenerator::Problem::body called at line 152 of /opt/webwork/webwork2/lib/WeBWorK/Template.pm\n * in WeBWorK::Template::t
emplate called at line 491 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::content called at line 195 of /opt/webwork/webwork2/li
b/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::go called at line 353 of /opt/webwork/webwork2/lib/WeBWorK.pm, referer: https://webwork.up.edu/webwork2/FMTH
201E/HH_Precalc2/3/
:Apache2 IO flush: (103) Software caused connection abort at -e line 0Use of uninitialized value in concatenation (.) or string at (eval 35339) line 109, <MACROFILE> chunk
1.
[Thu Sep 01 21:11:42 2011] [error] [client] File does not exist: /var/www/html/crossdomain.xml
Subroutine max redefined at (eval 37903) line 58, <MACROFILE> chunk 1.
Subroutine min redefined at (eval 37903) line 72, <MACROFILE> chunk 1.
Subroutine max redefined at (eval 38139) line 58, <MACROFILE> chunk 1.
Use of uninitialized value in concatenation (.) or string at (eval 3359) line 109, <MACROFILE> chunk 1.
[Fri Sep 02 02:06:19 2011] [error] [client] [/webwork2/FMTH201E/HH_Precalc3/6/] Software caused connection abort at /opt/webwork/webwork2/lib/WeBWorK/ContentGen
erator/Problem.pm line 1314.\n * in WeBWorK::ContentGenerator::Problem::body called at line 152 of /opt/webwork/webwork2/lib/WeBWorK/Template.pm\n * in WeBWorK::Template::t
emplate called at line 491 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::content called at line 195 of /opt/webwork/webwork2/li
b/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::go called at line 353 of /opt/webwork/webwork2/lib/WeBWorK.pm, referer: https://webwork.up.edu/webwork2/FMTH
201E/HH_Precalc3/6/
:Apache2 IO flush: (103) Software caused connection abort at -e line 0
[Fri Sep 02 02:12:51 2011] [warn] [client 10.10.1.] [/webwork2/FMTH201E/HH_Precalc3/3/] Timeout afte
r processing this problem for 60 seconds. Check for infinite loops in problem source., referer: https://webwork.up.edu/webwork2/FMTH201E/HH_Precalc3/3/
If an error page shows up, it's remedied by hitting the back button and trying to view the problem again. Sometimes it takes up to 2 or 3 tries to get the page to load correctly.
Anyone have any ideas as to what might be causing this?
Thanks!
Tony
Hi Tony,
Because this is an intermittent problem the first thing I would do is make sure that I have a fresh start on the server. An intermittent problem can mean that most of the child processes serving web requests are working fine, but one of them is not and it causes errors whenever it is chosen to handle the request.
So turn off the apache server and use "top" or "ps" to check the processes and make sure that all the httpd processes have stopped. You might have to kill some of them manually if they refuse to stop.
Then restart the server and whether these errors reoccur. In general the errors sound like difficulties with the server software, perhaps a child with a memory leak, rather than webwork specifically. If Parser.pm were really not available you would get that message every time.
Hope this helps. Let us know how things turn out.
-- Mike
Because this is an intermittent problem the first thing I would do is make sure that I have a fresh start on the server. An intermittent problem can mean that most of the child processes serving web requests are working fine, but one of them is not and it causes errors whenever it is chosen to handle the request.
So turn off the apache server and use "top" or "ps" to check the processes and make sure that all the httpd processes have stopped. You might have to kill some of them manually if they refuse to stop.
Then restart the server and whether these errors reoccur. In general the errors sound like difficulties with the server software, perhaps a child with a memory leak, rather than webwork specifically. If Parser.pm were really not available you would get that message every time.
Hope this helps. Let us know how things turn out.
-- Mike