Error log record number

“If anything can go wrong, it will certainly give” – Murphy’s Law

Since error is inevitable, we must learn to deal with it. And the best way to solve a problem is to identify its cause. It may seem obvious in this way, but there are many people who are concerned with treating only the symptoms and their side effects, thus neglecting their origins.

Let’s see in this post how Magento creates the log files, and how we can interpret the generated information.

Until version 1.3.2.4, whenever the system presented an unexpected problem, it was sent to the browser, thus exposing all fragility of the site to whoever was browsing.

That way you had two problems. The unexpected error, and a breach in security that could be exploited by some hacker on duty.

Starting with version 1.4.x, Magento presented improvements in the handling of errors.

There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 1000038750

Well, summarizing the error message is not quite the improvement that everyone expected, but it lowers the risk of external attacks by exploiting the flaws that caused the problem.

Interpreting the message

Many people think that the problem is identified by the number of the log presented. And they look in the forums and help groups for a solution to the xxx number error. And that’s not how it works. By doing a free and adapted translation of the error page, we will have a message that says:

You fucked up processing your page request
The error will not appear on this page for security.
SEE the log file with number: xxxxxxxxxxx

This number is random, probably based on a chronological counter as a timestamp. This number is only for the file to be located.

Whenever this error screen is displayed, you can find a file (without extension) in your Magento installation directory, in the “var/report/” folder. Just open the file using a text editor.

Identifying the problem

As soon as you open the file, a sequence of information should be displayed. The first glance may seem to be something undecipherable, but with time and some tips you will be able to solve most of them.

a:5:{i:0;s:220:"SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND (stock_id=1)' at line 2";i:1;s:5650:"#0 /Your install directory/lib/Zend/Db/Statement.php(300): Zend_Db_Statement_Pdo->_execute(Array)
#1 /Your install directory/lib/Zend/Db/Adapter/Abstract.php(468): Zend_Db_Statement->execute(Array)
#2 /Your install directory/lib/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('SELECT `catalog...', Array)
#3 /Your install directory/lib/Varien/Db/Adapter/Pdo/Mysql.php(333): Zend_Db_Adapter_Pdo_Abstract->query('SELECT `catalog...', Array)
#4 /Your install directory/lib/Zend/Db/Adapter/Abstract.php(725): Varien_Db_Adapter_Pdo_Mysql->query(Object(Varien_Db_Select), Array)
#5 /Your install directory/app/code/core/Mage/CatalogInventory/Model/Mysql4/Stock/Item.php(53): Zend_Db_Adapter_Abstract->fetchRow(Object(Varien_Db_Select))
#6 /Your install directory/app/code/core/Mage/CatalogInventory/Model/Stock/Item.php(134): Mage_CatalogInventory_Model_Mysql4_Stock_Item->loadByProductId(Object(Mage_CatalogInventory_Model_Stock_Item), Object(Mage_Sales_Model_Quote_Item))
#7 /Your install directory/app/design/adminhtml/default/default/template/sales/order/create/items/grid.phtml(239): Mage_CatalogInventory_Model_Stock_Item->loadByProduct(Object(Mage_Sales_Model_Quote_Item))
#8 /Your install directory/app/code/core/Mage/Core/Block/Template.php(212): include('/Volumes/ Unida...')
#9 /Your install directory/app/code/core/Mage/Core/Block/Template.php(239): Mage_Core_Block_Template->fetchView('adminhtml/defau...')
#10 /Your install directory/app/code/core/Mage/Core/Block/Template.php(253): Mage_Core_Block_Template->renderView()
#11 /Your install directory/app/code/core/Mage/Adminhtml/Block/Template.php(81): Mage_Core_Block_Template->_toHtml()
#12 /Your install directory/app/code/core/Mage/Core/Block/Abstract.php(753): Mage_Adminhtml_Block_Template->_toHtml()
#13 /Your install directory/app/code/core/Mage/Core/Block/Abstract.php(520): Mage_Core_Block_Abstract->toHtml()
#14 /Your install directory/app/code/core/Mage/Core/Block/Abstract.php(467): Mage_Core_Block_Abstract->_getChildHtml('items_grid', true)
#15 /Your install directory/app/design/adminhtml/default/default/template/sales/order/create/items.phtml(32): Mage_Core_Block_Abstract->getChildHtml()
#16 /Your install directory/app/code/core/Mage/Core/Block/Template.php(212): include('/Volumes/ Unida...')
#17 /Your install directory/app/code/core/Mage/Core/Block/Template.php(239): Mage_Core_Block_Template->fetchView('adminhtml/defau...')
#18 /Your install directory/app/code/core/Mage/Core/Block/Template.php(253): Mage_Core_Block_Template->renderView()
#19 /Your install directory/app/code/core/Mage/Adminhtml/Block/Template.php(81): Mage_Core_Block_Template->_toHtml()
#20 /Your install directory/app/code/core/Mage/Adminhtml/Block/Sales/Order/Create/Items.php(67): Mage_Adminhtml_Block_Template->_toHtml()
#21 /Your install directory/app/code/core/Mage/Core/Block/Abstract.php(753): Mage_Adminhtml_Block_Sales_Order_Create_Items->_toHtml()
#22 /Your install directory/app/code/core/Mage/Adminhtml/Block/Sales/Order/Create/Load.php(44): Mage_Core_Block_Abstract->toHtml()
#23 /Your install directory/app/code/core/Mage/Core/Block/Abstract.php(753): Mage_Adminhtml_Block_Sales_Order_Create_Load->_toHtml()
#24 /Your install directory/app/code/core/Mage/Adminhtml/controllers/Sales/Order/CreateController.php(342): Mage_Core_Block_Abstract->toHtml()
#25 /Your install directory/app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_Sales_Order_CreateController->loadBlockAction()
#26 /Your install directory/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('loadBlock')
#27 /Your install directory/app/code/core/Mage/Core/Controller/Varien/Front.php(177): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#28 /Your install directory/app/code/core/Mage/Core/Model/App.php(304): Mage_Core_Controller_Varien_Front->dispatch()
#29 /Your install directory/app/Mage.php(596): Mage_Core_Model_App->run(Array)
#30 /Your install directory/index.php(78): Mage::run('', 'store')
#31 {main}";s:3:"url";s:186:"/Your install directory/index.php/admin/sales_order_create/loadBlock/key/97888fef60b8f8c3ed3d7b6617e17259/block/search,items,shipping_method,totals,giftmessage,billing_method?isAjax=true";s:11:"script_name";s:33:"/Your install directory/index.php";s:4:"skin";s:5:"admin";}

Let’s look at the example above. Magento creates a sequence of events using # to identify every path traveled until the error is encountered.

Being the #31 source, it shows the event (url) that triggered the error. Although it was theoretically obvious information, since you were navigating the moment the error appeared.

What really matters to you is what comes before the #1. This is the message you must interpret. In this example:

a:5:{i:0;s:220:"SQLSTATE[42000]: Syntax error...

If you are a developer, you will quickly understand that this is a SQL error. And in the rest of the message it is still possible to identify the error in more detail.

Now, if you read the first line of the log file and did not understand anything… well, do not be discouraged. Now you know what to look for, and you can request help properly in forums and groups.

Always on alert

A good way to treat problems is by working on their prevention. And the tips below may help.

1. Always have a backup of what is really important. The frequency of generating backups will depend on the flow (quantity) and the (usually financial) importance that this may represent. Backups can be daily, weekly, monthly, bimonthly.

2. Have a testing environment. Magento has several versions of its system, and there are countless modules at your disposal. Do not get carried away by the excitement of having a new module running in your store right away… first make a battery of tests in a simulated environment, and only after you pass it you must homologate it in your store. Take this tip seriously, most problems are caused by incompatible modules.

3. After making changes to configuration files, modules and/or templates, update your system and browser cache. And do not forget to reindex the data whenever Magento requests. It may happen that you apply an inconsistent change and the system does not present a problem immediately because it continues to work with cache files, and months later the problem appears “nothing.”

4. After reading the log file, you no longer need it, you can delete the file from the “var/report/” folder without any problems. But be proactive, do not wait for the problem to come to you. Make it a habit to check this directory from time to time, as a problem may be “discovered” by some site visitors, and not everyone will contact the store to notify you that a shipping problem has occurred.

5. Learn to ask for help. Messages in forums titled “URGENT” will not help. Start by using the search field in the forum with keywords that identify your problem, see if someone has already experienced the same problem and was able to solve it. If not, open a new topic and put a title that is self-explanatory. Your chances of getting help and helping others will only increase.

Success!

Tags: