** Using WeBWorK **

I just upgraded our WeBWorK server to 2.18 and I'm running into an interesting problem.  Sometimes, when a page is loaded, the links to the CSS files give me 404 errors since they're not pointing to the minified versions with the hashes in the filenames.  For example:

<link href="/webwork2_files/themes/math4-green/bootstrap.css" rel="stylesheet">

But after refreshing (sometimes several times), I finally get the correct link, e.g.,:

<link href="/webwork2_files/themes/math4-green/bootstrap.4be740be.min.css" rel="stylesheet">

I tried clearing my browser's cache, but that didn't help.  Any thoughts?

Thanks!

Logging in as admin, the Course Administration page shows links for dealing with courses.

Click on Delete Course or Archive Course and the default "select listing format" is shown as alphabetical and the courses are indeed listed alphabetically.

But click on Hide Courses and the default "select listing format" is still shown as alphabetical but the courses are listed by last login date. Need to click "refresh listing" to get them in alphabetical order.

You really shouldn't paste the code into knowl.xxxxxxxx.min.js.  Instead you should paste it into knowl.js.  Then run "npm ci" in the pg/htdocs directory.  That will generate a new knowl.xxxxxxxx.min.js file with the updated contents with a new xxxxxxxx hash.  Make sure to restart apache2 so that it loads the updated static-assets.json file.  This way your users will not need to do a hard refresh in their browsers to get the updated content.  If you change knowl.xxxxxxxx.js directly they will need to do that, or the browser will use the cached file.

In addition, by changing knowl.js and running "npm ci", the javascript is minimized.  This reduces the size of the file and saves bandwidth for your users.

Hi, I've got a little more info now on this issue.  I did a new test today.  I opened a test at 3:07:07, with a 3 minute time limit, and simply let the test stay open.  At around 3:12 -- right when the auto submit should take place -- I noticed that the icon in my browser tab looked like it started refreshing repeatedly.  Sure enough, in the server log, there are records of POST requests each second from 3:12:02 to 3:12:07 (at which time I logged out of WW, to thwart another crash).

From the last actual crash, the server log shows that there was an out-of-memory kill.

So it sounds a little like WeBWorK auto-submit is trying to submit over and over again.  Apologies if this is misleading or unhelpful info, but if I'm right, could you imagine any reason why that might be happening?  Thanks again!

Hello Everyone

This is my first post to the forum.  We run multiple instances of WW, one instance per member College, and each instance lives on a dedicated VM.  We're running WW 2.15 on RHEL8 and users access the server through a F5 load balancer, though with one server per site we aren't actually doing any load balancing with it.  The F5 just takes care of public-facing SSL and IP. 

The setup has been stable for some time, but we recently started seeing an error when using the file manager.  I can click on File Manager without issue, but clicking on anything in the file list, whether directory or file, generates this error:

WeBWorK error

An error occured while processing your request. For help, please send mail to this site's webmaster, including all of the following information as well as what what you were doing when the error occured.

Wed Sep 21 08:46:23 2022

Warning messages

Error messages

Internal apreq error

Call stack

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

• in Apache2::Request::upload called at line 252 of /opt/webwork/webwork2/lib/WeBWorK.pm

The reason the students get this message is because they are refreshing the page after submitting the answer.

Most likely the student submits the answer, then it takes a long time, and then the student gets impatient and refreshes the page.  That is when they get this issue.

I am not sure what is causing the lag, but the message is not related.  Nor does it help in diagnosing the issue unfortunately.

This was a bug in previous versions of webwork.  The only fix is to update to WeBWorK 2.17 in which this bug is fixed.

Although you should also note that even with the bug fixed, refreshing the page immediately after logging in probably will not do what you expect.  When you refresh a page the browser resubmits the last request.  If you just logged in via LTI authentication, then the last request would be the request from the LMS containing the authentication parameters.  Since those will no longer be valid for another request what will happen is you will get the message that your authentication failed.

Hello,

I ran into a weird problem that occurs after logging into a course on webwork. After logging in, if I refresh the page I get the Error:

"Failed to validate Service Ticket ST-243968-tCQCVnarEWAnKGOh93504Frm2K8-cas4 : Ticket 'ST-243968-tCQCVnarEWAnKGOh93504Frm2K8-cas4' not recognized

The course PETRY-888-TEST uses an external authentication system (). You've authenticated through that system, but aren't allowed to log in to this course."

If I do not refresh the page I can navigate around the course page as expected. It is only if I do a refresh as my first action after logging into the course. If i navigate somewhere then refresh it will refresh normally with no errors. 

I am using CAS for the instructors that are logging into their course pages.



A similar problem arises for the students that access web work via external tool on Moodle. If the students click on the link it takes them to the webwork site using LTI to create their account and log them in. But if the student refreshes the page immediately after getting to webworks an error page comes up saying: 

"

Error record identifier

94b42b0d-0686-5865-bf90-d928862fea60::232b3aad-172c-11ed-b167-c4965dc31cb6

Warning messages

Error messages

Can't locate object method "put" via package "WeBWorK::DB" at /opt/webwork/webwork2/lib/WeBWorK/Authen/LTIAdvanced.pm line 811.

Any help would be appreciated.