RE: [Phpgroupware-developers] Crash with win32 apache

[Peter]

Hello JeanEric,
When I had the similar problem in earlier PHPs. There were a couple of faulty 
extensions I discovered by turning off all 
extensions then adding them back one at a time. Those extensions worked in a 
later release. There were a few in 4.0.5 
and at that time I needed to use several I had not used before. They were all 
working by 4.0.8 and I have not switched on 
a new extension since then. Perhaps you use an extension I do not use and the 
one you use recently received a major 
update.

I also hit one problem when using an old Apache with a brand new PHP release 
and a problem using an old MySQL 
with a brand new PHP/Apache combination. Now I update all three when I update 
PHP. I look for an Apache and 
MySQL that would have been available when the PHP developers where testing 
their new release.

The MySQL with problems produced the problems only with Berkerley tables. I 
switched back to MySQL tables and had 
no more problems. Your problem with MySQL might be the release or some option 
that is different to my setup.

The major change from NT to Win2k was active directories but there may be some 
other difference that creates your 
problem. It would be something the PHP Win32 developers are not testing. There 
is a mailing list at 
http://www.php4win.com/ if you are using their binary for Win2k. They might 
have Win2k users reporting similar results.

My NT 4.0 is rock solid so long as I do not install Internet Exploder. I use 
Win2k only to run SQL Server 2000 and leave 
Apache/PHP/MySQL/PostgreSQL on NT. I thought the Win32 API was the same between 
NT and Win2k so software 
like PHP should work the same. Perhaps PHP is starting to use some new feature 
of the Win32 API in Win2k.

The PHP error logs appear to be buffered so do not always report the last 
couple of records when PHP or Apache 
crashes. To bypass that problem, I use a function to write my own log file to 
disk and close the log file after each 
message. That gets every message out and I can insert trace messages wherever I 
like. The PHP developers hate it 
when I suggest you write your own error logs but I find with most PHP 
installations across most operating systems you 
just cannot guarantee to get the last error message. It is even harder when a 
site is hosted at an ISP and the ISP will not 
let you modify their operating system configuration.

When Apache crashes there is even less chance of PHP detecting the error so the 
PHP error logs are of little use and a 
step by step tract is needed. I do not know what execution trace facilities you 
can use with phpgw. I did see some 
test/trace code in phpgw but did not follow up how the code is switched on. 
Perhaps phpgw developers could point you 
to trace facilities.

Peter

2/6/02 7:48:32 PM, Cuendet JeanEric <address@hidden> wrote:

>
>> In PHP 4.0.6, I had the problem when certain extensions were 
>> enabled, even if the extensions were not used in the script 
>> I was testing. With PHP 4.1.1, I use all those extensions and 
>> more but do not have the exploding Apache problem.
>
>I have Apache 1.3.23 + PHP 4.1.1 and it crashes.
>If I run "php login.php" in /phpgroupware, then php crash alone ONLY if
>MySQL is started!
>If I shutdown MySQL, then I receive:
>X-Powered-By: PHP/4.1.1
>Cache-Control: no-cache, must-revalidate
>Pragma: no-cache
>Content-type: text/html
>
>It's not a very useful page, but it's here at least.
>
>> Look for instances where your code adds something to a global 
>> variable. With certain php.ini settings, you can end up 
>> with a variable going in to a global array and that variable 
>> itself being a global array, with the result being a loop. I found 
>> this with several open source applications when they try to 
>> register variables in sessions.
>
>It's not my code, it's phpgw 0.9.14
>A simple page with phpinfo() works well.
>
>> I test all code with PHP warnings on. For some errors, that 
>> brings up warnings before Apache explodes and you can fix 
>> the error. It is an extremely useful approach for all 
>> versions of PHP and found a few of the tricky errors in 
>> earlier versions 
>> of PHP 4.
>
>I'd like, but I can't get php to create a log file nor output to EventLog.
>Any idea? I have put the following in the php.ini file:
>
>error_reporting = E_ALL
>display_errors = On
>display_startup_errors = On
>log_errors = On
>error_log = c:\php\php.log
>error_log = syslog
>extension_dir = c:\php\extensions (Is it right?)
>
>Right?
>
>Thanks
>-jec
>
>PS: I normally use Apapche + Linux without problems but I don't have access
>to a Linux box here... So I MUSt use win2k :-(
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>