Re: Another PHP5 problem
At 06:49 PM 6/17/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: [snip out a lot] What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Me I just bit the bullet and went with the new locations as they were installed as defaults. I moved my content to the location. None of my content cared about the underlying file system path, however there is code that does. When faced with this most of the time there is some configuration utility that can be run to make changes, with the actual data you enter being stored in a database backend. This then becomes a choice of is it easier to simply modify the docroot in the .conf files?, if you have this situation. -Mike Just a follow-up on my own experience with upgrade to apache22 and its change of path. I was just overthinking it. Simply changing the doc root in the main httpd conf to match my exising one worked beautifully with any concern about moving content around and breaking the system path for scripts and things. By modifying the www/apache22/data back to www/data left everything as was. My production servers are now updated this way. My web serving was only down for a few minutes as I left apache2 running in memory. I simply uploaded copies of all of my tested .conf files from the test server before installing apache22. Also first made the minor changes needed to the main conf and vhost.conf. Killed the apache2 and voila! Thanks for your version of the process, but thought I'd post mine here too just in case there is anyone left on the planet besides me that hasn't already upgraded to apache22. Truly it doesn't pay to get too far behind on upgrades (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 06:49 PM 6/17/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: [snip] Oh, forgot that I did have to struggle apache22 still wanted to install db42 instead of my db46 and caused the apache22 build to stop. After a bit of looking, the problem wasn't with the apache22 Makefile but with the apr1 Makefile. Way down it called for db42+ which I suppose meant at LEAST db42. Instead apache22 saw it as db42 literally. A change in the apr1 Makefile to db46 specifically fixed things. This caused my earlier problems I mentioned, but I didn't yet know why. (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:12 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: snip out a lot Sorry to return with one more question about upgrading to apache22 from apache2. A note of concern was that apache22 changes the path to the document root by inserting ../www/apache22/data versus the previous ../www/data doc root. Of course my vhosts and a bunch of other things of importance now reside within the ../www path. I suppose I can change the doc root within the apache22 config file(s) but I can forsee some possible breakage in things on a production server when before, when moving from apache-1.3 to apache2, web things were put in the same path and without any modifications needed. I suppose this only affects the main host server stuff and things left in the ../www placement will still work as before according to the present setup. In examining the apache22 Makefile I see some places that the path might be changed, but don't know if that is the best idea vs maybe changing the doc root in apache22 config. A 3rd choice is to move stuff contained in the ../www/cgi-bin phpMyAdmin ...etc things that the main host needs to find in the new location. What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Methinks this is my last question before moving to production servers. Appreciate your further comments (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:12 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: snip out a lot Sorry to return with one more question about upgrading to apache22 from apache2. A note of concern was that apache22 changes the path to the document root by inserting ../www/apache22/data versus the previous ../www/data doc root. Of course my vhosts and a bunch of other things of importance now reside within the ../www path. I suppose I can change the doc root within the apache22 config file(s) but I can forsee some possible breakage in things on a production server when before, when moving from apache-1.3 to apache2, web things were put in the same path and without any modifications needed. I suppose this only affects the main host server stuff and things left in the ../www placement will still work as before according to the present setup. In examining the apache22 Makefile I see some places that the path might be changed, but don't know if that is the best idea vs maybe changing the doc root in apache22 config. A 3rd choice is to move stuff contained in the ../www/cgi-bin phpMyAdmin ...etc things that the main host needs to find in the new location. What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Methinks this is my last question before moving to production servers. Appreciate your further comments (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:12 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: snip out a lot Sorry to return with one more question about upgrading to apache22 from apache2. A note of concern was that apache22 changes the path to the document root by inserting ../www/apache22/data versus the previous ../www/data doc root. Of course my vhosts and a bunch of other things of importance now reside within the ../www path. I suppose I can change the doc root within the apache22 config file(s) but I can forsee some possible breakage in things on a production server when before, when moving from apache-1.3 to apache2, web things were put in the same path and without any modifications needed. I suppose this only affects the main host server stuff and things left in the ../www placement will still work as before according to the present setup. In examining the apache22 Makefile I see some places that the path might be changed, but don't know if that is the best idea vs maybe changing the doc root in apache22 config. A 3rd choice is to move stuff contained in the ../www/cgi-bin phpMyAdmin ...etc things that the main host needs to find in the new location. What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Methinks this is my last question before moving to production servers. Appreciate your further comments (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 07:26 PM 6/17/2011 -0500, Jack L. Stone wrote: OUCH! I hipe my last email really didn't go out 3 times. Mail server wasn't resolving properly, so had tried different ones. Sorry (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:12 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: snip out a lot Sorry to return with one more question about upgrading to apache22 from apache2. A note of concern was that apache22 changes the path to the document root by inserting ../www/apache22/data versus the previous ../www/data doc root. Of course my vhosts and a bunch of other things of importance now reside within the ../www path. I suppose I can change the doc root within the apache22 config file(s) but I can forsee some possible breakage in things on a production server when before, when moving from apache-1.3 to apache2, web things were put in the same path and without any modifications needed. I suppose this only affects the main host server stuff and things left in the ../www placement will still work as before according to the present setup. In examining the apache22 Makefile I see some places that the path might be changed, but don't know if that is the best idea vs maybe changing the doc root in apache22 config. A 3rd choice is to move stuff contained in the ../www/cgi-bin phpMyAdmin ...etc things that the main host needs to find in the new location. What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Methinks this is my last question before moving to production servers. Appreciate your further comments (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
That would explain the three different quote times in them. Yes it did, but I'm not concerned. On Jun 17, 2011, at 9:51 AM, Jack L. Stone wrote: At 07:26 PM 6/17/2011 -0500, Jack L. Stone wrote: OUCH! I hipe my last email really didn't go out 3 times. Mail server wasn't resolving properly, so had tried different ones. Sorry (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
Jack L. Stone wrote: [snip] A note of concern was that apache22 changes the path to the document root by inserting ../www/apache22/data versus the previous ../www/data doc root. Of course my vhosts and a bunch of other things of importance now reside within the ../www path. I suppose I can change the doc root within the apache22 config file(s) but I can forsee some possible breakage in things on a production server when before, when moving from apache-1.3 to apache2, web things were put in the same path and without any modifications needed. I suppose this only affects the main host server stuff and things left in the ../www placement will still work as before according to the present setup. In examining the apache22 Makefile I see some places that the path might be changed, but don't know if that is the best idea vs maybe changing the doc root in apache22 config. A 3rd choice is to move stuff contained in the ../www/cgi-bin phpMyAdmin ...etc things that the main host needs to find in the new location. What did you fellows do about this issue that worked best for you assuming y'all had vhosts and similar stuff to worry about? Me I just bit the bullet and went with the new locations as they were installed as defaults. I moved my content to the location. None of my content cared about the underlying file system path, however there is code that does. When faced with this most of the time there is some configuration utility that can be run to make changes, with the actual data you enter being stored in a database backend. This then becomes a choice of is it easier to simply modify the docroot in the .conf files?, if you have this situation. I made the choice I did because none of my code cared. My thinking was it would be better to have this arrangement in place for catastrophe requiring a complete reinstall from scratch. Changing the docroot in the .conf files (vhosts have docroot and Directory directives as well) is not as dangerous as it sounds. For example, when you change httpd.conf and later attempt to pkg_delete or deinstall the port you'll see a message about it not matching the checksum of the original and it will be left intact and not deleted. Same goes for updating with portupgrade, it will not replace your changed files either. So my first choice would be use the new layout and move file content. If this creates more problems than it's worth because too much code relies on being aware of the underlying file system, changing the docroot in the .conf files is the lesser of two evils but not as dangerous as it sounds. Methinks this is my last question before moving to production servers. You're doing it right by testing with a test server first. I only have 7 FreeBSD servers at work (we're a winderZ shop) with 2 at home. The 2 at home are close to being exactly the same as the ones at work in that the same environment and apps are installed with configurations pretty much the same. I use portupgrade for maintenance and upgrades. I've learned over time one trick with portupgrade is to check often, and upgrade in very small batches. I've noticed a higher probability of a hiccup when too much time goes by and now a hundred things all need updating at the same time. Update policies and procedures will vary by shop, such as doing a dump for being able to roll back, etc. What I do is test out any potential update on the servers at home first. If I get the warm fuzzy and everything is smooth I will then do the ones at work. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
I have very few uses for sqlite3 but I still have them. And PDO? Never seen anything run it. Some pretty big projects including Drupal CMS are moving to PDO. I reckon that having other options without reinventing the wheel, than one certain Oracle controlled DB-backend is starting to gain momentum. Just as a sidenote, PHP 5.3.6 so far seems to be unaffected by extension loading order, but looks like that any upgrade of apache, apr, php etc. means that every dependent module downstream has to be recompiled as well. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 03:41 PM 6/16/2011 +0300, Reko Turja wrote: I have very few uses for sqlite3 but I still have them. And PDO? Never seen anything run it. Some pretty big projects including Drupal CMS are moving to PDO. I reckon that having other options without reinventing the wheel, than one certain Oracle controlled DB-backend is starting to gain momentum. Just as a sidenote, PHP 5.3.6 so far seems to be unaffected by extension loading order, but looks like that any upgrade of apache, apr, php etc. means that every dependent module downstream has to be recompiled as well. -Reko With upgrade to php5-5.3.6 is the first time ever (many years) I've had any problem with php. The order of the extensions never came up as an issue, nor did it once I found the extensions causing the seg faults and core dumps. Ryan's suggestion of commenting out all of the extensions and then adding back 1 by 1 enabled me to find the offenders quickly. The 2 sqlite extensions caused the problem for me there also was a 3rd one and I removed them all as I don't use that database. For ports, I usually go with the defaults on options unless I KNOW what they do or don't do. Have used the same options and didn't know why the sqlites were added this time. That further cause an install of the core sqlite port. Without removing it, I couldn't delete the inclusion of the sqlite extensions. Now, I wrestling with the apache2 and apr0 issue. The apache port Makefile wants apr0, but it now has vulnablilities. Ports UPDATING says to do this with apr: - remove apache2 and then: portupgrade -f -o devel/apr1 devel/apr ...and then reinstall apache2. That didn't work because the Makefile in apache still wants apr0. I changed the Makefile to apr1 but the build failed after it looked again for that apr0 later in the build. I didn't find another call for apr0. What have others done for this? This is about the last issue I know about after the major upgrade of the ports. Thanks for all the help so far -- just any other help on the apr thingy would be nice. Yes, I have googled and always do before going to the trough here. Thanks again! (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
Now, I wrestling with the apache2 and apr0 issue. The apache port Makefile wants apr0, but it now has vulnablilities. Ports UPDATING says to do this with apr: - remove apache2 and then: portupgrade -f -o devel/apr1 devel/apr ...and then reinstall apache2. That didn't work because the Makefile in apache still wants apr0. I changed the Makefile to apr1 but the build failed after it looked again for that apr0 later in the build. I didn't find another call for apr0. Apache 2, not Apache 2.2? Could you consider upgrade - haven't had any problems with that version in several years now. Of course, everything depending on apache needs recompile afterwards. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
Jack L. Stone wrote: [snip] Now, I wrestling with the apache2 and apr0 issue. The apache port Makefile wants apr0, but it now has vulnablilities. Ports UPDATING says to do this with apr: - remove apache2 and then: portupgrade -f -o devel/apr1 devel/apr ...and then reinstall apache2. That didn't work because the Makefile in apache still wants apr0. I changed the Makefile to apr1 but the build failed after it looked again for that apr0 later in the build. I didn't find another call for apr0. What have others done for this? This is about the last issue I know about after the major upgrade of the ports. Thanks for all the help so far -- just any other help on the apr thingy would be nice. Yes, I have googled and always do before going to the trough here. I seem to remember vaguely going through this once upon a time, I believe it was circa trying to move from apache 1.3.xx to apache 2.0. apr0 was for 1.3 and apr1 was for apache 2.0. I seem to recall a chicken and egg scenario about installing the apr(x) port first, then during the apache install it tried to install it again. Back then the apache 2.0 would mistakenly go looking for apr0 the second time unless there was something like a USE_APACHE= 20 (or something like that) in make.conf. I remember chasing my tail on that one. I think later the USE_APACHE= 20 became deprecated and APACHE_PORT=www/apache22 replaced it. Really, apache2 is dated. Apache22 is now the default. You would only require the make.conf entries described above to force a change from default(22). It doesn't have the problems you're having. If you are at this stage you should really make the move to apache22. Be advised though, it pulls in a few more dependencies than I'd really like, especially the apr1 (now named apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12) port installing Python27. You might have to make a couple of twiddles on .conf files but it is something easy to do. But the sticky point is the apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12 is the new apr1 port for apache22 installs, not the old devel/apr(x) - those are for 1.3 and 2.0 and will need the make.conf entry (22 won't need anything). At any rate take a gander at /usr/ports/Mk/bsd.apache.mk for more info. But if it were me instead of fighting I'd just go with the apache22 default instead of struggling with apache20. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
From: Michael Powell nightre...@hotmail.com pulls in a few more dependencies than I'd really like, especially the apr1 (now named apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12) port installing The name depends completely on the knobs you have used with portbuild - my apr is: apr-ipv6-devrandom-db43-pgsql84-sqlite3-1.4.5.1.3.12 At any rate take a gander at /usr/ports/Mk/bsd.apache.mk for more info. But if it were me instead of fighting I'd just go with the apache22 default Yeah - the configuration differences are pretty minimal and even the 2.0 port makefile states now: DEPRECATED= will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 06:18 PM 6/16/2011 +0300, Reko Turja wrote: From: Michael Powell nightre...@hotmail.com pulls in a few more dependencies than I'd really like, especially the apr1 (now named apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12) port installing The name depends completely on the knobs you have used with portbuild - my apr is: apr-ipv6-devrandom-db43-pgsql84-sqlite3-1.4.5.1.3.12 At any rate take a gander at /usr/ports/Mk/bsd.apache.mk for more info. But if it were me instead of fighting I'd just go with the apache22 default Yeah - the configuration differences are pretty minimal and even the 2.0 port makefile states now: DEPRECATED= will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now -Reko Thanks to both you and Mike for the advice. I've already installed apache22 on a test server and trying to allocate time to it as and when. Looks like this apr thing is going to raise the priority. Also, I see the sqlite3 is tacked on the apr you have. I only have: apr-ipv6-devrandom-gdbm-db46-mysql50-1.4.5.1.3.12 What are all of those conf files in the apache22/extra directory? Any includes needed there besides perhaps the ssl if used? Thanks guys! Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
From: Jack L. Stone ja...@sage-american.com Also, I see the sqlite3 is tacked on the apr you have. I only have: apr-ipv6-devrandom-gdbm-db46-mysql50-1.4.5.1.3.12 Yeah when I ran make config for apr I selected sqlite as I had it already installed for stuff where I might need SQL capabilities, but full blown server is too 'heavy'. What are all of those conf files in the apache22/extra directory? Any includes needed there besides perhaps the ssl if used? Check those through, just in case there are some options you might want to include or are already using. I've moved the ones I needed to the Includes subdir and kept extra purely as a storage for originals. But sadly can't help more with the needed extra includes as those are so much dependent on your needs and setup. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
Jack L. Stone wrote: [snip] Thanks to both you and Mike for the advice. I've already installed apache22 on a test server and trying to allocate time to it as and when. Looks like this apr thing is going to raise the priority. You shouldn't have any of these apr problems with 22. Also, I see the sqlite3 is tacked on the apr you have. I only have: apr-ipv6-devrandom-gdbm-db46-mysql50-1.4.5.1.3.12 The name depends completely on the knobs you have used with portbuild - my apr is: apr-ipv6-devrandom-db43-pgsql84-sqlite3-1.4.5.1.3.12 Depends on what knobs you chose during the make config stage. What are all of those conf files in the apache22/extra directory? Any includes needed there besides perhaps the ssl if used? These are essentially just the big httpd.conf of old broken into separate sections. Many are not needed. You'll probably need httpd-default.conf, httpd-ssl.conf, httpd-mpm.conf at the bare minimum. If you are running any vhosts their configs will be in httpd-vhosts.conf. The no-accf.conf under includes is for if you do not desire to use either of the AcceptFilter choices, one for httpd the other for SSL traffic. These can be loaded as kernel modules in /boot/loader.conf as such: accf_http_load=YES accf_data_load=YES When there is a problem with these Apache will emit an error warning, but will operate OK. They are supposed to provide some small measure of performance improvement. What I've noticed is I never seem to get any warning when I boot a machine and Apache starts right up. I've only ever seen a warning occassionally when restarting. the no-accf.conf is simply telling Apache not to look for these modules. If you load these kernel modules simply comment out the 'Include' line at the bottom of httpd.conf. The structure of the .conf file storage has changed, but once you look at the individual files themselves a lot of it is familiar, just divided up into pieces. There have been new and changed Directives from Apache 13, 20, and 22. What I did was to let apache22 install all it's default files and then just migrated over settings from backup copies of what I had in place beforehand. One thing you'll want to know for the future - When you did make config to set the options for the Apache build the config gets saved as an 'options' file under /var/db/ports/apache22. There is a corresponding one for apr. Any additional extra build options not set here should be set in /etc/make.conf. Now I am remiss at going over and comparing mine for dupes and misfits, but by way of example my make.conf has this section in it: #For Apache-2.2.9 Build WITH_MPM=event WITH_THREADS=yes WITHOUT_AUTHN_MODULES=yes WITH_CUSTOM_AUTHZ=authz_host WITHOUT_DAV_MODULES=yes WITHOUT_LDAP_MODULES=yes #WITH_PROXY_MODULES=yes #WITHOUT_SUEXEC_MODULES=yes WITH_THREADS_MODULES=yes WITH_CACHE_MODULES=yes WITH_SSL_MODULES=yes WITH_AUTH_MODULES=yes WITH_MISC_MODULES=yes WITH_CUSTOM_EXPERIMENTAL=ext_filter As you can see it's old. The advantage of having these 2 configs stored is from now on out when you do a portupgrade it will be pretty automagical. I've portupgraded since 2.2.9 and never had to mess with fixing anything! Also, I would suspect your apr was just built with whatever the port maintainer has set as defaults if you just launched the Apache build and it built the apr port as a dependency. You can set your own if you build and do a 'make config' in the apr port first, or you could also do 'make config recursive' when beginning the Apache build and this allows to set dependency options ahead of time. The first time a port is built and there are no saved 'options' file it will display the build options for you to choose. Once this file exists you need to do 'make config' to bring that screen up again. A 'make config recursive' will walk the dependency tree and show you them all. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: -Mike Mike, very useful info. I had surmised about the extra .configs to reduce the size of the main config file. I had already started doing that with apache2. Have been studying the files and comparing to my present httpd.conf and do see some changes that I suppose will emerge should they be needed. Some lines/sections just have been moved around. Again, thanks for taking the time with the info. Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: The no-accf.conf under includes is for if you do not desire to use either of the AcceptFilter choices, one for httpd the other for SSL traffic. These can be loaded as kernel modules in /boot/loader.conf as such: accf_http_load=YES accf_data_load=YES Mike Mike: Got the apache22 configured on the test server with one exception being the error I keep getting regarding this one: [warn] (22)Invalid argument: Failed to enable the 'httpready' Accept Filter I first loaded it in the kernel via kldload: # kldload accf_http The first apache22 restart didn't have the error, but returned on other restarts. Can't seem to unload the line from the kernel and add to the boot loader.conf. What did I do wrong? Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
The no-accf.conf under includes is for if you do not desire to use either of the AcceptFilter choices, one for httpd the other for SSL traffic. These can be loaded as kernel modules in /boot/loader.conf as such: accf_http_load=YES accf_data_load=YES You can also build the modules into kernel itself with: #Apache kernel modules options ACCEPT_FILTER_HTTP options ACCEPT_FILTER_DATA I reckon that the thing you are missing is kernel rebuild and reinstall. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
Jack L. Stone wrote: At 12:56 PM 6/16/2011 -0400, Michael Powell wrote: Jack L. Stone wrote: The no-accf.conf under includes is for if you do not desire to use either of the AcceptFilter choices, one for httpd the other for SSL traffic. These can be loaded as kernel modules in /boot/loader.conf as such: accf_http_load=YES accf_data_load=YES Mike Mike: Got the apache22 configured on the test server with one exception being the error I keep getting regarding this one: [warn] (22)Invalid argument: Failed to enable the 'httpready' Accept Filter I first loaded it in the kernel via kldload: # kldload accf_http The first apache22 restart didn't have the error, but returned on other restarts. Can't seem to unload the line from the kernel and add to the boot loader.conf. What did I do wrong? The /boot/loader.conf is just a text file that you add lines of text. It is read and stuff done only at boot. When these modules are loaded at boot you do not need to kldload them. Nearest thing I can figure is they need to be loaded at boot, then Apache gets started right after. When this sequence applies there will not be these messages. For a server that stays up and online all the time this is not a problem. The only time I've ever seen this error is on apachectl restarts at times other than booting. And I don't really know why either. Strictly speaking these thing are not required, they are only supposedly some small performance enhancer. I have also never seen Apache actually fail or exhibit any problems even in spite of this error message. But I don't apachectl restart (or reboot for that matter) very often. You could just as easily forgo this, e.g. not load the kernel modules and leave the Include etc/apache22/Includes/*.conf line in your httpd.conf and never notice any difference. This will load the no-accf.conf files from the includes directory and tell Apache not to look for these modules. Whether and/or how much these actually help Apache is probably debatable. They are supposed to be helpful performance-wise, but as to how much I couldn't say. But I have never seen this error/warning message actually be related to any problem, and since I don't reboot or restart all the time I don't get them. You could just as easily forego using them and probably never notice. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 10:57 PM 6/16/2011 +0300, Reko Turja wrote: The no-accf.conf under includes is for if you do not desire to use either of the AcceptFilter choices, one for httpd the other for SSL traffic. These can be loaded as kernel modules in /boot/loader.conf as such: accf_http_load=YES accf_data_load=YES You can also build the modules into kernel itself with: #Apache kernel modules options ACCEPT_FILTER_HTTP options ACCEPT_FILTER_DATA I reckon that the thing you are missing is kernel rebuild and reinstall. -Reko Hi, Reko: Was hoping to avoid that, but really no biggie. Thanks! Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Another PHP5 problem
I just finished some major upgrades/updates to a server, including php5-5.3.6 and apache2. Now I keep getting Segmentation faults and core dumps whenever apache2 rolls over its logs and does a restart. Here's the error. Does nyone have an idea of what's happening to cause this?: PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14) Copyright (c) 1997-2011 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by ionCube Ltd. Segmentation fault (core dumped) Thanks for any hints Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
On Wed, 15 Jun 2011 09:04:01 -0500, Jack L. Stone ja...@sage-american.com wrote: with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by ionCube Ltd. ionCube causes all kinds of neat things like this. Disable it and I bet it won't happen. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
On 15/06/2011 15:04, Jack L. Stone wrote:
PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by
ionCube Ltd.
Segmentation fault (core dumped)
Check the mailing list archives for very many discussions on the effect
of having the extensions listed in ${PREFIX}/etc/php/extensions.ini
in the wrong order.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
RE: Another PHP5 problem
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Jack L. Stone Sent: June 15, 2011 10:04 AM To: freebsd-questions@freebsd.org Subject: Another PHP5 problem I just finished some major upgrades/updates to a server, including php5-5.3.6 and apache2. Now I keep getting Segmentation faults and core dumps whenever apache2 rolls over its logs and does a restart. Here's the error. Does nyone have an idea of what's happening to cause this?: PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14) Copyright (c) 1997-2011 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by ionCube Ltd. Segmentation fault (core dumped) Thanks for any hints Jack I would recommend that you recompile php/apache with the minimal necessary options. I've seen many issues in the past when combining multiple modules/extensions together. T. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 03:33 PM 6/15/2011 +0100, Matthew Seaman wrote:
On 15/06/2011 15:04, Jack L. Stone wrote:
PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by
ionCube Ltd.
Segmentation fault (core dumped)
Check the mailing list archives for very many discussions on the effect
of having the extensions listed in ${PREFIX}/etc/php/extensions.ini
in the wrong order.
Cheers,
Matthew
Matthew:
Thanks for that suggestion but couldn't find the numerous discussions about
the wrong order of extensions. Using google I did find one post and a list
that poster used. I tried following his list with the sames ones I had plus
some 6-7 he didn't have. Still get the core dump.
Can you suggest the key word to search in the list archives. I used php5
extensions and php5 core dump which brought up some discussions which
didn't include the order discussions though.
I cannot do without ioncube as another post mentioned.
Thanks to all and any other ideas.
Jack
(^_^)
Happy trails,
Jack L. Stone
System Admin
Sage-american
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
On Wed, 15 Jun 2011 13:40:15 -0500, Jack L. Stone ja...@sage-american.com wrote: I cannot do without ioncube as another post mentioned. I understand your need for ioncube, but replicate the problem to another non-production system and remove ioncube to see whether or not it is the cause. This is something we had to do and ultimately we told the only customer using ioncube they couldn't use it on our infrastructure anymore because it was a proprietary extension that causes issues. Again, before digging too deeply I strongly urge you repeat the test with ioncube extension disabled so you can rule that out immediately or else you'll be running around in circles for ages trying to figure out what the cause is. It's unfortunate that people think they need to obfuscate their code and use these silly workarounds. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 01:50 PM 6/15/2011 -0500, Mark Felder wrote: On Wed, 15 Jun 2011 13:40:15 -0500, Jack L. Stone ja...@sage-american.com wrote: I cannot do without ioncube as another post mentioned. I understand your need for ioncube, but replicate the problem to another non-production system and remove ioncube to see whether or not it is the cause. This is something we had to do and ultimately we told the only customer using ioncube they couldn't use it on our infrastructure anymore because it was a proprietary extension that causes issues. Again, before digging too deeply I strongly urge you repeat the test with ioncube extension disabled so you can rule that out immediately or else you'll be running around in circles for ages trying to figure out what the cause is. It's unfortunate that people think they need to obfuscate their code and use these silly workarounds. Regards, Mark I cannot do without ioncube as another post mentioned. I understand your need for ioncube, but replicate the problem to another non-production system and remove ioncube to see whether or not it is the cause. This is something we had to do and ultimately we told the only customer using ioncube they couldn't use it on our infrastructure anymore because it was a proprietary extension that causes issues. Again, before digging too deeply I strongly urge you repeat the test with ioncube extension disabled so you can rule that out immediately or else you'll be running around in circles for ages trying to figure out what the cause is. It's unfortunate that people think they need to obfuscate their code and use these silly workarounds. Regards, Mark Mark: Thanks for the suggestion. I tried a disable of the ioncube and still get the php seg fault/core dump. This one is maddening... Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
On 15/06/2011 19:40, Jack L. Stone wrote: Thanks for that suggestion but couldn't find the numerous discussions about the wrong order of extensions. Using google I did find one post and a list that poster used. I tried following his list with the sames ones I had plus some 6-7 he didn't have. Still get the core dump. Google for 'FreeBSD extensions.ini' Plenty of results there. However, to cut a long story short, some extensions needed to be loaded after certain other ones. The best way to work out a good load order is simply by trial and error -- most ordering permutations will actually work fine, with relatively few blowing up. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Another PHP5 problem
So I've seen that you haven't had a lot of success with this... can you post your extensions.ini file contents? -- Ryan On Jun 15, 2011, at 9:04 AM, Jack L. Stone wrote: I just finished some major upgrades/updates to a server, including php5-5.3.6 and apache2. Now I keep getting Segmentation faults and core dumps whenever apache2 rolls over its logs and does a restart. Here's the error. Does nyone have an idea of what's happening to cause this?: PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14) Copyright (c) 1997-2011 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by ionCube Ltd. Segmentation fault (core dumped) Thanks for any hints Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 02:50 PM 6/15/2011 -0500, Ryan Coleman wrote: So I've seen that you haven't had a lot of success with this... can you post your extensions.ini file contents? -- Ryan Here are my extensions after doing some shuffling according to ideas on google: extension=session.so extension=simplexml.so extension=ctype.so extension=apc.so extension=ftp.so extension=mbstring.so extension=tokenizer.so extension=filter.so extension=mcrypt.so extension=xmlwriter.so extension=gd.so extension=iconv.so extension=zlib.so extension=curl.so extension=bz2.so extension=pdf.so extension=openssl.so extension=dom.so extension=hash.so extension=xmlreader.so extension=sqlite.so extension=pdo.so extension=mysql.so extension=sockets.so extension=xml.so extension=sqlite3.so extension=json.so extension=zip.so extension=posix.so extension=snmp.so Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
And these were all built from the ports, yes? On Jun 15, 2011, at 3:06 PM, Jack L. Stone wrote: At 02:50 PM 6/15/2011 -0500, Ryan Coleman wrote: So I've seen that you haven't had a lot of success with this... can you post your extensions.ini file contents? -- Ryan Here are my extensions after doing some shuffling according to ideas on google: extension=session.so extension=simplexml.so extension=ctype.so extension=apc.so extension=ftp.so extension=mbstring.so extension=tokenizer.so extension=filter.so extension=mcrypt.so extension=xmlwriter.so extension=gd.so extension=iconv.so extension=zlib.so extension=curl.so extension=bz2.so extension=pdf.so extension=openssl.so extension=dom.so extension=hash.so extension=xmlreader.so extension=sqlite.so extension=pdo.so extension=mysql.so extension=sockets.so extension=xml.so extension=sqlite3.so extension=json.so extension=zip.so extension=posix.so extension=snmp.so Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 03:21 PM 6/15/2011 -0500, Ryan Coleman wrote: And these were all built from the ports, yes? Yes, all built from ports. (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. On Jun 15, 2011, at 3:59 PM, Jack L. Stone wrote: At 03:21 PM 6/15/2011 -0500, Ryan Coleman wrote: And these were all built from the ports, yes? Yes, all built from ports. (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. Sounds like a reasonable approach. Thanks, (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. Was wondering if it appeared an extension might be missing that would be expected? Have quite a few php scripts. What about the gettext one? I went with the defaults plus a couple I knew was needed like mysql and FTP. Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
That wouldn't likely cause a segfault, but you could use your apache logs to see if there's something in the last file before the segfault occurs... but that could be a wild goose chase. On Jun 15, 2011, at 5:57 PM, Jack L. Stone wrote: At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. Was wondering if it appeared an extension might be missing that would be expected? Have quite a few php scripts. What about the gettext one? I went with the defaults plus a couple I knew was needed like mysql and FTP. Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 06:35 PM 6/15/2011 -0500, Ryan Coleman wrote: That wouldn't likely cause a segfault, but you could use your apache logs to see if there's something in the last file before the segfault occurs... but that could be a wild goose chase. On Jun 15, 2011, at 5:57 PM, Jack L. Stone wrote: At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. Ryan: Found it! 2 extensions were the problem: # extension=sqlite3.so # extension=pdo_sqlite.so Don't even know why they got in there (except I checked the boxes in make config) Thanks for the great idea! Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
On Wed, Jun 15, 2011 at 03:33:08PM +0100, Matthew Seaman wrote:
Date: Wed, 15 Jun 2011 15:33:08 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: Another PHP5 problem
To: freebsd-questions@freebsd.org
On 15/06/2011 15:04, Jack L. Stone wrote:
PHP 5.3.6 with Suhosin-Patch (cli) (built: Jun 4 2011 18:04:14)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
with the ionCube PHP Loader v3.3.16, Copyright (c) 2002-2010, by
ionCube Ltd.
Segmentation fault (core dumped)
Check the mailing list archives for very many discussions on the effect
of having the extensions listed in ${PREFIX}/etc/php/extensions.ini
in the wrong order.
Cheers,
Matthew
This (fixing the extensions.ini list) was what worked for me...
...after endless hunting around.
gary
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
Journey Toward the Dawn, E-Book: http://www.thought.org
The 8.51a release of Jottings: http://jottings.thought.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
I have very few uses for sqlite3 but I still have them. And PDO? Never seen anything run it. Just because it is on by default 1) doesn't mean it's good for you and 2) the port connected to it is functioning properly. On Jun 15, 2011, at 7:18 PM, Jack L. Stone wrote: At 06:35 PM 6/15/2011 -0500, Ryan Coleman wrote: That wouldn't likely cause a segfault, but you could use your apache logs to see if there's something in the last file before the segfault occurs... but that could be a wild goose chase. On Jun 15, 2011, at 5:57 PM, Jack L. Stone wrote: At 04:04 PM 6/15/2011 -0500, Ryan Coleman wrote: My solution for these issues is usually pretty easy: Disable all extensions (with a ; before the line) and then re-enable batches until it dies on you and then go through line-by-line to see which one did it. Should take about 5 minutes, tops, to run through the entire list. Ryan: Found it! 2 extensions were the problem: # extension=sqlite3.so # extension=pdo_sqlite.so Don't even know why they got in there (except I checked the boxes in make config) Thanks for the great idea! Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Another PHP5 problem
At 08:14 PM 6/15/2011 -0500, Ryan Coleman wrote: I have very few uses for sqlite3 but I still have them. And PDO? Never seen anything run it. Just because it is on by default 1) doesn't mean it's good for you and 2) the port connected to it is functioning properly. Wierd! Told extensions to build without: extension=sqlite3.so extension=sqlite.so extension=pdo_sqlite.so But, built them anyway. Ran make config and then also checked the options file and it showed the WITHOUTS_ okay, but they were built anyway. Still have to comment out those sqlites. (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
