We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16183
    • 1,390 Posts
    Hi,

    I have been getting this error for the last 2(?) days trying to upgrade my revo install from svn.

    Fatal error: Maximum execution time of 240 seconds exceeded in C:\wamp\www\modxrevolution\core\xpdo\om\xpdoobject.class.php on line 2113


    My as you can see, is wamp => wamp2 server; xp; same error in FF and Iron (aka clean chrome)

    Note sure if it’s important but here’s the call stack

    Call Stack
    #	Time	Memory	Function	Location
    1	0.0009	132064	{main}( )	..\index.php:0
    2	0.0235	999360	modInstallRequest->handle( )	..\index.php:75
    3	0.0256	1017200	include( 'C:\wamp\www\modxrevolution\setup\controllers\install.php' )	..\modinstallrequest.class.php:72
    4	0.0259	1025912	modInstall->execute( )	..\install.php:15
    5	1.0252	9374760	xPDOTransport->install( )	..\modinstall.class.php:362
    6	233.6989	30697912	xPDOObjectVehicle->install( )	..\xpdotransport.class.php:192
    7	233.6989	30698064	xPDOObjectVehicle->_installObject( )	..\xpdoobjectvehicle.class.php:88
    8	233.7192	30711496	xPDOObjectVehicle->_installRelated( )	..\xpdoobjectvehicle.class.php:178
    9	240.0015	32667208	xPDOObjectVehicle->_installObject( )	..\xpdoobjectvehicle.class.php:205
    10	240.0183	32689552	xPDOObject->fromArray( )	..\xpdoobjectvehicle.class.php:152
    11	240.0186	32692856	xPDOObject->_setRaw( )	..\xpdoobject.class.php:1721


    Thanks.
    /k
      • 28215
      • 4,149 Posts
      Whats your memory_limit and max_execution_time set to?

      Also, PHP version? MySQL version? Server?
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 16183
        • 1,390 Posts
        Quote from: splittingred at Jun 25, 2009, 10:53 AM

        Whats your memory_limit and max_execution_time set to?

        Also, PHP version? MySQL version? Server?

        1. memory limit = 128m
        2. max execution time was 30 but changed to 300 when I started receiving the errors
        3. php version = 5.2.9-2
        4. mysql => Client API version =5.0.51a ; Server version 5.1.31-community
        5. server = WAMP2 => Apache/2.2.11 (Win32)

        cheers/k
          • 22303 MODX Staff
          • 10,725 Posts
          The max_execution_time is set to 240 on purpose; I don’t think a server that takes over 240 seconds to install on is advisable for use with MODx Revolution, IMHO. But if you want to get past it, change line 315 of setup/includes/modinstall.class.php to set the max_execution_time to 0 (i.e. unlimited).

          Also, note that your MySQL client API differing from your MySQL server version is not a good thing, and may be related to the long execution time.
            • 16183
            • 1,390 Posts
            Jason,

            Thanks. I’d rather not change/hack the code to change the max_exec time...I will look at the MySQL angle. Many thanks.

            cheers/k
              • 7923
              • 4,213 Posts
              Don’t have any meaningful input for your issues, but just to note and "warn" others.. I had serious problems when running Revolution off a USB drive. Updating existing installation hit max_exec times (while normal install went ok), reloading lexicon entries crashed apache, after installing a component and when Revolution updated the packages listing crashed apache every time (and sometimes mysql).. etc. Once I moved stuff on to proper hard drive from the USB drive everything worked smoothly.. I guess apache didn’t like the read times that it got from the USB drive.


                "He can have a lollipop any time he wants to. That's what it means to be a programmer."
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org