When WordPress.Org releases new update to it’s WordPress standalone CMS (Content Management System) for that you may have set your website to get your installation updated automatically or you may like to do it your self at your preferred time. What ever case may be.
But because of server load on part of your web host you may get error something like this with screwed up blank website with following error printed on 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
Real cause of above errors:
Above mentioned errors are generated because of interrupted WordPress updates mostly because of heavy load on your web host’s online server. As update fails all files mismatch with consistent version number so some old source files remains as it is & only remaining few get updated with new version. So it is 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’)
Continue Reading Post