2

We have some many error lines on httpd error log, about 10-15 errors for every day, on different time:

PHP Warning:  include(Mage.php): failed to open stream: No such file or directory in /var/www/html/lib/Varien/Autoload.php on line 94
...
PHP Fatal error:  Class 'Mage' not found in /var/www/html/app/code/core/Mage/Core/functions.php on line 244
...
PHP Fatal error:  Class 'Mage' not found in /var/www/html/app/code/core/Mage/Core/Model/Resource/Session.php on line 108

Any error not found related to the issue on Magento logs. Some times some customers cannot be login, is it result of the issue given above?

It seems these errors appeared after upgrading EE 1.13.1 to EE 1.14.1 month ago. Followed this one, but we have some difficulties to catch error as this error is only on live instance. Magento instance status:

  • Uses Redis for session, cache and fpc
  • Uses load balancer
  • about 2000 SKUs
  • about 20000 visits per day
  • Compilation mode is off

Issue is not permanent, it is available only some times (maybe peak time of the day)

Any help will be appreciated.

Update

Unknown and strange thing is I have set full permission to var folder (chmod 777 -R var/*) and issue has gone away. But var directory was be available for web-server user and group: magento logs, magento-connect, system backup was worked perfectly as a fact of valid permission of the folder. Consider this change while giving some diagnose.

|improve this question
2
+100

I remember debugging a similar issue and it happened sometimes when the session was written during script shutdown from the destructor of the session model.

For some reason the Mage class was already unloaded at this time, so the autoloader tries to load Mage.php which is not in the include path (it gets explicitly required in index.php).

Unfortunately the problem solved itself mysteriously in my case and I still don't know how this class unloading could happen, it might have been a bug in PHP.

But closing the session explicitly with session_write_close() at the end of index.php might be a workaround.

|improve this answer
2

Ask your hosting provider if they have any logs about the I/O, it seems the file system is unavailable from time to time and the Mage.php file is inaccessible. Second error might be related to the first one.

|improve this answer
  • Hosting is at the reputed provider with SSD drive, and issue is not permanent – mageUz Jan 22 '15 at 9:06
  • This issue could be not permanent if it's caused high server (presumably I/O) load, which could happen from time to time. – DmitryR Jan 22 '15 at 9:58
  • Since the issue is not permanent it might be happening during I/O spikes. I really suggest you to ask our hosting provider about this. – mbalparda Jan 22 '15 at 11:03
0

I'd leave this as a comment, but reputation doesn't allow that.

I suggest checking the permissions on the Autoload.php file and make sure that it is readable by the Webserver.

Additionally are you running with compilation enabled? I suggest recompiling if so.

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.