no apache22, php5 cores
freebsd-questions at herveybayaustralia.com.au
Sat Jan 22 01:25:18 UTC 2011
On 01/22/11 11:03, Gary Kline wrote:
> On Sat, Jan 22, 2011 at 09:28:50AM +1000, Da Rock wrote:
>> On 01/22/11 08:42, Gary Kline wrote:
>>> On Fri, Jan 21, 2011 at 05:01:25PM -0500, Brad Mettee wrote:
>>>> Gary Kline wrote:
>>>> Hope this helps,
>> Run ps ax | grep httpd. If it doesn't show up then its not working. If
>> it says NO_HTTP_ACCEPT or similar its not working either.
> yes! i was wondering. I tried this around noon and got a slew of the
> DNOHTTPACCEPT ... I Was going to mention this but didn't.
>> Also, regardless of the output there, try commenting out loading the php
>> module in httpd.conf. If apache works then it is just a php problem.
>> 9/10 the php problem is just the extensions dependencies problem.
>> /usr/local/etc/php/extensions.ini - recode at the top (required by most
>> other extensions), and shuffle the others as required. ie.:
> By jove [[aka ohshit]], apache still works. With all the php stuff
> commented out. just to be sure, i'll try Wash's apachectl ....
> For some reason i just dont trust scripts... .
> Says ^Syntax OK
> Still, even with apache22 going I can't reach any of my sites. At
> lwast two have index.html, so these subdomains ought to work, right?
>> (Thats probably an old one - been floating around my ~)
> Good grief, there are more than i'd thought. I asked before how the
> above strings got stuck into the extensions.ini. I'll ck my mail
> queue, but in case you know, will you clue me in?
> Well, at least we know that apache works ;-)
Apache will work with php, but some sites may be coded with it, so they
will simply show the code- careful with security! Better stop apache to
be sure until it works with php, OR comment out the sites using it.
When you build the php-extensions port, everything selected via make
config options is built, and as it is built (it doesn't give 2 hoots
about extension dependencies) it appends the extensions.ini. You need to
reorder the extensions so that the extensions are loaded AFTER the
extensions they depend on. And they will change from time to time
killing your apache once IT reloads- reloading the php module will fail
and it won't respond.
Once you have discovered which extensions rely on which, you'll get the
idea. The extensions.ini I posted should get you started. But subtract
and add what you need. Running php should give you some clue as to what
is wrong, and a quick search on google will generally provide you what
From memory recode should be at the top (needed by most), hash relies
on mhash (I think- or the reverse); sorry I can't exactly remember more :)
More information about the freebsd-questions