Support the ongoing development of Laravel.io →
posted 9 years ago
Requests
Last updated 2 years ago.
0

This is a restriction of PHP. You can increase the timeout value to avoid it if the script needs more than 30 seconds to run sometimes.

Find max_execution_time in your php.ini file, increase the value, then restart Apache and you should be good.

You may also want to look at why that script takes more than 30 seconds to run.

Last updated 2 years ago.
0

I believe you can force the max_execution time in your code this way

ini_set('max_execution_time', 60);

Last updated 2 years ago.
0

Thanks for the replies. But I don't think our code will take that much time. And it seems that these are triggered by Laravel...

Last updated 2 years ago.
0

I have a similar issue, code shouldn't take that long, upon visiting same pages that create the error and running same code we have no issue...just seems to have random timeouts

0

I solved my issue, a push had overwritten the session.php file and server had started using file based sessions instead of Memcached. the iterator related issue makes sense, the errors were somehow related to file pointers reading session files.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

euyuil euyuil Joined 2 Dec 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.