Dependency problems and seg faults on AWS AMI

[edhgoose]

Hi,

I'm not sure if this is the right place for this, but hopefully this can get to the right people?

I had a lot of trouble upgrading to php70 this afternoon from php56, and part of the problem is incompatibility between the igbinary version available on AWS AMIs in the yum repo and one that this library can use.

I installed the below, after a quick yum search igbinary:

Name        : php70-pecl-igbinary
Arch        : x86_64
Version     : 1.2.2
Release     : 0.1.20151217git2b7c703.5.amzn1
Size        : 54 k
Repo        : amzn-main/latest
Summary     : Replacement for the standard PHP serializer
URL         : http://pecl.php.net/package/igbinary

Unfortunately - this version (1.2.2) is incompatible with something in this AWS memcached client library and/or php7 as it threw multiple seg faults (I'm happy to provide a core dump if required).

It would appear running pecl install igbinary instead gets you a PHP7 version of igbinary (2.0.1).

This is alluded to in the README of this repo, but I only found this by manually unzipping the 5.6 version of the client library from https://eu-west-1.console.aws.amazon.com/elasticache/home?region=eu-west-1#client-download: and trying the README. It'd be great if there was documentation within the AWS console / the packages were maintained to ensure compatability.

Hope that makes sense. If I can be of use by providing code dumps from the seg faults I was seeing from the 1.2.2 version of igbinary I'd be happy to!

Cheers
Ed

[sodabrew]

For PHP 7 you need igbinary 2.x with memcached 3.x (The AWS ElastiCache memcached client is a lightly modified php-memcached 3.x.)

https://github.com/php-memcached-dev/php-memcached/blob/master/README.markdown#dependencies

[edhgoose]

Thanks @sodabrew - now I've got it setup and working I can totally understand that. I guess my question/issue is if you were downloading the Memcache client for the first time, there is nothing to provide you with that information. The package from the AWS console comes with no readme and has no additional information or install, and there's no links to documentation.

Is there anything that can be done to make it easier for users?

[sodabrew]

@malyeyev-AMZN might be able to help with the posted documentation / requirements?

[malyeyev-AMZN]

@edhgoose:

This is alluded to in the README of this repo, but I only found this by manually unzipping the 5.6 version of the client library from https://eu-west-1.console.aws.amazon.com/elasticache/home?region=eu-west-1#client-download: and trying the README. It'd be great if there was documentation within the AWS console / the packages were maintained to ensure compatability.

That's odd, the source of this package does come with a README describing igbinary instructions:
php7 branch README.markdown
master (php5.x) branch README.markdown

[edhgoose]

I think these screenshots below best illustrates my scenario.

I've never known that the Elasticache library was an open source library until a couple of days ago and I've always downloaded the Elasticache library from the URL above (https://eu-west-1.console.aws.amazon.com/elasticache/home?region=eu-west-1#client-download:). If I hadn't installed the 5.6 version before and had some understanding of how it worked, I'd be stumped.

If I contrast with this screenshot below, the PHP 5.6 library is a very different beast. There is a package.xml, a README, an INSTALL file, an example ini file and a class file with the various methods in.

Does that make sense?

If it helps, the sha256 of the 5.6 library is 0f1b1ec4ac5a926bd792026c1f7d6e5a9b710c4437443a3051e1fb4f8c9b08a2 and the 7.0 library is e9a6bb5982f1a7cb7ccc28c70f5c4b8eb5ceec7ad4ead2492a71845df245fb66

[malyeyev-AMZN]

Thank you for a detailed report. I have opened a ticket internally to track this and hopefully we'll have a chance to fix it at some point.

Are you still experiencing segfaults or any other issues now that you're using igbinary 2.0.1?

[edhgoose]

Brilliant. Thanks. No more segfaults after upgrading, although I haven't extensively tested it after the upgrade to igbinary 2.

…

On Fri, 17 Feb 2017 at 18:38 malyeyev-AMZN ***@***.***> wrote: Thank you for a detailed report. I have opened a ticket internally to track this and hopefully we'll have a chance to fix it at some point. Are you still experiencing segfaults or any other issues now that you're using igbinary 2.0.1? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABDozdrtGiifeVzbEVve5rGCAvpo7-hSks5rdekzgaJpZM4MBJpB> .