Excellent suggestions.
On May 20, 2008, at 12:42 PM, Sean C. Farley wrote:
I meant the opposite. The latest port version of PHP has a bug on
FreeBSD 7. Try it again with the previous patch.
How do I do that with the ports collection?
On May 20, 2008, at 12:45 PM, Claus Guttesen wrote:
On Tue, May 20, 2008 at 8:11 AM, Randy Bush [EMAIL PROTECTED] wrote:
did you ever try comment out the three extensions I mentioned in my
previous email? That fixed it right up for me.
i did not have those extensions at all. or maybe i did not understand
where they are.
Could you guys
Could you guys google for fixphpextorder.sh and see if that would help.
It did help me last year when I had this problem and I always rely on it
during upgrade, but I'm not saying I guarantee it will:-)
still cores
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22 configuration:
Segmentation fault (core dumped)
Starting apache22.
Segmentation fault (core dumped)
Apache (1.3) would core dump when pgsql (from php 5.2.5) was loaded as
a module. Commenting this module out from
Could you guys google for fixphpextorder.sh and see if that would help.
It did help me last year when I had this problem and I always rely on it
during upgrade, but I'm not saying I guarantee it will:-)
still cores
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22
On May 19, 2008, Andrew Moran wrote:
I recently upgraded my php5 ports to latest ports tree versions
(5.2.6), and now I'm in a situation where any HUP signal sent to
apache is causing the entire process to dump core. I get this in the
apache error log:
[Mon May 19 16:08:48 2008] [notice]
On Mon, 19 May 2008, Randy Bush wrote:
386 very current
i have been unable to get apache not to segv on one server for a while
now.
i tried the php rebuild
i tried clearing obj, full system build, full ports force rebuild, ...
i just tried
If you have a backup of php/extensions.ini from
OK I've narrowed down my problem to:
extension=mhash.so
in extensions.ini
If I comment out that php extension, I'm good. If I don't, I crash
when sending HUP signal to parent apache process. I experimented
with the order of the extensions.ini file but could not get to work
On Tue, 20 May 2008, Andrew Moran wrote:
OK I've narrowed down my problem to:
extension=mhash.so
in extensions.ini
If I comment out that php extension, I'm good. If I don't, I crash
when sending HUP signal to parent apache process. I experimented with
the order of the extensions.ini file
OK I've narrowed down my problem to:
extension=mhash.so
in extensions.ini
If I comment out that php extension, I'm good. If I don't, I crash when
sending HUP signal to parent apache process. I experimented with the
order of the extensions.ini file but could not get to work regardless
Hey guys,
I recently upgraded my php5 ports to latest ports tree versions
(5.2.6), and now I'm in a situation where any HUP signal sent to
apache is causing the entire process to dump core. I get this in the
apache error log:
[Mon May 19 16:08:48 2008] [notice] SIGHUP received.
On Mon, May 19, 2008 at 4:18 PM, Andrew Moran [EMAIL PROTECTED] wrote:
Hey guys,
I recently upgraded my php5 ports to latest ports tree versions (5.2.6), and
now I'm in a situation where any HUP signal sent to apache is causing the
entire process to dump core. I get this in the apache error
Kevin Downey wrote:
On Mon, May 19, 2008 at 4:18 PM, Andrew Moran [EMAIL PROTECTED] wrote:
Hey guys,
I recently upgraded my php5 ports to latest ports tree versions (5.2.6), and
now I'm in a situation where any HUP signal sent to apache is causing the
entire process to dump core. I get this
386 very current
i have been unable to get apache not to segv on one server for a while now.
i tried the php rebuild
i tried clearing obj, full system build, full ports force rebuild, ...
i just tried
If you have a backup of php/extensions.ini from before you did your
updates, it would be
On Mon, May 19, 2008 at 9:51 PM, Randy Bush [EMAIL PROTECTED] wrote:
386 very current
i have been unable to get apache not to segv on one server for a while now.
i tried the php rebuild
i tried clearing obj, full system build, full ports force rebuild, ...
i just tried
If you have a
did you ever try comment out the three extensions I mentioned in my
previous email? That fixed it right up for me.
i did not have those extensions at all. or maybe i did not understand
where they are.
randy
___
freebsd-questions@freebsd.org mailing
16 matches
Mail list logo
