browser waits forever on my script

As first I was getting "PHP Warning: Unknown: failed to open stream:
Permission denied in Unknown on line 0"
errors in my server log.

so I gave the file permissions.
now the browser sits there forever waiting for the server to respond. I
even tried bouncing the server. no joy.

the file is 700 lines long, so I decided not to post it here.

any clues as to what might be going on?

using PHP5.

--
Jim Michaels
for email, edit the address

Re: browser waits forever on my script

Jim Michaels wrote:

> now the browser sits there forever waiting for the server to respond. I
> even tried bouncing the server. no joy.

You never have to run untested Code into productive Environments.
If its not productive install and use a debugger for locating the problem.

Otherwise u can only use manual debugging (print_r, var_dump, ...)
to clean the problems.

> the file is 700 lines long, so I decided not to post it here.

So you can only quest a magic glass ball or consult your rather clairvoyant.

Ulf

--
_,
_(_p> Ulf [Kado] Kadner
\<_)
^^

Re: browser waits forever on my script

On 25 Nov, 11:33, Ulf Kadner wrote:
> Jim Michaels wrote:
> > now the browser sits there forever waiting for the server to respond. I
> > even tried bouncing the server. no joy.
>
> You never have to run untested Code into productive Environments.
> If its not productive install and use a debugger for locating the problem.
>
> Otherwise u can only use manual debugging (print_r, var_dump, ...)
> to clean the problems.
>
> > the file is 700 lines long, so I decided not to post it here.
>
> So you can only quest a magic glass ball or consult your rather clairvoyant.
>

try publishing a 10 line script which replicates the problem (although
by then you'll probably have worked it out for yourself).

C.

Re: browser waits forever on my script

C. (http://symcbean.blogspot.com/) wrote:
> On 25 Nov, 11:33, Ulf Kadner wrote:
>> Jim Michaels wrote:
>>> now the browser sits there forever waiting for the server to respond. I
>>> even tried bouncing the server. no joy.
>> You never have to run untested Code into productive Environments.
>> If its not productive install and use a debugger for locating the problem.
>>
>> Otherwise u can only use manual debugging (print_r, var_dump, ...)
>> to clean the problems.
>>
>>> the file is 700 lines long, so I decided not to post it here.
>> So you can only quest a magic glass ball or consult your rather clairvoyant.
>>
>
> try publishing a 10 line script which replicates the problem (although
> by then you'll probably have worked it out for yourself).
>
> C.

in php.ini:
max_execution_time = 60 ; Maximum execution time of each script, in
seconds

it waits a whole lot longer than that. it won't ever stop. usually I
see a browser timeout after a certain number of seconds, but this has me
stumped. it would be nice to know what's going on under the hood.

is this apache which is having a problem? this is not on a production
server, just a test environment.

--
Jim Michaels
for email, edit the address

Re: browser waits forever on my script

"failed to open stream", are you doing an fopen() or fsockopen() on a
remote url ?
If yes, the remote url being unavailable and timing out is likely to
be the issue.

Regards,
Kailash Nadh
http://kailashnadh.name

On Nov 25, 8:53 am, Jim Michaels
wrote:
> As first I was getting "PHP Warning: Unknown: failed to open stream:
> Permission denied in Unknown on line 0"
> errors in my server log.
>
> so I gave the file permissions.
> now the browser sits there forever waiting for the server to respond. I
> even tried bouncing the server. no joy.
>
> the file is 700 lines long, so I decided not to post it here.
>
> any clues as to what might be going on?
>
> using PHP5.
>
> --
> Jim Michaels
> for email, edit the address

Re: browser waits forever on my script

Jim Michaels wrote:
> C. (http://symcbean.blogspot.com/) wrote:
>> On 25 Nov, 11:33, Ulf Kadner wrote:
>>> Jim Michaels wrote:
>>>> now the browser sits there forever waiting for the server to
>>>> respond. I
>>>> even tried bouncing the server. no joy.
>>> You never have to run untested Code into productive Environments.
>>> If its not productive install and use a debugger for locating the
>>> problem.
>>>
>>> Otherwise u can only use manual debugging (print_r, var_dump, ...)
>>> to clean the problems.
>>>
>>>> the file is 700 lines long, so I decided not to post it here.
>>> So you can only quest a magic glass ball or consult your rather
>>> clairvoyant.
>>>
>>
>> try publishing a 10 line script which replicates the problem (although
>> by then you'll probably have worked it out for yourself).
>>
>> C.
>
> in php.ini:
> max_execution_time = 60 ; Maximum execution time of each script, in
> seconds
>
> it waits a whole lot longer than that. it won't ever stop. usually I
> see a browser timeout after a certain number of seconds, but this has me
> stumped. it would be nice to know what's going on under the hood.
>
> is this apache which is having a problem? this is not on a production
> server, just a test environment.
>

Jim,

Much more likely is you have a loop in your script which doesn't exit.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Re: browser waits forever on my script

Jerry Stuckle wrote:
> Jim Michaels wrote:
>> C. (http://symcbean.blogspot.com/) wrote:
>>> On 25 Nov, 11:33, Ulf Kadner wrote:
>>>> Jim Michaels wrote:
>>>>> now the browser sits there forever waiting for the server to
>>>>> respond. I
>>>>> even tried bouncing the server. no joy.
>>>> You never have to run untested Code into productive Environments.
>>>> If its not productive install and use a debugger for locating the
>>>> problem.
>>>>
>>>> Otherwise u can only use manual debugging (print_r, var_dump, ...)
>>>> to clean the problems.
>>>>
>>>>> the file is 700 lines long, so I decided not to post it here.
>>>> So you can only quest a magic glass ball or consult your rather
>>>> clairvoyant.
>>>>
>>>
>>> try publishing a 10 line script which replicates the problem (although
>>> by then you'll probably have worked it out for yourself).
>>>
>>> C.
>>
>> in php.ini:
>> max_execution_time = 60 ; Maximum execution time of each script,
>> in seconds
>>
>> it waits a whole lot longer than that. it won't ever stop. usually I
>> see a browser timeout after a certain number of seconds, but this has
>> me stumped. it would be nice to know what's going on under the hood.
>>
>> is this apache which is having a problem? this is not on a production
>> server, just a test environment.
>>
>
> Jim,
>
> Much more likely is you have a loop in your script which doesn't exit.
>


this was correct. it was a header statement which refers to itself with
no proper conditions. problem solved. now onto other things.

--
Jim Michaels
for email, edit the address

Re: browser waits forever on my script

Jim Michaels wrote:
> Jerry Stuckle wrote:
>> Jim Michaels wrote:
>>> C. (http://symcbean.blogspot.com/) wrote:
>>>> On 25 Nov, 11:33, Ulf Kadner wrote:
>>>>> Jim Michaels wrote:
>>>>>> now the browser sits there forever waiting for the server to
>>>>>> respond. I
>>>>>> even tried bouncing the server. no joy.
>>>>> You never have to run untested Code into productive Environments.
>>>>> If its not productive install and use a debugger for locating the
>>>>> problem.
>>>>>
>>>>> Otherwise u can only use manual debugging (print_r, var_dump, ...)
>>>>> to clean the problems.
>>>>>
>>>>>> the file is 700 lines long, so I decided not to post it here.
>>>>> So you can only quest a magic glass ball or consult your rather
>>>>> clairvoyant.
>>>>>
>>>>
>>>> try publishing a 10 line script which replicates the problem (although
>>>> by then you'll probably have worked it out for yourself).
>>>>
>>>> C.
>>>
>>> in php.ini:
>>> max_execution_time = 60 ; Maximum execution time of each script,
>>> in seconds
>>>
>>> it waits a whole lot longer than that. it won't ever stop. usually
>>> I see a browser timeout after a certain number of seconds, but this
>>> has me stumped. it would be nice to know what's going on under the
>>> hood.
>>>
>>> is this apache which is having a problem? this is not on a
>>> production server, just a test environment.
>>>
>>
>> Jim,
>>
>> Much more likely is you have a loop in your script which doesn't exit.
>>
>
>
> this was correct. it was a header statement which refers to itself with
> no proper conditions. problem solved. now onto other things.
>

I won't tell you how many times I've done similar things :-)

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================