WeBWorK Main Forum

WeBWorK giving warning messages

WeBWorK giving warning messages

by Larry Riddle -
Number of replies: 4
Trying to log into a WeBWorK course as admin gives the following warning messages

WeBWorK Warnings

WeBWorK has encountered warnings while processing your request. If this occured when viewing a problem, it was likely caused by an error or ambiguity in that problem. Otherwise, it may indicate a problem with the WeBWorK system itself. If you are a student, report these warnings to your professor to have them corrected. If you are a professor, please consult the warning output below for more information.

Warning messages

  • failed to open /opt/webwork/courses/Math295_S18/logs/login.log for writing: Read-only file system at /opt/webwork/webwork2/lib/WeBWorK/Utils.pm line 784.
  • Difficulty adding key for userID admin: DBD::mysql::st execute failed: File './webwork/Math295_S18_key.MYD' not found (Errcode: 30) at /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm line 826.
  • at /opt/webwork/webwork2/lib/WeBWorK/Authen.pm line 740.
  • Couldn't put key for userid admin either: DBD::mysql::st execute failed: File './webwork/Math295_S18_key.MYD' not found (Errcode: 30) at /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm line 826.
  • failed to open /opt/webwork/courses/Math295_S18/logs/login.log for writing: Read-only file system at /opt/webwork/webwork2/lib/WeBWorK/Utils.pm line 784.
Trying to log into a difference courses results in the following warnings

Warning messages

Error messages

DBD::mysql::st execute failed: File './webwork/Math118_S18_key.MYD' not found (Errcode: 30) at /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm line 826.

Call stack

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

  • in WeBWorK::DB::Schema::NewSQL::Std::handle_error called at line 413 of /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm
  • in WeBWorK::DB::Schema::NewSQL::Std::_get_fields_where_prepex called at line 381 of /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm
  • in WeBWorK::DB::Schema::NewSQL::Std::get_fields_where called at line 441 of /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm
  • in WeBWorK::DB::Schema::NewSQL::Std::get_records_where called at line 741 of /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm
  • in WeBWorK::DB::Schema::NewSQL::Std::gets called at line 767 of /opt/webwork/webwork2/lib/WeBWorK/DB.pm
  • in WeBWorK::DB::getKeys called at line 762 of /opt/webwork/webwork2/lib/WeBWorK/DB.pm
  • in WeBWorK::DB::getKey called at line 760 of /opt/webwork/webwork2/lib/WeBWorK/Authen.pm
  • in WeBWorK::Authen::check_session called at line 519 of /opt/webwork/webwork2/lib/WeBWorK/Authen.pm
  • in WeBWorK::Authen::verify_normal_user called at line 306 of /opt/webwork/webwork2/lib/WeBWorK/Authen.pm
  • in WeBWorK::Authen::do_verify called at line 216 of /opt/webwork/webwork2/lib/WeBWorK/Authen.pm
  • in WeBWorK::Authen::verify called at line 321 of /opt/webwork/webwork2/lib/WeBWorK.pm

Request information

Method POST
URI /webwork2/Math118_S18/
HTTP Headers
Cookie __utma=87823112.2116505278.1369839979.1510333481.1510591624.155; __utmz=87823112.1510333481.154.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.2.2116505278.1369839979
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Accept-Language en-US,en;q=0.9
Content-Length 247
Upgrade-Insecure-Requests 1
Origin http://webwork.agnesscott.edu
Accept-Encoding gzip, deflate
Content-Type multipart/form-data; boundary=----WebKitFormBoundaryKhwWPFxlMf9fu8Lx
Accept text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Referer http://webwork.agnesscott.edu/webwork2/Math118_S18/
Connection keep-alive
Host webwork.agnesscott.edu
Cache-Control max-age=0

Can anyone suggest what might be causing this and possible fixes? Thanks.

Larry Riddle

In reply to Larry Riddle

Re: WeBWorK giving warning messages

by Michael Gage -
These look like permissions problems.

The first error about the log file is definitely a permission problem. The webserver needs to be able to write to the file logs/login.log.

You can check the permissions on that file from the command line.

The other errors appear to be database failures.

Have you recently updated or
rebuilt your database or your webwork system?

Does the fact that the warning message claims that the file system is read only suggest any recent changes?

In reply to Michael Gage

Re: WeBWorK giving warning messages

by Larry Riddle -
We have made no changes to Webwork since updating to version 2.13 last summer. It was working fine yesterday (Monday) afternoon. I first noticed the problem Monday evening when trying to check student progress on a homework assignment.

I'm trying to check the permissions, but for some reason when I try to connect to our webwork (virtual) server, the connection is being refused. Have an email in to our ITS network manager about why that is happening.

In reply to Michael Gage

Re: WeBWorK giving warning messages

by Danny Glin -
If the file system as a whole is read only, then it is probably not a permissions issue.

According to a quick google search, the file system can be pushed into read-only mode if there are consistency issues with the file system. This can be caused by a variety of different things, including a failing hard drive.

Check to see if the disk is full (run `df -h` to show free space). I'd also try rebooting to see if that clears it up. You can run `dmesg` to see if the system logs give you any more info as to what caused the system to become read only.
In reply to Danny Glin

Re: WeBWorK giving warning messages

by Larry Riddle -
Turned out to be a misbehaving server that had somehow ended up in an indeterminate state. Rebooting the server did in fact clear up all the problems and Webwork is back to running properly.