Background:
When WordPress.Org releases a new update to its WordPress standalone CMS (Content Management System), you may have set your website to get your installation updated automatically, or you may like to do it yourself at your preferred time.
But because of server load on the part of your web host, you may get an error something like this with a screwed-up blank website with the following error printed on the screen:
Warning: require(/nfs/domains/your-domain-name.com/html/wp-includes/session.php) [function.require]: failed to open stream: No such file or directory in /nfs/domains/your-domain-name.com/html/wp-settings.php on line 122
Fatal error: require() [function.require]: Failed opening required '/nfs/domains/your-domain-name.com/html/wp-includes/session.php' (include_path='.:/usr/local/php-5.3.27/share/pear') in /nfs/domains/your-domain-name.com/html/wp-settings.php on line 122
The actual cause of the above errors:
As mentioned, errors are generated because of interrupted WordPress updates, primarily because of heavy load on your web host’s online server. As the update fails, all files mismatch with consistent version numbers, so some old source files remain as it is & only the remaining few get updated with the new version. So, it is a problem of source code version consistency.
How to fix this:
Error 01: [function.require]: failed to open stream: No such file or directory in
Error 02: Fatal error: require() [function.require]: Failed opening required & (include_path=’.:/usr/local/php-5.3.27/share/pear’)
(more…)