• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fatal error: Maximum execution time of 240 seconds exceeded in /usr/local/sitebuil...

AlexandreS

New Pleskian
Hello,

Performance problems, again.

I have one site with several pages, and I can't get it published.
I have already applied the "timeout patch", with success: http://kb.odin.com/en/5373

I have also tried to put a timeout value even larger (360), both in php.ini and httpd.conf, but now I'm receiving this error in the publish step in SiteBuilder:

Fatal error: Maximum execution time of 240 seconds exceeded in /usr/local/sitebuilder/include/Base/ORM/BrokerFactory.php on line 48

And this is what is logged in the /var/log/httpd/sitebuilder_error.log file:

[Tue Jul 20 13:22:58 2010] [error] [client 200.186.180.201] PHP Fatal error: Maximum execution time of 240 seconds exceeded in /usr/local/sitebuilder/include/Base/ORM/BrokerFactory.php on line 48, referer: http://sitebuilder1.zooming.com.br/Wizard/Publish

I have restarted apache and mysql, and even the server, but the limit stills fixed in 240.

File I've edited:

/opt/php52/etc/php.ini

max_execution_time = 360 ; Maximum execution time of each script, in seconds
max_input_time = 360 ; Maximum amount of time each script may spend parsing request data
default_socket_timeout = 240

/etc/php.ini

max_execution_time = 360 ; Maximum execution time of each script, in seconds
max_input_time = 360 ; Maximum amount of time each script may spend parsing request data

/etc/httpd/conf/httpd.conf

Timeout 360

Can anyone help me please?

Thank you!
Alexandre
 
Alexandre,

Try to setup similar values on your server:

# less /opt/php52/etc/php.ini |grep exec
max_execution_time = 3600; Maximum execution time of each script, in seconds

# less /etc/httpd/conf/httpd.conf |grep Timeout
Timeout 2400

# cat /usr/local/sitebuilder/etc/php.ini | grep max_execution_time
max_execution_time = 360

After that restart apache and check publication one more time. Such big values could help to understand if this is really timeout issue or not. I assume it should help to resolve the situation.
 
Back
Top