Re: Updated php, and apache segfaults on SIGHUP

2008-05-23 Thread Andrew Moran

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:

Try to compile it into php rather than a module.

http://no.php.net/manual/en/mhash.installation.php


Same as above -- is there an easy way to do that with the ports  
collection?  an option I pass into portinstall/portupgrade?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Odhiambo Washington
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 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:-)


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Oh My God! They killed init! You Bastards!
--from a /. post
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Randy Bush
 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 configuration:
Segmentation fault (core dumped)
Starting apache22.
Segmentation fault (core dumped)


randy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Randy Bush
 # /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
 /usr/local/etc/php/extensions.php solved the startup problem

commenting out all extensions did not solve it

randy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Claus Guttesen
 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 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
/usr/local/etc/php/extensions.php solved the startup problem (but then
the web-app could not connect to our postgresql-server). Compiling
pgsql statically into php worked around my problem.

-- 
regards
Claus

When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.

Shakespeare
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Norbert Papke
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] SIGHUP received.  Attempting to
 restart
 [Mon May 19 16:08:48 2008] [notice] seg fault or similar nasty error
 detected in the parent process

 and this in the messages log:

 May 19 16:14:45 celebrian kernel: pid 36900 (httpd), uid 0: exited on
 signal 11 (core dumped)

I ran into a similar problem.  In my case, the problem was caused by PHP5 
using the putenv(3) function incorrectly.  Removing 
files/patch-ext_standard_basic_functions.c from the port and rebuilding fixed 
the issue for me.  I have reported this to the maintainer but have not raised 
a PR.

For more information, see

http://docs.freebsd.org/cgi/getmsg.cgi?fetch=875448+0+archive/2008/freebsd-stable/20080518.freebsd-stable

Cheers.

-- Norbert.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Sean C. Farley

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 before you did your
updates, it would be worth trying reverting to that, to get the order
you had before that seemed OK.


still coring

but it is nice to know i have company :)


I recall mention on an E-mail list or on IRC of a core dump with PHP due
to improper use of putenv(), but I do not remember where.  Bug #44836[1]
discusses it.  It seems the patch was reverted, but I see that it is
included as a patch within the ports tree.  You could try to see if
things improve by using the older patch[2] for FreeBSD 7 (and above)
systems.

Cc'ing delphij to mention that the patch was reverted in the PHP tree.
Was the patch written for FreeBSD 6?  I noticed that it frees memory
just after the call to putenv().  The is valid for FreeBSD 6 where the
string was duped, but in 7, it follows the POSIX standard of using the
string directly.

Sean
  1. http://bugs.php.net/bug.php?id=44836
  2. 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php5/files/patch-ext_standard_basic_functions.c?rev=1.1;content-type=text%2Fplain
--
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Andrew Moran


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 of putting that mhash in the beginning or the end of the  
file.


On freebsd 7, I've cvsup'd and rebuilt all ports, so I know it's not  
an 'out of date' kind of thing.  Hmm..


--Andy

On May 20, 2008, at 8:02 AM, Sean C. Farley wrote:


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 before you did your
updates, it would be worth trying reverting to that, to get the  
order

you had before that seemed OK.


still coring

but it is nice to know i have company :)


I recall mention on an E-mail list or on IRC of a core dump with PHP  
due
to improper use of putenv(), but I do not remember where.  Bug  
#44836[1]

discusses it.  It seems the patch was reverted, but I see that it is
included as a patch within the ports tree.  You could try to see if
things improve by using the older patch[2] for FreeBSD 7 (and above)
systems.

Cc'ing delphij to mention that the patch was reverted in the PHP tree.
Was the patch written for FreeBSD 6?  I noticed that it frees memory
just after the call to putenv().  The is valid for FreeBSD 6 where the
string was duped, but in 7, it follows the POSIX standard of using the
string directly.

Sean
 1. http://bugs.php.net/bug.php?id=44836
 2. 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php5/files/patch-ext_standard_basic_functions.c?rev=1.1;content-type=text%2Fplain
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED] 





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Sean C. Farley

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 but could not get to work
regardless of putting that mhash in the beginning or the end of the
file.

On freebsd 7, I've cvsup'd and rebuilt all ports, so I know it's not
an 'out of date' kind of thing.  Hmm..


I meant the opposite.  The latest port version of PHP has a bug on
FreeBSD 7.  Try it again with the previous patch.


On May 20, 2008, at 8:02 AM, Sean C. Farley wrote:


*snip*


I recall mention on an E-mail list or on IRC of a core dump with PHP
due to improper use of putenv(), but I do not remember where.  Bug
#44836[1] discusses it.  It seems the patch was reverted, but I see
that it is included as a patch within the ports tree.  You could try
to see if things improve by using the older patch[2] for FreeBSD 7
(and above) systems.

Cc'ing delphij to mention that the patch was reverted in the PHP
tree.  Was the patch written for FreeBSD 6?  I noticed that it frees
memory just after the call to putenv().  The is valid for FreeBSD 6
where the string was duped, but in 7, it follows the POSIX standard
of using the string directly.

Sean
1. http://bugs.php.net/bug.php?id=44836
2. 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php5/files/patch-ext_standard_basic_functions.c?rev=1.1;content-type=text%2Fplain


Sean
--
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-20 Thread Claus Guttesen
 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 of
 putting that mhash in the beginning or the end of the file.

 On freebsd 7, I've cvsup'd and rebuilt all ports, so I know it's not an 'out
 of date' kind of thing.  Hmm..

Try to compile it into php rather than a module.

http://no.php.net/manual/en/mhash.installation.php

-- 
regards
Claus

When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.

Shakespeare
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-19 Thread Kevin Downey
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 log:

 [Mon May 19 16:08:48 2008] [notice] SIGHUP received.  Attempting to restart
 [Mon May 19 16:08:48 2008] [notice] seg fault or similar nasty error
 detected in the parent process

 and this in the messages log:

 May 19 16:14:45 celebrian kernel: pid 36900 (httpd), uid 0: exited on signal
 11 (core dumped)


 I narrowed it down to php - when I disable the php5 module, it doesn't
 behave like this.

 celebrian# pkg_info  | grep php
 php5-5.2.6  PHP Scripting Language
 php5-gd-5.2.6   The gd shared extension for php
 php5-gettext-5.2.6  The gettext shared extension for php
 php5-iconv-5.2.6The iconv shared extension for php
 php5-mbstring-5.2.6 The mbstring shared extension for php
 php5-mhash-5.2.6The mhash shared extension for php
 php5-mysql-5.2.6The mysql shared extension for php
 php5-openssl-5.2.6  The openssl shared extension for php
 php5-pcre-5.2.6 The pcre shared extension for php
 php5-session-5.2.6  The session shared extension for php
 php5-xml-5.2.6  The xml shared extension for php
 celebrian#

 This is on apache-2.0.63 and php 5.2.6 on FreeBSD 7.0.

 In case it was an out of date dependency, I did a cvsup on the ports tree,
 then a portupgrade -fa .it rebuilt all ports without any errors.


 Has anyone else seen this?

 --Andy
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]


there was a thread on a while back on one of the other lists, maybe -questions.
the offending extension is one of these three:
#extension=mcrypt.so
#extension=mbstring.so
#extension=mhash.so
I have the three of them commented out, so I am not sure which one was
the poblem.

-- 
The Mafia way is that we pursue larger goals under the guise of
personal relationships.
 Fisheye
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-19 Thread Barry Pederson

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 in the apache error log:

[Mon May 19 16:08:48 2008] [notice] SIGHUP received.  Attempting to restart
[Mon May 19 16:08:48 2008] [notice] seg fault or similar nasty error
detected in the parent process

and this in the messages log:

May 19 16:14:45 celebrian kernel: pid 36900 (httpd), uid 0: exited on signal
11 (core dumped)


I narrowed it down to php - when I disable the php5 module, it doesn't
behave like this.



there was a thread on a while back on one of the other lists, maybe -questions.
the offending extension is one of these three:
#extension=mcrypt.so
#extension=mbstring.so
#extension=mhash.so
I have the three of them commented out, so I am not sure which one was
the poblem.


Andy:

It seems the order of the extensions in 
/usr/local/etc/php/extensions.ini matters.  For example, in the php5 
ports Makefile.ext, there's an Ugly hack to load session before pspell 
to avoid crashes It could be there are other ordering dependencies.


If you have a backup of php/extensions.ini from before you did your 
updates, it would be worth trying reverting to that, to get the order 
you had before that seemed OK.


Barry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-19 Thread Randy Bush
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 worth trying reverting to that, to get the order
 you had before that seemed OK.

still coring

but it is nice to know i have company :)

randy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-19 Thread Kevin Downey
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 backup of php/extensions.ini from before you did your
 updates, it would be worth trying reverting to that, to get the order
 you had before that seemed OK.

 still coring

 but it is nice to know i have company :)

 randy
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]

did you ever try comment out the three extensions I mentioned in my
previous email? That fixed it right up for me.


-- 
The Mafia way is that we pursue larger goals under the guise of
personal relationships.
 Fisheye
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Updated php, and apache segfaults on SIGHUP

2008-05-19 Thread Randy Bush
 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 list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]