Visvanath Ratnaweera

Read https://docs.moodle.org/dev/Releases and decide to which version.

The upgrading routinge is documented here: https://docs.moodle.org/23/en/Upgrading.

I don't know the connection to 64 years, 64 bit systems are common though.

Hi

You have a configuration issue. The question is, Where?

Start with the two Apache errors:
1. Create a simple index.html in the moodle directory and visit your Moodle site. As a safety measure move the index.php there to a safe place. You should get the HTML displayed.

2. Once that works, get the PHP info displayed: https://docs.moodle.org/en/PHP#Displaying_phpinfo_in_Moodle. Go through it checking the values of important parameters.

P.S. When you repeat the installation procedure by deleting the config.php, you cleaned the moodledata directory completely and dropped/recreated the database, right?

Hi Frank

You wrote:
> I got to the part to copy and create the /var/www/html/moodle.config.php ...

Is that a typo? Expected /var/www/html/moodle/config.php.

I don't know the video. Have you checked the docs, https://docs.moodle.org/en/Step-by-step_Installation_Guide_for_Ubuntu, for example?

Hi Howard

The advocacy part was intention. [What would you expect if you start a discussion by just saying that the Linux performance is dodgy?]
;-P

To the OP, see https://moodle.org/mod/forum/discuss.php?d=312419#p1256208.

Seriously, I didn't say that the problem is Windows. [How could I, before the root cause was found and eliminated? See the pointer to file systems.] It could well be the Windows philosophy. For any problem start with throwing resources at random, for example. Either Windows don't allow the kind of debugging which an Open and command line oriented System like Linux allows, or the amateur Windows sysadmin doesn't know how (or does't have the meter long MS*** course material in their shelves).

Hi Mike

I don't touch Windows servers, clients only if have to. Still trying to look at the problem from first principles.

You wrote:
> Linux machine however, we found really dodgy performance ...

Could you publish the evidence? The https://docs.moodle.org/en/Performance_recommendations says otherwise: "You can use Linux(recommended), Unix-based, Windows or Mac OS X for the server operating system. *nix operating systems generally require less memory than Mac OS X or Windows servers for doing the same task as the server is configured with just a shell interface." [Whether it is due to the missing GUI is a different question.]

> You hit the nail on the head as it is a VM but we added some significant resources. It has 2 2.5 GHz CPUs, 4 gbs of RAM on a 64 bit Windows server 2008 R2 operating system. We also upped the NIC card bandwidth from 1gps to 10gps.

Where did you notice a clear improvement? That is most likely the bottleneck. You might need to add more of that resource.

> We found the when users logged in cpu usage never climbed above 15%. Processes were still running.

So the CPU wasn't the bottleneck?

> All the sessions from users that logged on at the same time would freeze up and they would be forced to close their browsers and log back in. However, someone could log in individually during that time and not experience any issues.

That sounds more like a file system issue. What are the file systems in use? You know that (desktop) virtualisation has a bad reputation in this aspect?

> We tried different browsers, have used hard top boxes and vm workstations and monitored the server when the error occurred.

Aren't those on the client side?