Missed your second question. Aren't HDDs effectively dead and gone?
Howard Miller
Posts made by Howard Miller
Do you mean 50GB storage for the whole VM or just for 'moodledata'?
The VMs I use for development with (almost) NO users, have twice that disk space and I'm using a reasonable percentage of it.
At the end of the day, nobody can tell you how much disk space you are going to use. But... given how (relatively) cheap it is, 50GB seems pretty miserable. Especially, the pain and hassle you can get into if you run out.
The VMs I use for development with (almost) NO users, have twice that disk space and I'm using a reasonable percentage of it.
At the end of the day, nobody can tell you how much disk space you are going to use. But... given how (relatively) cheap it is, 50GB seems pretty miserable. Especially, the pain and hassle you can get into if you run out.
Also, and I'm sorry to be the voice of doom, 200 concurrent users all doing a quiz is quite an ask. A single quad core processor probably isn't going to cut that. I'd rather have more ram, too. However, I'd first ask you to justify how you calculated the 200 figure. Getting that wrong is either getting you a system that doesn't work or costing you lots of money.
I'm not sure what it is. If I could tell you the solution I would. If, as you say, you replaced the Moodle code with the clean copy then that would eliminate some form of code corruption.
Why do you suspect database corruption? There's nothing in the errors you sent earlier to suggest that. To be anyway.
If you haven't already, you should definitely clear caches. This might clear up some of the template issues.
Why do you suspect database corruption? There's nothing in the errors you sent earlier to suggest that. To be anyway.
If you haven't already, you should definitely clear caches. This might clear up some of the template issues.
There's nothing in the errors you have posted here to suggest a DB problem. You can't install a plugin twice. It's just not possible.
None of this means that your database is NOT somehow corrupt, of course.
None of this means that your database is NOT somehow corrupt, of course.
I'm hoping somebody else comes along with a better idea. I'm struggling to think what to suggest.
PS. I deleted your other post. PLEASE do not post multiple times about the same problem.
Not easily.
I don't know what you have done, but I think you've probably corrupted the code, somehow.
I would think about...
- take a complete backup.
- download completely new/clean 3.6.10 code
- replace your existing suspect code
If it works.... then consider 'marching' to the current version. But that's going to be another story.
I don't know what you have done, but I think you've probably corrupted the code, somehow.
I would think about...
- take a complete backup.
- download completely new/clean 3.6.10 code
- replace your existing suspect code
If it works.... then consider 'marching' to the current version. But that's going to be another story.