cancel
Showing results for 
Search instead for 
Did you mean: 

Front controller reached 100 router match iterations

Front controller reached 100 router match iterations

As of today , all Magento sites down.

Shows this error below 


Honestly, Magento has so many problems and constantly crashes. Why not just use Shopify , Volusion so they can give you near 100% uptime instead of having to manage Magento on your own server and deal with issue after issue after issue....

 
 
Front controller reached 100 router match iterations
Trace: #0 /home/audiobuy/production/source/app/code/core/Mage/Core/Controller/Varien/Front.php(179): Mage::throwException('Front controlle...') #1 /home/audiobuy/production/source/app/code/core/Mage/Core/Model/App.php(365): Mage_Core_Controller_Varien_Front->dispatch() #2 /home/audiobuy/production/source/app/Mage.php(684): Mage_Core_Model_App->run(Array) #3 /home/audiobuy/production/source/index.php(90): Mage::run('hk', 'website') #4 {main}
1 REPLY 1

Re: Front controller reached 100 router match iterations

Hello @pablo_williams,

 

 

It seems you were experiencing a Magento configuration bug. 

I overrode Mage_Core_Model_Config forforced when $_useCache = false generating the config. This fix is validated by the replication script/phpunit tests above, and completely stopped this bug from occurring in our instances.

/**
 * Initialization of core configuration
 *
 * @return Mage_Core_Model_Config
 */
public function init($options=array())
{
    $this->setCacheChecksum(null);
    $this->_cacheLoadedSections = array();
    $this->setOptions($options);
    $this->loadBase();

    $cacheLoad = $this->loadModulesCache();
    if ($cacheLoad) {
        return $this;
    }
    //100 Router Fix Start
    $this->_useCache = false;
    //100 Router Fix End
    $this->loadModules();
    $this->loadDb();
    $this->saveCache();
    return $this;
}

It would be naive of me to believe that this will completely solve the issue for everyone's Magento setup. If it does not work for you then I recommend you

  1. Implement the logic mentioned in the Debugging the Issue section.
  2. Wait for some log data to appear.

 

--
If my answer is useful, please Accept as Solution & give Kudos