Our Webwork server is back running again.
Following your suggestions, I deleted /opt/webwork/webwork2/logs/timing.log that was about 190 Mb in size. That didn't solve the issue. But just in case, I created the configuration file for timing.log in logrotate.
The latest installation of the server has option A implemented that removes temporary files (pdf, images, etc) with a cron job. Not something that would solve the issue neither.
I found out that the /opt/webwork/webwork2/logs/debug.log was huge, 97Gb in size. It was turned on because of another issue that I reported in February (https://webwork.maa.org/moodle/mod/forum/discuss.php?d=4955#p16130).
Following your suggestions, I deleted /opt/webwork/webwork2/logs/timing.log that was about 190 Mb in size. That didn't solve the issue. But just in case, I created the configuration file for timing.log in logrotate.
The latest installation of the server has option A implemented that removes temporary files (pdf, images, etc) with a cron job. Not something that would solve the issue neither.
I found out that the /opt/webwork/webwork2/logs/debug.log was huge, 97Gb in size. It was turned on because of another issue that I reported in February (https://webwork.maa.org/moodle/mod/forum/discuss.php?d=4955#p16130).
After deleting debug file, I was able to restart the database and Webwork is running again.
I still plan to keep the debug on for a bit longer, just in case, because of the other issue above reported in the forum. I also configured file in logrotate for the debug to keep compressed weekly backups of the debug for up to 4 weeks to avoid the file to become so big as before.
I also requested our college IT to increase the disk space in the Virtual Machine for the server. Probably, IT will do it tomorrow morning.
Thank you so much for all the help.