Troubleshooting issues with sse4_crc32

[flovilmart]

We're going on trying to troubleshoot the issues with sse4_crc32 (a dependency injected by parse-server-gcd-adapter and gcloud)

from: googleapis/google-cloud-node#1197 (comment)

If you face issues deploying your code, and that this module seems to be the culplrit, please upload your npm-debug.log or any relevant stack trace.

Please also include the version of parse-server you're deploying as well as your server configuration, distribution etc...

Thanks!

[flovilmart]

@anandsuresh AWS Elastic Beanstalk, AMI 2016

$ uname -r
4.1.17-22.30.amzn1.x86_64

$ yum --version
3.4.3
  Installés : rpm-4.11.2-2.73.amzn1.x86_64 à 2016-02-10 18:09
  Compilé   : Amazon.com, Inc. <http://aws.amazon.com> à 2015-11-16 21:31
  Commité   : Ben Cressey <[email protected]> à 2015-03-25

  Installés : yum-3.4.3-137.65.amzn1.noarch à 2016-02-10 18:09
  Compilé   : Amazon.com, Inc. <http://aws.amazon.com> à 2015-10-15 00:11
  Commité   : Heath Petty <[email protected]> à 2015-10-13

Original command:

1 verbose cli [ '/opt/elasticbeanstalk/node-install/node-v4.3.0-linux-x64/bin/node',
1 verbose cli   '/opt/elasticbeanstalk/node-install/node-v4.3.0-linux-x64/bin/npm',
1 verbose cli   '--production',
1 verbose cli   'rebuild' ]

Gist from npm-debug.log
https://gist.github.com/flovilmart/3bcb096ef70e28a71d62c49904e393e6

Also:
https://gist.github.com/flovilmart/39c9720cc747b63ed2cfd20f3ff25056

[flovilmart]

http://stackoverflow.com/questions/34084814/npm-error-when-deploying-nodejs-to-elastic-beanstalk

[anandsuresh]

@flovilmart I'm not well-versed with AWS or Amazon's offerings. Tried googling but couldn't find much on any free/OSS offerings for Elastic Beanstalk. I'm looking for a way to spin up an instance and dig deeper into the build process logs. Any suggestions/links that would point me in the right direction would be super helpful.

[flovilmart]

@anandsuresh somewhat this was related to that: #1276

Seems that the issue at hands is not the package or anything but a memory pressure problem.

[anandsuresh]

@flovilmart Looking at the logs in that thread, it seems that the SSE4_CRC32 module is building successfully:

    CXX(target) Release/obj.target/crc32c_sse42/src/crc32c_sse42.o
    AR(target) Release/obj.target/crc32c_sse42.a
    COPY Release/crc32c_sse42.a
    CXX(target) Release/obj.target/sse4_crc32/src/crc32c.o
    SOLINK_MODULE(target) Release/obj.target/sse4_crc32.node
    COPY Release/sse4_crc32.node
  make: Leaving directory `/tmp/deployment/application/node_modules/parse-server/node_modules/parse-server-gcs-adapter/node_modules/gcloud/node_modules/hash-stream-validation/node_modules/fast-crc32c/node_modules/sse4_crc32/build'

However, the gist you posted seems to fail on SSE4_CRC32.

Also, very surprising that it is running into memory pressure on a machine with a gig of RAM, but if there is orchestration involved, then I can see that might be an issue.

At this point, I'm going to go ahead and consider this issue resolved, unless you find something otherwise. Please feel free to shoot me an email/open an issue if you find something else.

[flovilmart]

Yeah that was my feeling too. We've seen high memory pressure during the build. So that don't seem to be related to your package. Thanks again for your time!

[drew-gross]

We are going to remove the GCS adapter from the repo, which will solve the issue for anyone not using the GCS adapter.