Magento 1.9 Error – Cause of ‘Front Controller Reached 100 Router Match Iterations’

bugconfigurationerrormagento-1.9router

As a Magento developer I have faced this problem tons of times, I know it is a misconfiguration problem when it occurs some modules are not loaded, neither their routers, causing the error. Most of the times it is solved with no action, other times you may flush the cache

I've read multiple posts about this, trying to debug placing some extra code in Magento core Front controller app/code/core/Mage/Core/Controller/Varien/Front.php, but at the end this only shows which module routers are missing, not why they are not being loaded. Every time it occurs I try to look which URLs are giving the error, but this is useless information, same as the code trace. It's always the same

Maybe it is caused by module conflicts? Maybe it is some cron task doing something wrong? Maybe some wrong code in older Magento versions? The thing is this problem does not occur since 1.7 version (or if it occurs then it is totally sporadic). I have found some code differences in the main flow, such as

Mage::register('application_params', $params);

In run() method of app/code/core/Mage/Core/Model/App.php, or the

$this->_shouldSkipProcessModulesUpdates()

check in _initModules() method…

I want to believe there should be someone who has definitively found the cause. Any tips?

Best Answer

It seems you were experiencing a Magento configuration bug.

There is an excellent write-up with solution here.

In that article the author was able to rectify the bug by overriding Mage_Core_Model_Config and forcing $_useCache = false when regenerating the config.

Related Solutions

Magento 1.9 – 404 Page Front Controller Reached 100 Router Match Iterations

After some time debugging Mage_Core_Controller_Varien_Front, it showed up that it was trying to load a wrong no_route path.

I run the next query:

SELECT * FROM core_config_data where path = 'web/default/no_route';

and I could confirm the value set there was wrong, so I updated to be:

cms/index/noRoute

and everything started working just fine.

References: http://magentoexplorer.com/how-to-debug-and-fix-front-controller-reached-100-router-match-iterations-in-magento

Magento1.9 – Causes of Error Related to ‘dashboard/tunnel/key’

The tunnel action is the action that retrieves the chart data on the dashboard.

As you may know the dashboard chart are generated by Google Chart Api.

As you can see from the method, the tunnel action calls the API URL to generate the chart:

public function tunnelAction()
{
    $httpClient = new Varien_Http_Client();
    $gaData = $this->getRequest()->getParam('ga');
    $gaHash = $this->getRequest()->getParam('h');
    if ($gaData && $gaHash) {
        $newHash = Mage::helper('adminhtml/dashboard_data')->getChartDataHash($gaData);
        if ($newHash == $gaHash) {
            $params = json_decode(base64_decode(urldecode($gaData)), true);
            if ($params) {
                $response = $httpClient->setUri(Mage_Adminhtml_Block_Dashboard_Graph::API_URL)
                        ->setParameterGet($params)
                        ->setConfig(array('timeout' => 5))
                        ->request('GET');

                $headers = $response->getHeaders();

                $this->getResponse()
                    ->setHeader('Content-type', $headers['Content-type'])
                    ->setBody($response->getBody());
            }
        }
    }
}

With:

const API_URL = 'http://chart.apis.google.com/chart';

The problem could be that your store is behing a proxy and thus it cannot retrieve the Google Chart API URL data.

Related Topic

Magento – How to Fix – Front controller reached 100 router match iterations