Content-type: text/html
Software error
Unable to create sub named "Safe::Root2::_PG_init" at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm line 535.
eval {...} called at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm
line 535 WeBWorK::PG::Translator::unrestricted_load called at
/usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 362
main::displayProbSet called at
/usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 181 Please inform the webwork meister.
In addition to the error message above the following warnings were detected:
;
It's sometimes hard to tell exactly what has gone wrong since the full
error message may have been sent to standard error instead of to
standard out. To debug you can
- guess what went wrong and try to fix it.
- call the offending script directly from the command line of unix
- enable the debugging features by redefining $cgiURL in
Global.pm and checking the redirection scripts in system/cgi. This will
force the standard error to be placed in the standard out pipe as well.
- Run tail -f error_log
from the unix command line to see
error messages from the webserver. The standard error output is being
placed in the error_log file for the apache web server. To run this
command you have to be in the directory containing the error_log or
enter the full path name of the error_log. In a standard apache installation, this file is at /usr/local/apache/logs/error_log
In a RedHat Linux installation, this file is at /var/log/httpd/error_log
At Rochester this file is at /ww/logs/error_log.
Good luck.
Content-type: text/html
Software error
Unable to create sub named "Safe::Root2::_dangerousMacros_init" at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm line 535.
eval {...} called at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm
line 535 WeBWorK::PG::Translator::unrestricted_load called at
/usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 363
main::displayProbSet called at
/usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 181 Please inform the webwork meister.
In addition to the error message above the following warnings were detected:
* Use of uninitialized value in concatenation (.) or string at /usr/local/webwork/system/lib//Global.pm line 903.
##More details:
-------- Global::__ANON__ called at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm line 535
---- WeBWorK::PG::Translator::unrestricted_load called at /usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 362
---- main::displayProbSet called at /usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 181
--------------------------------------
* Use of uninitialized value in subroutine dereference at /usr/local/webwork/system/courseScripts//WeBWorK/PG/Translator.pm line 537.
##More details:
--------
WeBWorK::PG::Translator::unrestricted_load called at
/usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 362
---- main::displayProbSet called at /usr/local/webwork/system/cgi/cgi-scripts/welcomeAction.pl line 181
--------------------------------------
;
It's sometimes hard to tell exactly what has gone wrong since the full
error message may have been sent to standard error instead of to
standard out. To debug you can
- guess what went wrong and try to fix it.
- call the offending script directly from the command line of unix
- enable the debugging features by redefining $cgiURL in
Global.pm and checking the redirection scripts in system/cgi. This will
force the standard error to be placed in the standard out pipe as well.
- Run tail -f error_log
from the unix command line to see
error messages from the webserver. The standard error output is being
placed in the error_log file for the apache web server. To run this
command you have to be in the directory containing the error_log or
enter the full path name of the error_log. In a standard apache installation, this file is at /usr/local/apache/logs/error_log
In a RedHat Linux installation, this file is at /var/log/httpd/error_log
At Rochester this file is at /ww/logs/error_log.
Good luck.
WeBWorK assignment number 0 is due 1/1/05 at 2:00 AM.
This first problem set (set 0) is designed to acquaint you with
using WeBWorK. YOUR SCORE ON THIS SET WILL NOT BE COUNTED TOWARD YOUR
FINAL GRADE. In addition to doing the screen problems, practice getting
a hard copy print out of the problem set. You probably won't need it
for this problem set, but you may in the future. If you need software
installed on your own computer look here .
The primary purpose of WeBWorK is to let you know if you are
getting the right answer or to alert you if you get the wrong answer.
Usually you can attempt a problem as many times as you want before the
due date. However, if you are having trouble figuring out your error,
you should consult the book, or ask a fellow student, one of the TA's
or your professor for help. Don't spend a lot of time guessing -- it's
not very efficient or effective. You can use the Feedback button on each problem page to send e-mail to the professors.
Give 4 or 5 significant digits for (floating point) numerical
answers. For most problems when entering numerical answers, you can if
you wish enter elementary expressions such as 2^3 instead of 8,
sin(3pi/2) instead of -1, e^(ln(2)) instead of 2,
(2+tan(3))*(4-sin(5))^6-7/8 instead of 27620.3413, etc. Here's the list of the functions which WeBWorK understands. | 