I had been requested to assist trobleshoot and fix someone's website. It's designed in php, on the linux box, utilizing an apache server and mysql, and I have not labored with these before (except maybe linux in class).

I acquired the majority of the issues fixed (most code is usually the same regardless of what langues it's) however there's still one page that's timing out when processing huge files. I am fairly sure the issue is a timeout somewhere however i have no clue where all of the php timeouts could be.

I've modified max_execution_time, max_input_time, mysql.connect_timeout, default_socket_timeout, and realpath_cache_ttl in php.ini but it's still timing out after about ten minutes. The other configurations might exist which i could increase to fix this?

Like a sidenote, I am conscious that 10min is usually not preferred when processing an file, however this portion of the website is an endeavor solely for one individual a couple of times per week and she or he does not mind supplying the procedure finishes not surprisingly !and that i really don't wish to go rewrite another person's bad coding inside a language I do not understand, for any process I do not understand)

EDIT: The sql process finishes without anyone's knowledge, its only the web page itself that occasions out.

Per Frank Farmer's suggestion, I added flush() towards the code and delay pills work now. Certainly a browser timeout, thanks Frank!

You should use set_time_limit() should you place it to zero the script shouldn't break whatsoever.

This is placed in your script, not in almost any config etc...

Edit: Try altering apache's timeout configurations. Within the config search for TimeOut directive (ought to be the same for apache 2.x and apache 1.3.x), once transformed restart apache and appearance it.

Edit 3: Did put forth the hyperlink I provided? It lists there the default, that is 300 seconds (a few minutes). And if the setting Isn't within the config file, you can include it.

Based on the paperwork:

The TimeOut directive presently defines how long Apache will watch for three things:

  1. The quantity of your time it requires to get a GET request.
  2. How long between receipt of TCP packets on the Publish or PUT request.
  3. How long between ACKs on transmissions of TCP packets in reactions.

So it's possible it does not relate, but check it out and find out.