Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-08-20 Thread Ben Harper

Hey Andy,

As always, thanks for your time.  I agree on skipping the pull request.

-Ben

On 08/20/2015 12:45 AM, Andy Thompson wrote:

Actually, ignore my PRs, as there seems to be code in that area I changed that 
requires it.

It might be best running `yum provides /etc/php.d/opcache.ini` to see if it was 
the RPM that added the opcache.ini, or if it was for example an upgrade from a 
previous php56u version that renamed the file, given edits to the original 
opcache.ini wouldn’t move over in the process

Andy


On 20 Aug 2015, at 06:31, Andy Thompson m...@andytson.com wrote:

Hi Jakov/Ben,

PHP Zend extensions can conflict with others quite often. The solution is to 
change the ordering of how they load, in this case it was to move opcache to be 
the first extension to be loaded.

The RPMs appear to additionally be introducing opcache as a standard extension 
as well.

I’ve submitted 2 PRs to solve this. I’m unsure if this is the reason for 
Jakov’s PHP’s behaviour, but is a good start.

https://github.com/iuscommunity-pkg/php56u/pull/13
https://github.com/iuscommunity-pkg/php55u/pull/15

@Jakov, you should be able to delete the /etc/php.d/opcache.ini manually, which 
then you might be able to see if this is the cause.

Note there may be another extension opcache might conflict with, so the 
ordering, and/or use of the conflicting extensions might need to change.

Kind Regards

Andy



On 20 Aug 2015, at 00:22, Jakov Sosic jso...@gmail.com wrote:

On 08/17/2015 03:57 PM, Ben Harper wrote:

You mentioned that you are rebuilding your php packages against httpd24.
Can you reproduce this issue with stock IUS php packages?


Hi Ben,

sorry for the late answer, but I finally got some spare time and I found a 
reason for this segfault.

Problem was within opcache module, and actually, problem was that I had two 
files:

/etc/php.d/10-opcache.ini

and

/etc/php.d/opcache.ini


Both files had same content, which is ok. Reason I had these two files was that 
I use puppet as CM, and in 5.6 you guys changed names of the ini files by 
adding enumeration in front of them, and puppet deployed this file as usual.


Actually, to reproduce it, it is enough to have:

zend_extension=opcache.so
zend_extension=opcache.so

in /etc/php.ini.


While this is my mistake, I still am puzzled as to why does php segfault in 
this case. IMHO, php should handle multiple .so loading same as Apache does, by 
printing warning and ignoring the second 'zend_extension=' line...

I already filed a bug upstream, so I'll just update the bug description, or 
open a new bug...

What puzzles me though is that I remember having this problem with early 5.6.x 
versions (5.6.3) even with opcache disabled, so I'm kinda really lost.

I'll give it a little bit more testing to see if it's stable enough to move 
prod to 5.6.x now.

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-08-19 Thread Jakov Sosic

On 08/17/2015 03:57 PM, Ben Harper wrote:

You mentioned that you are rebuilding your php packages against httpd24.
  Can you reproduce this issue with stock IUS php packages?


Hi Ben,

sorry for the late answer, but I finally got some spare time and I found 
a reason for this segfault.


Problem was within opcache module, and actually, problem was that I had 
two files:


/etc/php.d/10-opcache.ini

and

/etc/php.d/opcache.ini


Both files had same content, which is ok. Reason I had these two files 
was that I use puppet as CM, and in 5.6 you guys changed names of the 
ini files by adding enumeration in front of them, and puppet deployed 
this file as usual.



Actually, to reproduce it, it is enough to have:

zend_extension=opcache.so
zend_extension=opcache.so

in /etc/php.ini.


While this is my mistake, I still am puzzled as to why does php segfault 
in this case. IMHO, php should handle multiple .so loading same as 
Apache does, by printing warning and ignoring the second 
'zend_extension=' line...


I already filed a bug upstream, so I'll just update the bug description, 
or open a new bug...


What puzzles me though is that I remember having this problem with early 
5.6.x versions (5.6.3) even with opcache disabled, so I'm kinda really lost.


I'll give it a little bit more testing to see if it's stable enough to 
move prod to 5.6.x now.


___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-08-19 Thread Andy Thompson
Hi Jakov/Ben,

PHP Zend extensions can conflict with others quite often. The solution is to 
change the ordering of how they load, in this case it was to move opcache to be 
the first extension to be loaded.

The RPMs appear to additionally be introducing opcache as a standard extension 
as well.

I’ve submitted 2 PRs to solve this. I’m unsure if this is the reason for 
Jakov’s PHP’s behaviour, but is a good start.

https://github.com/iuscommunity-pkg/php56u/pull/13
https://github.com/iuscommunity-pkg/php55u/pull/15

@Jakov, you should be able to delete the /etc/php.d/opcache.ini manually, which 
then you might be able to see if this is the cause.

Note there may be another extension opcache might conflict with, so the 
ordering, and/or use of the conflicting extensions might need to change.

Kind Regards

Andy


 On 20 Aug 2015, at 00:22, Jakov Sosic jso...@gmail.com wrote:
 
 On 08/17/2015 03:57 PM, Ben Harper wrote:
 You mentioned that you are rebuilding your php packages against httpd24.
  Can you reproduce this issue with stock IUS php packages?
 
 Hi Ben,
 
 sorry for the late answer, but I finally got some spare time and I found a 
 reason for this segfault.
 
 Problem was within opcache module, and actually, problem was that I had two 
 files:
 
 /etc/php.d/10-opcache.ini
 
 and
 
 /etc/php.d/opcache.ini
 
 
 Both files had same content, which is ok. Reason I had these two files was 
 that I use puppet as CM, and in 5.6 you guys changed names of the ini files 
 by adding enumeration in front of them, and puppet deployed this file as 
 usual.
 
 
 Actually, to reproduce it, it is enough to have:
 
 zend_extension=opcache.so
 zend_extension=opcache.so
 
 in /etc/php.ini.
 
 
 While this is my mistake, I still am puzzled as to why does php segfault in 
 this case. IMHO, php should handle multiple .so loading same as Apache does, 
 by printing warning and ignoring the second 'zend_extension=' line...
 
 I already filed a bug upstream, so I'll just update the bug description, or 
 open a new bug...
 
 What puzzles me though is that I remember having this problem with early 
 5.6.x versions (5.6.3) even with opcache disabled, so I'm kinda really lost.
 
 I'll give it a little bit more testing to see if it's stable enough to move 
 prod to 5.6.x now.
 
 ___
 Mailing list: https://launchpad.net/~ius-community
 Post to : ius-community@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~ius-community
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-28 Thread Carl George
Hello Jakov,

We actually just recently got a bug report about httpd24u's apxs command not 
working properly.  I'm betting you saw the same issue.

https://bugs.launchpad.net/ius/+bug/1478588

Check out httpd24u-2.4.16-2.ius in our testing repos and reply in that bug if 
it works for you.

Carl George
IUS CoreDev Team


From: Ius-community 
ius-community-bounces+carl.george=rackspace@lists.launchpad.net on behalf 
of Jakov Sosic jso...@gmail.com
Sent: Monday, July 27, 2015 07:12 PM
To: ius-community@lists.launchpad.net
Subject: Re: [Ius-community] php56u-pecl-memcache coredumps httpd

On 07/27/2015 07:51 PM, Ben Harper wrote:
 Hey Jakov,

 Thanks for taking the time to reach out to us about this issue.  Can we
 assume this code and configuration worked with php55u with
 php55u-pecl-memcache?  Also can we assume the code works without the
 memcache module?  Have you tried the memcached module?

Actually, everything worked/works perfectly with php54. I didn't try
php55u, but I can spin up env and try it if you want?

That would buy me some time, but I wanted to avoid double upgrade (php54
- php55u - php56u) cause each upgrade brings it's own rollout plan and
testing phases.

I'll try php55u tomorrow and report back.


 With these types of issues, we need to figure out is this an upstream
 issue with the pecl module itself or an issue with the way the module is
 packaged.  While I am not an expert with the memcache module, I don't
 think this is issue with the way we package memcache.

I don't want to imply that packaging is the culprit for this issue, at
contrary - I'm posting at this mailing list because you guys seem to
know what you're doing and was hoping to get some insight into what may
I try as a remedy.


 Looking over the output, I do see you are running an older version of
 PHP.  Have you tried with php56u-5.6.11?

I'm actually rebuilding IUS php to link it agains httpd24u, and I
haven't rebuild 5.6.11 yet. But, since I have this issue from the first
time I noticed php56u in your repos (around 5.6.3 I think), and upgrades
to 5.6.9 didn't help, I got impression this is purely pecl-memcache vs
5.6 branch related issue, and not something that will get fixed in minor
versions.

Now, as a side remark - I did notice some issues with httpd24u when
building php against it: /usr/bin/apxs didn't parse libdir correctly. I
can open a thread with info about that if you want (I think this may be
a bug on a packaging side though).


 Looking over bugs for the memache module[0], I don't see anything that
 jumps out at me.  There are a few bugs that mention memcache_pool.c[1],
 but I am not sure if any of those are related.  It might be worth
 looking through those bugs.

 -Ben


 [0]
 https://bugs.php.net/search.php?cmd=displaystatus=Openpackage_name[]=memcache

 [1]
 https://bugs.php.net/search.php?cmd=displaysearch_for=memcache_pool.cx=0y=0

Thank you Ben for answering, I'll skim through the bugs.

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-28 Thread Jakov Sosic

On 07/28/2015 03:24 PM, Carl George wrote:

Hello Jakov,

We actually just recently got a bug report about httpd24u's apxs command not 
working properly.  I'm betting you saw the same issue.

https://bugs.launchpad.net/ius/+bug/1478588

Check out httpd24u-2.4.16-2.ius in our testing repos and reply in that bug if 
it works for you.



Yup, this is the bug I intended to report :)


Thank you,

Jakov

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-28 Thread Jakov Sosic

On 07/28/2015 06:30 PM, Ben Harper wrote:

Hey Jakov,

Seeing that you are trying to jump from PHP 5.4 to PHP 5.6, the
following mitigation guide might be useful:

http://php.net/manual/en/migration55.php

http://php.net/manual/en/migration56.php


Thank you, code is already prepared. Problems come from session handler, 
which is php.ini stuff...


Do you want me to try php55u with my apps/stack ?


___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-28 Thread Ben Harper

Hey Jakov,

I was not sure how far into the migration process you have gotten. 
Looks like you are much further along than I thought.  I got asking 
about php55u just to try to get a better understand of your situation. 
If you feel confident that your code is ready for PHP 5.6, I don't think 
testing on php55u is needed at this time.


So I think the next step is to figure out if the issue you are running 
into is with the memcache module itself or with the way we package it. 
Are you getting the same error when installing the memcache module via 
pecl?


-Ben

On 07/28/2015 12:09 PM, Jakov Sosic wrote:

On 07/28/2015 06:30 PM, Ben Harper wrote:

Hey Jakov,

Seeing that you are trying to jump from PHP 5.4 to PHP 5.6, the
following mitigation guide might be useful:

http://php.net/manual/en/migration55.php

http://php.net/manual/en/migration56.php


Thank you, code is already prepared. Problems come from session handler,
which is php.ini stuff...

Do you want me to try php55u with my apps/stack ?


___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-27 Thread Ben Harper

Hey Jakov,

Thanks for taking the time to reach out to us about this issue.  Can we 
assume this code and configuration worked with php55u with 
php55u-pecl-memcache?  Also can we assume the code works without the 
memcache module?  Have you tried the memcached module?


With these types of issues, we need to figure out is this an upstream 
issue with the pecl module itself or an issue with the way the module is 
packaged.  While I am not an expert with the memcache module, I don't 
think this is issue with the way we package memcache.


Looking over the output, I do see you are running an older version of 
PHP.  Have you tried with php56u-5.6.11?


Looking over bugs for the memache module[0], I don't see anything that 
jumps out at me.  There are a few bugs that mention memcache_pool.c[1], 
but I am not sure if any of those are related.  It might be worth 
looking through those bugs.


-Ben


[0] 
https://bugs.php.net/search.php?cmd=displaystatus=Openpackage_name[]=memcache
[1] 
https://bugs.php.net/search.php?cmd=displaysearch_for=memcache_pool.cx=0y=0




On 07/27/2015 11:11 AM, Jakov Sosic wrote:

Hi guys,

I was wondering if any of you could point me what do next with the
following issue I'm observing.

I have php56u + php56u-pecl-memcache. Memcache is used to store user
sessions via:

session.save_path = tcp://localhost:11914
session.gc_maxlifetime = 10800

php.ini directives.

But, opening certain pages I get apache coredumps.


I've tried analyzing one of the dumps, and this is what I got so far:

#0  mmc_pool_select (pool=0x7fad4456eae0) at
/usr/src/debug/php-pecl-memcache-3.0.8/NTS/memcache_pool.c:1422
1422for (i=0; i  sending-len; i++) {


Backtrace is available at:

http://pastebin.com/e6Hmne50


Any ideas what could be the reason for this, or where could I look
further? It's blocking me from upgrading to php 5.6 ...

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp


Re: [Ius-community] php56u-pecl-memcache coredumps httpd

2015-07-27 Thread Jakov Sosic

On 07/27/2015 07:51 PM, Ben Harper wrote:

Hey Jakov,

Thanks for taking the time to reach out to us about this issue.  Can we
assume this code and configuration worked with php55u with
php55u-pecl-memcache?  Also can we assume the code works without the
memcache module?  Have you tried the memcached module?


Actually, everything worked/works perfectly with php54. I didn't try 
php55u, but I can spin up env and try it if you want?


That would buy me some time, but I wanted to avoid double upgrade (php54 
- php55u - php56u) cause each upgrade brings it's own rollout plan and 
testing phases.


I'll try php55u tomorrow and report back.



With these types of issues, we need to figure out is this an upstream
issue with the pecl module itself or an issue with the way the module is
packaged.  While I am not an expert with the memcache module, I don't
think this is issue with the way we package memcache.


I don't want to imply that packaging is the culprit for this issue, at 
contrary - I'm posting at this mailing list because you guys seem to 
know what you're doing and was hoping to get some insight into what may 
I try as a remedy.




Looking over the output, I do see you are running an older version of
PHP.  Have you tried with php56u-5.6.11?


I'm actually rebuilding IUS php to link it agains httpd24u, and I 
haven't rebuild 5.6.11 yet. But, since I have this issue from the first 
time I noticed php56u in your repos (around 5.6.3 I think), and upgrades 
to 5.6.9 didn't help, I got impression this is purely pecl-memcache vs 
5.6 branch related issue, and not something that will get fixed in minor 
versions.


Now, as a side remark - I did notice some issues with httpd24u when 
building php against it: /usr/bin/apxs didn't parse libdir correctly. I 
can open a thread with info about that if you want (I think this may be 
a bug on a packaging side though).




Looking over bugs for the memache module[0], I don't see anything that
jumps out at me.  There are a few bugs that mention memcache_pool.c[1],
but I am not sure if any of those are related.  It might be worth
looking through those bugs.

-Ben


[0]
https://bugs.php.net/search.php?cmd=displaystatus=Openpackage_name[]=memcache

[1]
https://bugs.php.net/search.php?cmd=displaysearch_for=memcache_pool.cx=0y=0


Thank you Ben for answering, I'll skim through the bugs.

___
Mailing list: https://launchpad.net/~ius-community
Post to : ius-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ius-community
More help   : https://help.launchpad.net/ListHelp