Forum Moderators: phranque

Message Too Old, No Replies

Server Timeout

Page Not Found?

         

aquanutz

2:58 pm on May 4, 2007 (gmt 0)

10+ Year Member



Hi, I wasn't sure if I should put this in the PHP section because it's a php script that is running when the error happens, but I think this has more or a webmaster general section feel to it.

Anyhow, on my server I run a script that takes a looooong time to go through my entire database and do a lot of editing to each entry. There are roughly a few hundred thousand entries.. I go to run the script and it runs fine for about two hours or so and then my browser gets the "Page Not Found" error. I am assuming it's because of a timeout somewhere. I know it's not the php script because I tested the exact code on a smaller scale (1000) entries and it ran just fine, it just took about 5 minutes.

I am running a Win2k3 box with IIS. Anyone have any thoughts? Thanks.

trillianjedi

3:30 pm on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Sounds to me like it might be a database query issue, and perhaps you have a query or table that is not well optimised?

You may be better to take the discussion into the databases forum.

TJ

aquanutz

3:55 pm on May 4, 2007 (gmt 0)

10+ Year Member



I'll check in with them there too, but what would make the webserver stop responding? Something in IIS or CGI maybe?

trillianjedi

4:26 pm on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



No, just a timeout from the database taking too long to serve the query back.

I believe timeouts are set browser-side?

aquanutz

5:29 pm on May 4, 2007 (gmt 0)

10+ Year Member



Alrighty, Thanks!

rocknbil

5:31 pm on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I go to run the script and it runs fine for about two hours or so and then my browser gets the "Page Not Found" error.

I would **seriously** rethink any process that takes more than 60 seconds to call from the web. If you're on shared hosting, it's probably sucking up major resources and if discovered your ISP may cut you off.

Consider a cron job for something like this ("scheduled task" on Windblows servers) or rethink how you're doing what you're doing - two hours is an insane amount of time to perform a web task.