php-windows Digest 8 Apr 2010 17:27:29 -0000 Issue 3783

Topics (messages 29981 through 29989):

Re: Windows binaries
        29981 by: Venkat Raman Don
        29982 by: Ferenc Kovacs
        29983 by: Todd Oberly
        29984 by: Tommy Pham
        29985 by: Todd Oberly
        29986 by: Ferenc Kovacs
        29987 by: Ferenc Kovacs
        29988 by: Tommy Pham
        29989 by: Pierre Joye

Administrivia:

To subscribe to the digest, e-mail:
        php-windows-digest-subscr...@lists.php.net

To unsubscribe from the digest, e-mail:
        php-windows-digest-unsubscr...@lists.php.net

To post to the list, e-mail:
        php-wind...@lists.php.net


----------------------------------------------------------------------
--- Begin Message ---
Hi,

I am part of IIS FAstCGI development team. Can you give me details about error 
messages. Write a 1:1 mail to me.

Thanks,
Don.

-----Original Message-----
From: Todd Oberly [mailto:taobe...@mindspring.com] 
Sent: Wednesday, April 07, 2010 9:35 PM
To: Pierre Joye
Cc: php-wind...@lists.php.net
Subject: Re: [PHP-WIN] Windows binaries

-----Original Message-----
>From: Pierre Joye <pierre....@gmail.com>
>Sent: Apr 5, 2010 6:08 AM
>To: Todd Oberly <taobe...@mindspring.com>
>Cc: php-wind...@lists.php.net
>Subject: Re: [PHP-WIN] Windows binaries
>
>On Mon, Apr 5, 2010 at 6:27 AM, Todd Oberly <taobe...@mindspring.com> wrote:
>
>> I've heard of FastCGI, but never used it before.  If I want to get the 
>> application running ASAP without FastCGI (please don't argue), what would be 
>> the effect of using the thread-safe VC6 build of 5.2.13?  Just a decrease in 
>> performance?
>
>PHP TS is slightly slower than PHP NTS but not in a significant
>manner. However the stability of the ISAPI may affect your sites much
>more than the TS vs NTS delta. Many crashes have worst side effects
>than slowdowns.

A short follow-up.  I had the PHP application package running through ISAPI for 
a short time, but then noticed errors like

Faulting application w3wp.exe, version 6.0.3790.3959, faulting module unknown, 
version 0.0.0.0, fault address 0x01b45c80.

in the Event Viewer.  Soooo after some investigation, FastCGI is now the 
solution. :)  But I then noticed something strange, but am not sure if it's 
related.  I then started seeing a warning in my browser when running a certain 
aspect of the script.  I'd done this a number of times before, but saw no 
errors.  Could there be something about the ISAPI interface that was blocking 
error output?

Thanks,

Todd

-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



--- End Message ---
--- Begin Message ---
On Thu, Apr 8, 2010 at 6:34 AM, Todd Oberly <taobe...@mindspring.com> wrote:

> -----Original Message-----
> >From: Pierre Joye <pierre....@gmail.com>
> >Sent: Apr 5, 2010 6:08 AM
> >To: Todd Oberly <taobe...@mindspring.com>
> >Cc: php-wind...@lists.php.net
> >Subject: Re: [PHP-WIN] Windows binaries
> >
> >On Mon, Apr 5, 2010 at 6:27 AM, Todd Oberly <taobe...@mindspring.com>
> wrote:
> >
> >> I've heard of FastCGI, but never used it before.  If I want to get the
> application running ASAP without FastCGI (please don't argue), what would be
> the effect of using the thread-safe VC6 build of 5.2.13?  Just a decrease in
> performance?
> >
> >PHP TS is slightly slower than PHP NTS but not in a significant
> >manner. However the stability of the ISAPI may affect your sites much
> >more than the TS vs NTS delta. Many crashes have worst side effects
> >than slowdowns.
>
> A short follow-up.  I had the PHP application package running through ISAPI
> for a short time, but then noticed errors like
>
> Faulting application w3wp.exe, version 6.0.3790.3959, faulting module
> unknown, version 0.0.0.0, fault address 0x01b45c80.
>
> in the Event Viewer.  Soooo after some investigation, FastCGI is now the
> solution. :)  But I then noticed something strange, but am not sure if it's
> related.  I then started seeing a warning in my browser when running a
> certain aspect of the script.  I'd done this a number of times before, but
> saw no errors.  Could there be something about the ISAPI interface that was
> blocking error output?
>
> Thanks,
>
> Todd
>
>
http://www.google.hu/search?hl=hu&client=firefox-a&hs=WdP&rls=org.mozilla%3Ahu%3Aofficial&q=InstanceMaxRequests+vs+PHP_FCGI_MAX_REQUESTS&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=
There is a known problem, if you set the PHP_FCGI_MAX_REQUESTS lower than
the InstanceMaxRequests then sometimes the InstanceMaxRequests will be
reached, the fastcgi PM manager will restart the worker, and the visitor
will get a http 500, Internal Server Error.
Others will correct me, if I'm missing something.

Tyrael


> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--- End Message ---
--- Begin Message ---
-----Original Message-----
>From: Ferenc Kovacs <tyr...@gmail.com>
>Sent: Apr 8, 2010 12:53 AM
>To: Todd Oberly <taobe...@mindspring.com>
>Subject: Re: [PHP-WIN] Windows binaries
>
>On Thu, Apr 8, 2010 at 6:34 AM, Todd Oberly <taobe...@mindspring.com> wrote:
>
>> -----Original Message-----
>> >From: Pierre Joye <pierre....@gmail.com>
>> >Sent: Apr 5, 2010 6:08 AM
>> >To: Todd Oberly <taobe...@mindspring.com>
>> >Cc: php-wind...@lists.php.net
>> >Subject: Re: [PHP-WIN] Windows binaries
>> >
>> >On Mon, Apr 5, 2010 at 6:27 AM, Todd Oberly <taobe...@mindspring.com>
>> wrote:
>> >
>> >> I've heard of FastCGI, but never used it before.  If I want to get the
>> application running ASAP without FastCGI (please don't argue), what would be
>> the effect of using the thread-safe VC6 build of 5.2.13?  Just a decrease in
>> performance?
>> >
>> >PHP TS is slightly slower than PHP NTS but not in a significant
>> >manner. However the stability of the ISAPI may affect your sites much
>> >more than the TS vs NTS delta. Many crashes have worst side effects
>> >than slowdowns.
>>
>> A short follow-up.  I had the PHP application package running through ISAPI
>> for a short time, but then noticed errors like
>>
>> Faulting application w3wp.exe, version 6.0.3790.3959, faulting module
>> unknown, version 0.0.0.0, fault address 0x01b45c80.
>>
>> in the Event Viewer.  Soooo after some investigation, FastCGI is now the
>> solution. :)  But I then noticed something strange, but am not sure if it's
>> related.  I then started seeing a warning in my browser when running a
>> certain aspect of the script.  I'd done this a number of times before, but
>> saw no errors.  Could there be something about the ISAPI interface that was
>> blocking error output?
>>
>>
>http://www.google.hu/search?hl=hu&client=firefox-a&hs=WdP&rls=org.mozilla%3Ahu%3Aofficial&q=InstanceMaxRequests+vs+PHP_FCGI_MAX_REQUESTS&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=
>There is a known problem, if you set the PHP_FCGI_MAX_REQUESTS lower than
>the InstanceMaxRequests then sometimes the InstanceMaxRequests will be
>reached, the fastcgi PM manager will restart the worker, and the visitor
>will get a http 500, Internal Server Error.
>Others will correct me, if I'm missing something.
>
>Tyrael

I think I've described this poorly, so let me try again.  This is how it 
occurred:

1) I installed the PHP scripts using the vendor-recommended ISAPI method, and 
verified that it worked completely.  The scripts are some glue between a 
commercial application and IIS for sending mobile phone clients to a web page 
and allowing users to download them.

2) I then installed and configured the FastCGI system, and upgraded PHP to the 
recommended 5.2.13 non-thread-safe version.  I'm not an expert with IIS, so it 
took some trial and error to get it working.  At no time did I modify any PHP 
code or change any error logging settings in php.ini.

3) Upon testing this new setup, I started seeing a PHP warning when trying to 
download a client: "PHP Warning: Missing argument 4..."

The warning is legitimate, and I will be reporting it to the vendor (and also 
fixing it myself, as it looks very simple)...but these errors seem to have 
started upon installing FastCGI.  Unless the difference was moving from PHP 
5.2.12 -> 5.2.13 ?  I could be wrong.  The situation is under control, so this 
just an inquiry rather than a complaint.

Thanks again,

Todd


--- End Message ---
--- Begin Message ---
> -----Original Message-----
> From: Todd Oberly [mailto:taobe...@mindspring.com]
> Sent: Thursday, April 08, 2010 7:13 AM
> To: php-wind...@lists.php.net
> Subject: Re: [PHP-WIN] Windows binaries
> 

<snip>

> 
> The warning is legitimate, and I will be reporting it to the vendor
> (and also fixing it myself, as it looks very simple)...but these errors
> seem to have started upon installing FastCGI.  Unless the difference
> was moving from PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The
> situation is under control, so this just an inquiry rather than a
> complaint.
> 
> Thanks again,
> 
> Todd
> 

The problem is not so much as PHP version upgrade but rather ISAPI > FastCGI.  
Another example of broken app is phpmyadmin.  Works fine with ISAPI 
configuration but breaks with FastCGI.

Regards,
Tommy


--- End Message ---
--- Begin Message ---
-----Original Message-----
>From: Tommy Pham <tommy...@gmail.com>
>Sent: Apr 8, 2010 10:15 AM
>To: 'Todd Oberly' <taobe...@mindspring.com>, php-wind...@lists.php.net
>Subject: RE: [PHP-WIN] Windows binaries
>
>> -----Original Message-----
>> From: Todd Oberly [mailto:taobe...@mindspring.com]
>> Sent: Thursday, April 08, 2010 7:13 AM
>> To: php-wind...@lists.php.net
>> Subject: Re: [PHP-WIN] Windows binaries
>> 
>
><snip>
>
>> 
>> The warning is legitimate, and I will be reporting it to the vendor
>> (and also fixing it myself, as it looks very simple)...but these errors
>> seem to have started upon installing FastCGI.  Unless the difference
>> was moving from PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The
>> situation is under control, so this just an inquiry rather than a
>> complaint.
>> 
>> Thanks again,
>> 
>> Todd
>> 
>
>The problem is not so much as PHP version upgrade but rather ISAPI > FastCGI.  
>Another example of broken app is phpmyadmin.  Works fine with ISAPI 
>configuration but breaks with FastCGI.
>
>Regards,
>Tommy

Ah, so these types of issues aren't unheard of?  Do you suspect the vendor will 
need to modify anything besides the function causing the warning?

Thanks,

Todd

--- End Message ---
--- Begin Message ---
On Thu, Apr 8, 2010 at 4:12 PM, Todd Oberly <taobe...@mindspring.com> wrote:

> -----Original Message-----
> >From: Ferenc Kovacs <tyr...@gmail.com>
> >Sent: Apr 8, 2010 12:53 AM
> >To: Todd Oberly <taobe...@mindspring.com>
> >Subject: Re: [PHP-WIN] Windows binaries
> >
> >On Thu, Apr 8, 2010 at 6:34 AM, Todd Oberly <taobe...@mindspring.com>
> wrote:
> >
> >> -----Original Message-----
> >> >From: Pierre Joye <pierre....@gmail.com>
> >> >Sent: Apr 5, 2010 6:08 AM
> >> >To: Todd Oberly <taobe...@mindspring.com>
> >> >Cc: php-wind...@lists.php.net
> >> >Subject: Re: [PHP-WIN] Windows binaries
> >> >
> >> >On Mon, Apr 5, 2010 at 6:27 AM, Todd Oberly <taobe...@mindspring.com>
> >> wrote:
> >> >
> >> >> I've heard of FastCGI, but never used it before.  If I want to get
> the
> >> application running ASAP without FastCGI (please don't argue), what
> would be
> >> the effect of using the thread-safe VC6 build of 5.2.13?  Just a
> decrease in
> >> performance?
> >> >
> >> >PHP TS is slightly slower than PHP NTS but not in a significant
> >> >manner. However the stability of the ISAPI may affect your sites much
> >> >more than the TS vs NTS delta. Many crashes have worst side effects
> >> >than slowdowns.
> >>
> >> A short follow-up.  I had the PHP application package running through
> ISAPI
> >> for a short time, but then noticed errors like
> >>
> >> Faulting application w3wp.exe, version 6.0.3790.3959, faulting module
> >> unknown, version 0.0.0.0, fault address 0x01b45c80.
> >>
> >> in the Event Viewer.  Soooo after some investigation, FastCGI is now the
> >> solution. :)  But I then noticed something strange, but am not sure if
> it's
> >> related.  I then started seeing a warning in my browser when running a
> >> certain aspect of the script.  I'd done this a number of times before,
> but
> >> saw no errors.  Could there be something about the ISAPI interface that
> was
> >> blocking error output?
> >>
> >>
> >
> http://www.google.hu/search?hl=hu&client=firefox-a&hs=WdP&rls=org.mozilla%3Ahu%3Aofficial&q=InstanceMaxRequests+vs+PHP_FCGI_MAX_REQUESTS&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=
> >There is a known problem, if you set the PHP_FCGI_MAX_REQUESTS lower than
> >the InstanceMaxRequests then sometimes the InstanceMaxRequests will be
> >reached, the fastcgi PM manager will restart the worker, and the visitor
> >will get a http 500, Internal Server Error.
> >Others will correct me, if I'm missing something.
> >
> >Tyrael
>
> I think I've described this poorly, so let me try again.  This is how it
> occurred:
>
> 1) I installed the PHP scripts using the vendor-recommended ISAPI method,
> and verified that it worked completely.  The scripts are some glue between a
> commercial application and IIS for sending mobile phone clients to a web
> page and allowing users to download them.
>
> 2) I then installed and configured the FastCGI system, and upgraded PHP to
> the recommended 5.2.13 non-thread-safe version.  I'm not an expert with IIS,
> so it took some trial and error to get it working.  At no time did I modify
> any PHP code or change any error logging settings in php.ini.
>
> 3) Upon testing this new setup, I started seeing a PHP warning when trying
> to download a client: "PHP Warning: Missing argument 4..."
>
> The warning is legitimate, and I will be reporting it to the vendor (and
> also fixing it myself, as it looks very simple)...but these errors seem to
> have started upon installing FastCGI.  Unless the difference was moving from
> PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The situation is under control,
> so this just an inquiry rather than a complaint.
>
> Could you check that your fastcgi php is using the same php.ini as the
previous ISAPI one?
I think that you either changed the content of the original php.ini (either
manualy or overwriting with a newer php.ini) or you configured differently
your new environment, and its using a different php.ini than it was used
before.

You should configure the display_errors and error_reporting directives in
your current php.ini to hide this kind of notice/warning/error messages from
your users.
If you are unsure about which php.ini is in use now, you can create a test
php file containinig
<?php phpinfo();
and it will print a lot of information, and you should look for the
Loaded Configuration File
and
Additional .ini files parsed

Tyrael

> Thanks again,
>
> Todd
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--- End Message ---
--- Begin Message ---
On Thu, Apr 8, 2010 at 4:15 PM, Tommy Pham <tommy...@gmail.com> wrote:

> > -----Original Message-----
> > From: Todd Oberly [mailto:taobe...@mindspring.com]
> > Sent: Thursday, April 08, 2010 7:13 AM
> > To: php-wind...@lists.php.net
> > Subject: Re: [PHP-WIN] Windows binaries
> >
>
> <snip>
>
> >
> > The warning is legitimate, and I will be reporting it to the vendor
> > (and also fixing it myself, as it looks very simple)...but these errors
> > seem to have started upon installing FastCGI.  Unless the difference
> > was moving from PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The
> > situation is under control, so this just an inquiry rather than a
> > complaint.
> >
> > Thanks again,
> >
> > Todd
> >
>
> The problem is not so much as PHP version upgrade but rather ISAPI >
> FastCGI.  Another example of broken app is phpmyadmin.  Works fine with
> ISAPI configuration but breaks with FastCGI.
>
> I don't think so, if the error is present just doesn't displayed in the old
configuration but it does in the new, then I think this is a configuration
issue, and not a SAPI one.

btw: which phpmyadmin version are you using? I did heard of that kind of
report, but last weekend, when I was playing with a windows + apache +
fastcgi + php devel environment I successfuly installed the latest
phpmyadmin without running in any issue.
what are the symptoms, maybe they are IIS only?

Tyrael

> Regards,
> Tommy
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--- End Message ---
--- Begin Message ---
The problem with FastCGI breaking certain apps is with IIS.  I’ve always use 
PHP with Apache as module for both Windows and FreeBSD.  I’ll see if it works 
for FastCGI with Apache on Windows.  You can get to login screen (configured as 
cookie), but after a long while, I receive HTTP500 error.  The same config 
works fine with phpbb, phppgadmin.  The phpmyadmin version that I’m trying to 
get work is 3.3.1, although I have similar problems with previous versions of 
phpmyadmin when FastCGI came out even though I didn’t try to troubleshoot it 
since it wasn’t important at that time.

 

Regards,

Tommy

 

From: Ferenc Kovacs [mailto:tyr...@gmail.com] 
Sent: Thursday, April 08, 2010 7:42 AM
To: Tommy Pham
Cc: Todd Oberly; php-wind...@lists.php.net
Subject: Re: [PHP-WIN] Windows binaries

 

 

On Thu, Apr 8, 2010 at 4:15 PM, Tommy Pham <tommy...@gmail.com> wrote:

> -----Original Message-----
> From: Todd Oberly [mailto:taobe...@mindspring.com]

> Sent: Thursday, April 08, 2010 7:13 AM
> To: php-wind...@lists.php.net
> Subject: Re: [PHP-WIN] Windows binaries
>

<snip>

>
> The warning is legitimate, and I will be reporting it to the vendor
> (and also fixing it myself, as it looks very simple)...but these errors
> seem to have started upon installing FastCGI.  Unless the difference
> was moving from PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The
> situation is under control, so this just an inquiry rather than a
> complaint.
>
> Thanks again,
>
> Todd
>

The problem is not so much as PHP version upgrade but rather ISAPI > FastCGI.  
Another example of broken app is phpmyadmin.  Works fine with ISAPI 
configuration but breaks with FastCGI.

I don't think so, if the error is present just doesn't displayed in the old 
configuration but it does in the new, then I think this is a configuration 
issue, and not a SAPI one.

btw: which phpmyadmin version are you using? I did heard of that kind of 
report, but last weekend, when I was playing with a windows + apache + fastcgi 
+ php devel environment I successfuly installed the latest phpmyadmin without 
running in any issue.
what are the symptoms, maybe they are IIS only?

Tyrael  

Regards,
Tommy



--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


--- End Message ---
--- Begin Message ---
Hi,

FastCGI does not break any application. Please explain what you mean
by "breaking applications". It also helps to verify your log to see
what's actually happening, an error 500 can be a lot of things.

Cheers,

On Thu, Apr 8, 2010 at 5:23 PM, Tommy Pham <tommy...@gmail.com> wrote:
> The problem with FastCGI breaking certain apps is with IIS.  I’ve always use 
> PHP with Apache as module for both Windows and FreeBSD.  I’ll see if it works 
> for FastCGI with Apache on Windows.  You can get to login screen (configured 
> as cookie), but after a long while, I receive HTTP500 error.  The same config 
> works fine with phpbb, phppgadmin.  The phpmyadmin version that I’m trying to 
> get work is 3.3.1, although I have similar problems with previous versions of 
> phpmyadmin when FastCGI came out even though I didn’t try to troubleshoot it 
> since it wasn’t important at that time.
>
>
>
> Regards,
>
> Tommy
>
>
>
> From: Ferenc Kovacs [mailto:tyr...@gmail.com]
> Sent: Thursday, April 08, 2010 7:42 AM
> To: Tommy Pham
> Cc: Todd Oberly; php-wind...@lists.php.net
> Subject: Re: [PHP-WIN] Windows binaries
>
>
>
>
>
> On Thu, Apr 8, 2010 at 4:15 PM, Tommy Pham <tommy...@gmail.com> wrote:
>
>> -----Original Message-----
>> From: Todd Oberly [mailto:taobe...@mindspring.com]
>
>> Sent: Thursday, April 08, 2010 7:13 AM
>> To: php-wind...@lists.php.net
>> Subject: Re: [PHP-WIN] Windows binaries
>>
>
> <snip>
>
>>
>> The warning is legitimate, and I will be reporting it to the vendor
>> (and also fixing it myself, as it looks very simple)...but these errors
>> seem to have started upon installing FastCGI.  Unless the difference
>> was moving from PHP 5.2.12 -> 5.2.13 ?  I could be wrong.  The
>> situation is under control, so this just an inquiry rather than a
>> complaint.
>>
>> Thanks again,
>>
>> Todd
>>
>
> The problem is not so much as PHP version upgrade but rather ISAPI > FastCGI. 
>  Another example of broken app is phpmyadmin.  Works fine with ISAPI 
> configuration but breaks with FastCGI.
>
> I don't think so, if the error is present just doesn't displayed in the old 
> configuration but it does in the new, then I think this is a configuration 
> issue, and not a SAPI one.
>
> btw: which phpmyadmin version are you using? I did heard of that kind of 
> report, but last weekend, when I was playing with a windows + apache + 
> fastcgi + php devel environment I successfuly installed the latest phpmyadmin 
> without running in any issue.
> what are the symptoms, maybe they are IIS only?
>
> Tyrael
>
> Regards,
> Tommy
>
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org

--- End Message ---

Reply via email to