## Forum archive 2000-2006

### Gavin LaRose - httpd error log entries

by Arnold Pizer -
Number of replies: 0
 httpd error log entries topic started 9/24/2002; 8:11:46 AMlast post 9/25/2002; 2:41:04 AM
 Gavin LaRose - httpd error log entries  9/24/2002; 8:11:46 AM (reads: 1025, responses: 2) Hi all, I'm seeing some "interesting" entries in my httpd error log which appear to be caused by WeBWorK script calls. Can anyone tell me if these are a result of (1) my poor system set-up, or (2) known or unknown bugs? Thanks, Gavin Errors seen: getCourseEnvironment was called without specifying a course at /opt/www/webwork/system/lib/Global.pm line 526. [Tue Sep 17 01:34:40 2002] Caught a SIGPIPE, Error: Illegal seek stopped at opt/www/http/cgi-bin/webwork-cgi/cgi-scripts/welcomeAction.pl [Tue Sep 17 08:56:37 2002] Caught a SIGPIPE, Error: Illegal seek stopped at /opt/www/http/cgi-bin/webwork-cgi/cgi-scripts/processProblem8.pl Use of uninitialized value in concatenation (.) or string at /opt/www/webwork/system/lib/Global.pm line 747. <| Post or View Comments |>

 Zbigniew Fiedorowicz - Re: httpd error log entries  9/25/2002; 2:36:50 AM (reads: 1258, responses: 0) Gavin, I believe that most errors of the first type are caused by the client browser deciding (sometimes capriciously) to forget because it thinks this information is stale. Another possible cause is deep bookmarking by the student trying to avoid the login page. I believe most SIGPIPEs are due to students impatiently clicking on the SUBMIT button twice. I don't worry about this, unless there is a dramatic upsurge in SIGPIPEs, which might indicate that the web server is getting overloaded, network congestion or similar things. The last one might be due to some carelessness in coding of some WeBWorK script or problem. It might also be due to forgetfulness by the client browser, like the first problem. Zig <| Post or View Comments |>

 Zbigniew Fiedorowicz - Re: httpd error log entries  9/25/2002; 2:41:04 AM (reads: 1204, responses: 0) Gavin, (Sorry about the previous message, which contained some HTML that the discussion board editor ate.) I believe that most errors of the first type are caused by the client browser deciding (sometimes capriciously) to forget INPUT TYPE="HIDDEN" NAME="course" VALUE="math153au02sk" because it thinks this information is stale. Another possible cause is deep bookmarking by the student trying to avoid the login page. I believe most SIGPIPEs are due to students impatiently clicking on the SUBMIT button twice. I don't worry about this, unless there is a dramatic upsurge in SIGPIPEs, which might indicate that the web server is getting overloaded, network congestion or similar things. The last one might be due to some carelessness in coding of some WeBWorK script or problem. It might also be due to forgetfulness by the client browser, like the first problem. Zig <| Post or View Comments |>