Level 67
In your php.ini
max_execution_time = 1200;
Then restart the webserver and worker.
Aug 14, 2019
8
Level 2
The Process exceeded the timeout of 600 seconds. (Symfony)
I have a queue worker that I am running to process some video, and it takes a while.
When trying to work with a large video, I get the following error:
local.ERROR: The process "*long command*" exceeded the timeout of 600 seconds. {"exception":"[object] (Symfony\Component\Process\Exception\ProcessTimedOutException(code: 0): The process \"*long command*" exceeded the timeout of 600 seconds. at /home/hunterhawley/blueprintstats/vendor/symfony/process/Process.php:1237)
The thing is though, in my queue worker, I have:
--timeout=1200
Which is exactly double the 600 second timeout that the error claims is tripping it up. It is obvious to me that either there is some cap at 600, or that some other setting is preventing it from going above. Does anyone have a guess as to which setting may be capping me at 600?
Level 2
I just checked and that is set to 180, so it seems weird that it would have run for 600 with that setting. I will give it a try and get back to you though. Thanks!
Level 2
In the meantime, I am now noticing on my Queue Worker log something about both a $this-timeout and $this->idleTimeout
Could idleTimeout be tripping me up?
Level 122
Your web server and your command line (queue jobs) could be running a different php.ini
at the command line, type php -i | grep max_execution_time and check the response
Level 2
This is the response I get
max_execution_time => 0 => 0
Level 122
So no limit at all from the command line!
What version Laravel is it?
Level 2
Laravel Framework 5.8.31
Level 2
Just tried again after changing the php.ini and restarting with no luck. After seeing the max_execution_time => 0 though I assumed that might happen. Any other thoughts?
1 like
Please or to participate in this conversation.