Thanks, that worked. 1000 was not enough, but 1500 did the trick.
This has come back to haunt me. I upgraded the Jobe Server (to Ubuntu 24.04), and the version of mongosh. The above error returned. So I increased the memory limit to 1600. I then got:
***Time limit exceeded***
So I increased TimeLimit to 15. When I did this, Moodle threw me out with a 404 error. This MAY be an issue with our Moodle configuration/set-up, but our technical support could not find anything suspicious in the logs. Is there anything else I can try?
Thanks,
Mark Stern
***Time limit exceeded***
So I increased TimeLimit to 15. When I did this, Moodle threw me out with a 404 error. This MAY be an issue with our Moodle configuration/set-up, but our technical support could not find anything suspicious in the logs. Is there anything else I can try?
Thanks,
Mark Stern
The time limit error is likely spurious - I've seen such errors result from the memory limit being too low. Possibly the system is looping trying to allocate memory.
404 errors occur if file uploads to jobe fail. Dioes the question or its prototype have support files? It's possible that the 404 is also a memory limit issue though I haven't seen that before.
Certainly the first thing to try is setting the memory limit to 0, just for testing purposes. Then, if 404s persist, confirm that it's a file upload problem by running a question without support files.
File uploads will fail if Moodle security settings or network components like firewalls are disallowing HTTP PUT requests.
404 errors occur if file uploads to jobe fail. Dioes the question or its prototype have support files? It's possible that the 404 is also a memory limit issue though I haven't seen that before.
Certainly the first thing to try is setting the memory limit to 0, just for testing purposes. Then, if 404s persist, confirm that it's a file upload problem by running a question without support files.
File uploads will fail if Moodle security settings or network components like firewalls are disallowing HTTP PUT requests.
Thanks. Setting the memory limit to 0 did not help, and there are no support files. I do not know what the problem was, but it is moot.
The new version of mongosh lets me specify a file as input, and it then behaves very differently than in interactive mode. So I re-wrote the template taking advantage of this. I also had to tweak the tests to work with the new template. It is now a lot simpler and it works.
The new version of mongosh lets me specify a file as input, and it then behaves very differently than in interactive mode. So I re-wrote the template taking advantage of this. I also had to tweak the tests to work with the new template. It is now a lot simpler and it works.
Good to know. Well done on beating it into submission.