Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf [SOLVED]
On Wed, 12 Sep 2007 22:45:29 +0200 Zbigniew Szalbot wrote: > > > > Actually, maybe my description should be corrected - that is when I > > > > want to access a directory where index.php resides, apache will just > > > > display this directory content. But when I click (not reload) the php > > > > file, page is loaded correctly. Ah right, that makes more sense, now matching my similar experience :) > > > maybe this was already mentioned, but what do you have DirectoryIndex > > > set to? > > > > > > it should look something like: > > > > > > DirectoryIndex index.html index.php > > > > All is fine here. I do have index.php listed. The file httpd.conf came > > almost without any modification (apart from usual php4 replaced php5 > > references during update). > > I was given advice on php list to comment out everything in mod_dir.c > starting from > > > > > and then enter just this: > > >DirectoryIndex index.php index.php3 index.html index.htm > > > Everything now works very well! Thank you all for your patience with me! Cool. That is why I'd asked earlier to see your section; I'd had exactly that same problem last December, which I solved the long way around, adding what I thought was one way the php5 install could/should have done it (which comes to the same thing, in the end): DirectoryIndex index.php index.php3 index.html DirectoryIndex index.php3 index.html DirectoryIndex index.php index.html DirectoryIndex index.html #% 17/12/6 for php5 .. DirectoryIndex index.php index.html Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf [SOLVED]
On Wednesday 12 September 2007 22:45:29 Zbigniew Szalbot wrote: > Hello, > > 2007/9/12, Zbigniew Szalbot <[EMAIL PROTECTED]>: > > Hi there again, > > > > > > Actually, maybe my description should be corrected - that is when I > > > > want to access a directory where index.php resides, apache will just > > > > display this directory content. But when I click (not reload) the php > > > > file, page is loaded correctly. > > > > > > > >> To try and come to the cause, take Indexes outof Options for a given > > > >> directory/location. It should give a Forbidden at that time, reason > > > >> will be in error log, the exact request should be in access log. > > > >> Look for subtle differences if there are any - between the forbidden > > > >> and the reloaded page (like ending slash or what not). > > > > > > > > I did it for one directory where it was defined and I did get 403 > > > > error. So reading httpd-error.log: > > > > Directory index forbidden by rule: /usr/local/www/data/test/ > > > > > > > > access-log: > > > > "GET / HTTP/1.1" 403 302 > > > > > > > > Maybe I will have to say reconcile with php 4.4.7 after all. > > > > > > maybe this was already mentioned, but what do you have DirectoryIndex > > > set to? > > > > > > it should look something like: > > > > > > DirectoryIndex index.html index.php > > > > All is fine here. I do have index.php listed. The file httpd.conf came > > almost without any modification (apart from usual php4 replaced php5 > > references during update). > > I was given advice on php list to comment out everything in mod_dir.c > starting from > > > > > and then enter just this: > > >DirectoryIndex index.php index.php3 index.html index.htm > > > Everything now works very well! Thank you all for your patience with me! Duh! I hafta remember that. Apparently --enable-versioning doesn't expose "I am mod_php3.c", so Apache bails out on the IfModule mod_php3.c and doesn't even see what's in there. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
On Wednesday 12 September 2007 21:28:45 Eric wrote: > Mel wrote: > > On Wednesday 12 September 2007 09:23:19 Zbigniew Szalbot wrote: > >> Hi there again, > > > > Change the order of the extensions in extensions.ini. Each upgrade the > > order is magically different, but the following comments I've assembled > > over time: $ grep '^;' /usr/local/etc/php/extensions.ini > > ; NOTE: spl makes php coredump if loaded after pspell > > ; NOTE 2: simplexml makes php coredump if loaded after pspell > > > > Yes, pspell is the common factor, but it isn't always. I should've kept > > track, but the binding factor seems to be php extensions using a > > C++-written library. > > Once I see the coredump, I start moving the last extension up and re-run > > php -v. If it's all the way up, take the next extension on the bottom and > > rince and repeat. > > i see the same behavior if session module is loaded after other modules. > Moving things around fixes this. I use the php -v trick as well until > the core dump goes away Correct, it started with session in 5.1.x, only on -cli, so I moved it from extensions.ini to etc/php.ini and *not* in etc/php-cli.ini (cli doesn't need sessions 99.9% of the time anyway). Later another module was the cause, so I started looking into it more. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf [SOLVED]
Hello, 2007/9/12, Zbigniew Szalbot <[EMAIL PROTECTED]>: > Hi there again, > > > > Actually, maybe my description should be corrected - that is when I > > > want to access a directory where index.php resides, apache will just > > > display this directory content. But when I click (not reload) the php > > > file, page is loaded correctly. > > > > > >> To try and come to the cause, take Indexes outof Options for a given > > >> directory/location. It should give a Forbidden at that time, reason will > > >> be > > >> in error log, the exact request should be in access log. Look for subtle > > >> differences if there are any - between the forbidden and the reloaded > > >> page > > >> (like ending slash or what not). > > > > > > I did it for one directory where it was defined and I did get 403 > > > error. So reading httpd-error.log: > > > Directory index forbidden by rule: /usr/local/www/data/test/ > > > > > > access-log: > > > "GET / HTTP/1.1" 403 302 > > > > > > Maybe I will have to say reconcile with php 4.4.7 after all. > > > > > > > > > maybe this was already mentioned, but what do you have DirectoryIndex > > set to? > > > > it should look something like: > > > > DirectoryIndex index.html index.php > > All is fine here. I do have index.php listed. The file httpd.conf came > almost without any modification (apart from usual php4 replaced php5 > references during update). I was given advice on php list to comment out everything in mod_dir.c starting from and then enter just this: DirectoryIndex index.php index.php3 index.html index.htm Everything now works very well! Thank you all for your patience with me! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Hi there again, > > Actually, maybe my description should be corrected - that is when I > > want to access a directory where index.php resides, apache will just > > display this directory content. But when I click (not reload) the php > > file, page is loaded correctly. > > > >> To try and come to the cause, take Indexes outof Options for a given > >> directory/location. It should give a Forbidden at that time, reason will be > >> in error log, the exact request should be in access log. Look for subtle > >> differences if there are any - between the forbidden and the reloaded page > >> (like ending slash or what not). > > > > I did it for one directory where it was defined and I did get 403 > > error. So reading httpd-error.log: > > Directory index forbidden by rule: /usr/local/www/data/test/ > > > > access-log: > > "GET / HTTP/1.1" 403 302 > > > > Maybe I will have to say reconcile with php 4.4.7 after all. > > > > > maybe this was already mentioned, but what do you have DirectoryIndex > set to? > > it should look something like: > > DirectoryIndex index.html index.php All is fine here. I do have index.php listed. The file httpd.conf came almost without any modification (apart from usual php4 replaced php5 references during update). Thanks! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Zbigniew Szalbot wrote: Hello, 2007/9/12, Mel <[EMAIL PROTECTED]>: On Wednesday 12 September 2007 20:51:52 Zbigniew Szalbot wrote: There's only one problem left to be solved - files with php extensions are not really shown in browser until I click RELOAD. Files with html extensions are shown without the need to reload. Thanks for your patience! Actually, maybe my description should be corrected - that is when I want to access a directory where index.php resides, apache will just display this directory content. But when I click (not reload) the php file, page is loaded correctly. To try and come to the cause, take Indexes outof Options for a given directory/location. It should give a Forbidden at that time, reason will be in error log, the exact request should be in access log. Look for subtle differences if there are any - between the forbidden and the reloaded page (like ending slash or what not). I did it for one directory where it was defined and I did get 403 error. So reading httpd-error.log: Directory index forbidden by rule: /usr/local/www/data/test/ access-log: "GET / HTTP/1.1" 403 302 Maybe I will have to say reconcile with php 4.4.7 after all. maybe this was already mentioned, but what do you have DirectoryIndex set to? it should look something like: DirectoryIndex index.html index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Hello, 2007/9/12, Mel <[EMAIL PROTECTED]>: > On Wednesday 12 September 2007 20:51:52 Zbigniew Szalbot wrote: > > > There's only one problem left to be solved - files with php extensions > > are not really shown in browser until I click RELOAD. Files with html > > extensions are shown without the need to reload. Thanks for your > > patience! Actually, maybe my description should be corrected - that is when I want to access a directory where index.php resides, apache will just display this directory content. But when I click (not reload) the php file, page is loaded correctly. > > To try and come to the cause, take Indexes outof Options for a given > directory/location. It should give a Forbidden at that time, reason will be > in error log, the exact request should be in access log. Look for subtle > differences if there are any - between the forbidden and the reloaded page > (like ending slash or what not). I did it for one directory where it was defined and I did get 403 error. So reading httpd-error.log: Directory index forbidden by rule: /usr/local/www/data/test/ access-log: "GET / HTTP/1.1" 403 302 Maybe I will have to say reconcile with php 4.4.7 after all. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
On Wednesday 12 September 2007 20:51:52 Zbigniew Szalbot wrote: > There's only one problem left to be solved - files with php extensions > are not really shown in browser until I click RELOAD. Files with html > extensions are shown without the need to reload. Thanks for your > patience! To try and come to the cause, take Indexes outof Options for a given directory/location. It should give a Forbidden at that time, reason will be in error log, the exact request should be in access log. Look for subtle differences if there are any - between the forbidden and the reloaded page (like ending slash or what not). -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Mel wrote: On Wednesday 12 September 2007 09:23:19 Zbigniew Szalbot wrote: Hi there again, Change the order of the extensions in extensions.ini. Each upgrade the order is magically different, but the following comments I've assembled over time: $ grep '^;' /usr/local/etc/php/extensions.ini ; NOTE: spl makes php coredump if loaded after pspell ; NOTE 2: simplexml makes php coredump if loaded after pspell Yes, pspell is the common factor, but it isn't always. I should've kept track, but the binding factor seems to be php extensions using a C++-written library. Once I see the coredump, I start moving the last extension up and re-run php -v. If it's all the way up, take the next extension on the bottom and rince and repeat. i see the same behavior if session module is loaded after other modules. Moving things around fixes this. I use the php -v trick as well until the core dump goes away ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
On Wednesday 12 September 2007 09:23:19 Zbigniew Szalbot wrote: > Hi there again, > > 2007/9/12, Ian Smith <[EMAIL PROTECTED]>: > > On Tue, 11 Sep 2007 19:19:32 +0200 Zbigniew Szalbot wrote: > > > I decided to upgrade my home machine to php5.2.3 from 4.4.7. All went > > > fine. I had one error about hash extension already loaded which I > > > solved by deleting a duplicated entry from extensions.ini. The curious > > > thing is that once apache has been restarted, if I want to load a > > > website which resides on this box, it behaves as if no php was enabled > > > in apache. In other words I can see the directory content (files > > > present in a given directory) despite index.php being there. What is > > > more strange is that when I click reload, the website is indeed loaded > > > into browser! So when I first type an URL, it shows directory content. > > > After hitting reload in browser (tested with both FF and IE), the page > > > is shown. > > > > Except for the reload bit - perhaps I never tried that - I've been here. > > > > > My first thought was checking httpd.conf > > > > > > > > > DirectoryIndex index.php index.php3 index.html > > > > > > > > > and also > > > AddType application/x-tar .tgz > > > AddType application/x-httpd-php .php > > > AddType application/x-httpd-php-source .phps > > > > The latter AddTypes should be within section? > > No, it wasn't in there but I moved it to this section. There is no > difference. I cannot start apache. > > > index.php3 there looks a bit odd, unless you're supporting some old > > .php3 scripts? If you're then still having trouble, show us the whole > > .. section? > > > > For a php4 to php5 update, make sure you also have such as: > > > > #LoadModule php4_module libexec/apache/libphp4.so > > LoadModule php5_module libexec/apache/libphp5.so > > > > and > > > > #AddModule mod_php4.c > > AddModule mod_php5.c > > > > And check that /usr/local/libexec/apache/libphp5.so exists! > > Everything is fine here. But I think now that the problem is not with > apache but with php. It does not even matter if I do start or > startssl. In both instances the httpd server dies. The reason I think > it is php-related is that when I issue php -v I get: > > PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52) > Copyright (c) 1997-2007 The PHP Group > Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies > Segmentation fault (core dumped) Change the order of the extensions in extensions.ini. Each upgrade the order is magically different, but the following comments I've assembled over time: $ grep '^;' /usr/local/etc/php/extensions.ini ; NOTE: spl makes php coredump if loaded after pspell ; NOTE 2: simplexml makes php coredump if loaded after pspell Yes, pspell is the common factor, but it isn't always. I should've kept track, but the binding factor seems to be php extensions using a C++-written library. Once I see the coredump, I start moving the last extension up and re-run php -v. If it's all the way up, take the next extension on the bottom and rince and repeat. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Dear Ian and others, 2007/9/12, Ian Smith <[EMAIL PROTECTED]>: > On Wed, 12 Sep 2007 09:23:19 +0200 Zbigniew Szalbot wrote: > > 2007/9/12, Ian Smith <[EMAIL PROTECTED]>: > > > On Tue, 11 Sep 2007 19:19:32 +0200 Zbigniew Szalbot wrote: > [..] > > No, it wasn't in there but I moved it to this section. There is no > > difference. I cannot start apache. > [..] > > > And check that /usr/local/libexec/apache/libphp5.so exists! > > > > Everything is fine here. But I think now that the problem is not with > > apache but with php. It does not even matter if I do start or > > startssl. In both instances the httpd server dies. The reason I think > > it is php-related is that when I issue php -v I get: > > > > PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52) > > Copyright (c) 1997-2007 The PHP Group > > Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies > > Segmentation fault (core dumped) > > Well it's broken for sure if php -v dumps .. and if php cli is broken > most likely the module is too, which may well explain apache crashing .. > > > pkg_info | grep php5 > > php5-5.2.3_1PHP Scripting Language (Apache Module and CLI) > > > > I do not really feel like upgrading apache (as suggested by someone > > else - thank you by the way) because it is just a home machine on > > which I do not need all the greatest and latest. > > > > If there's nothing obvious that comes to your mind I will try posting > > it on a php list. > > Sorry, I'm on digests here which can take half a day unless you cc me, > so I hope you've made some progress by now .. no, nothing obvious, but: > > I'd be trying to separate these two problems: save configs, comment out > all of the php stuff in httpd.conf and get your upgraded apache up and > running properly first, then refetch / reinstall / reconfigure php5? I commented out all extensions and then brought them in one by one. The one which was causing core dumps was simplexml.so. I had a few others that I had to comment as otherwise they were giving me trouble (because of the simplexml being commented out I guess): pdo.so, pdo_sqlite.so, spl.so, mysqli.so, sqlite.so. I am not really worried about these. I am not really sure if I will ever need them. So fine for the time being. php -v does not produce core dumps and I can start apache. There's only one problem left to be solved - files with php extensions are not really shown in browser until I click RELOAD. Files with html extensions are shown without the need to reload. Thanks for your patience! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
On Wed, 12 Sep 2007 09:23:19 +0200 Zbigniew Szalbot wrote: > 2007/9/12, Ian Smith <[EMAIL PROTECTED]>: > > On Tue, 11 Sep 2007 19:19:32 +0200 Zbigniew Szalbot wrote: [..] > No, it wasn't in there but I moved it to this section. There is no > difference. I cannot start apache. [..] > > And check that /usr/local/libexec/apache/libphp5.so exists! > > Everything is fine here. But I think now that the problem is not with > apache but with php. It does not even matter if I do start or > startssl. In both instances the httpd server dies. The reason I think > it is php-related is that when I issue php -v I get: > > PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52) > Copyright (c) 1997-2007 The PHP Group > Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies > Segmentation fault (core dumped) Well it's broken for sure if php -v dumps .. and if php cli is broken most likely the module is too, which may well explain apache crashing .. > pkg_info | grep php5 > php5-5.2.3_1PHP Scripting Language (Apache Module and CLI) > > I do not really feel like upgrading apache (as suggested by someone > else - thank you by the way) because it is just a home machine on > which I do not need all the greatest and latest. > > If there's nothing obvious that comes to your mind I will try posting > it on a php list. Sorry, I'm on digests here which can take half a day unless you cc me, so I hope you've made some progress by now .. no, nothing obvious, but: I'd be trying to separate these two problems: save configs, comment out all of the php stuff in httpd.conf and get your upgraded apache up and running properly first, then refetch / reinstall / reconfigure php5? Good luck, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
On Sep 12, 2007, at 3:23 AM, Zbigniew Szalbot wrote: Everything is fine here. But I think now that the problem is not with apache but with php. It does not even matter if I do start or startssl. In both instances the httpd server dies. The reason I think it is php-related is that when I issue php -v I get: PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52) Copyright (c) 1997-2007 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies Segmentation fault (core dumped) pkg_info | grep php5 php5-5.2.3_1PHP Scripting Language (Apache Module and CLI) I do not really feel like upgrading apache (as suggested by someone else - thank you by the way) because it is just a home machine on which I do not need all the greatest and latest. If there's nothing obvious that comes to your mind I will try posting it on a php list. Can you make a copy of /usr/local/etc/php/extensions.ini and put an empty extensions.ini in it's place? This will turn off all of the PHP extensions. The last time I experienced core dumps in Apache after an upgrade of my PHP install was when some of my PHP Extensions didn't get rebuilt. If Apache starts with PHP working (but without extensions) then you can narrow down which extensions didn't get rebuilt when you upgraded to /usr/ports/lang/php5-extensions. Best, -Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Hi there again, 2007/9/12, Ian Smith <[EMAIL PROTECTED]>: > On Tue, 11 Sep 2007 19:19:32 +0200 Zbigniew Szalbot wrote: > > > I decided to upgrade my home machine to php5.2.3 from 4.4.7. All went > > fine. I had one error about hash extension already loaded which I > > solved by deleting a duplicated entry from extensions.ini. The curious > > thing is that once apache has been restarted, if I want to load a > > website which resides on this box, it behaves as if no php was enabled > > in apache. In other words I can see the directory content (files > > present in a given directory) despite index.php being there. What is > > more strange is that when I click reload, the website is indeed loaded > > into browser! So when I first type an URL, it shows directory content. > > After hitting reload in browser (tested with both FF and IE), the page > > is shown. > > Except for the reload bit - perhaps I never tried that - I've been here. > > > My first thought was checking httpd.conf > > > > > > DirectoryIndex index.php index.php3 index.html > > > > > > and also > > AddType application/x-tar .tgz > > AddType application/x-httpd-php .php > > AddType application/x-httpd-php-source .phps > > The latter AddTypes should be within section? No, it wasn't in there but I moved it to this section. There is no difference. I cannot start apache. > > index.php3 there looks a bit odd, unless you're supporting some old > .php3 scripts? If you're then still having trouble, show us the whole > .. section? > > For a php4 to php5 update, make sure you also have such as: > > #LoadModule php4_module libexec/apache/libphp4.so > LoadModule php5_module libexec/apache/libphp5.so > > and > > #AddModule mod_php4.c > AddModule mod_php5.c > > And check that /usr/local/libexec/apache/libphp5.so exists! Everything is fine here. But I think now that the problem is not with apache but with php. It does not even matter if I do start or startssl. In both instances the httpd server dies. The reason I think it is php-related is that when I issue php -v I get: PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52) Copyright (c) 1997-2007 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies Segmentation fault (core dumped) pkg_info | grep php5 php5-5.2.3_1PHP Scripting Language (Apache Module and CLI) I do not really feel like upgrading apache (as suggested by someone else - thank you by the way) because it is just a home machine on which I do not need all the greatest and latest. If there's nothing obvious that comes to your mind I will try posting it on a php list. Thank you! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Zbigniew Szalbot wrote: Hello again, 2007/9/11, Zbigniew Szalbot <[EMAIL PROTECTED]>: Dear all, My next (not so brillian thought) was to refresh apache. And when I now try to start apache, I get core dumps.. Sep 11 21:47:45 szalbot kernel: pid 71766 (httpd), uid 0: exited on signal 11 (core dumped) $ httpd -v Server version: Apache/1.3.39 (Unix) Server built: Sep 11 2007 20:48:37 I guess I should be asking on the apache list by now? Thanks! Zbigniew Szalbot Why not upgrade to a modern version of apache and see if that clears it up? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf
Hello again, 2007/9/11, Zbigniew Szalbot <[EMAIL PROTECTED]>: > Dear all, > > I decided to upgrade my home machine to php5.2.3 from 4.4.7. All went > fine. I had one error about hash extension already loaded which I > solved by deleting a duplicated entry from extensions.ini. The curious > thing is that once apache has been restarted, if I want to load a > website which resides on this box, it behaves as if no php was enabled > in apache. In other words I can see the directory content (files > present in a given directory) despite index.php being there. What is > more strange is that when I click reload, the website is indeed loaded > into browser! So when I first type an URL, it shows directory content. > After hitting reload in browser (tested with both FF and IE), the page > is shown. > > My first thought was checking httpd.conf > > > DirectoryIndex index.php index.php3 index.html > > > and also > AddType application/x-tar .tgz > AddType application/x-httpd-php .php > AddType application/x-httpd-php-source .phps > > So I am a bit stuck as to what may cause this strange behaviour. I am running: > PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 11 2007 17:36:31) > Copyright (c) 1997-2007 The PHP Group > Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies > > Server version: Apache/1.3.37 (Unix) > Server built: Jun 27 2007 07:58:38 > > FreeBSD 6.2-RELEASE-p6 #4 > /usr/obj/usr/src/sys/SZALBOT > > httpd-error.log does not show any error despite having error_reporting > = E_ALL & ~E_NOTICE set in php.ini. > > Many thanks in advance! My next (not so brillian thought) was to refresh apache. And when I now try to start apache, I get core dumps.. Sep 11 21:47:45 szalbot kernel: pid 71766 (httpd), uid 0: exited on signal 11 (core dumped) $ httpd -v Server version: Apache/1.3.39 (Unix) Server built: Sep 11 2007 20:48:37 I guess I should be asking on the apache list by now? Thanks! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
