0

I tried to install Hyperledger Composer on my AWS Lightsail following instructions documented on https://hyperledger.github.io/composer/installing/development-tools.html

I succeeded until step 3, where I entered npm install -g composer-rest-server. It complains about several deprecated items and on the 5th times, it just got frozen. image

Can someone please help? Thanks!

Max
  • 915
  • 10
  • 28
Redscarfs
  • 1
  • 1
  • What's the spec of the machine and what are you trying to run concurrently in this machine ? Maybe you don't have enough memory ? – david_k Aug 05 '17 at 09:56
  • Thanks for your reply. According to AWS, Lightsail has 512MB memory, 1vCPU, 20GB SSD and 1TB data transfer (more detailed analysis on https://stackoverflow.com/questions/40927189/what-is-difference-between-lightsail-and-ec2). – Redscarfs Aug 05 '17 at 19:16
  • I too suspect the Lightsail is too "weak" but how can I check if the problem is memory related? Is there anything I can do (other than using a more powerful VPS?)? – Redscarfs Aug 05 '17 at 19:19
  • I am not running anything else on this instance / VPS other than Fabric and Composer files from Hyperledger. – Redscarfs Aug 05 '17 at 19:21
  • we recommend a memory footprint of at least 3.75Gb, so I suspect its failing to build the Fabric environment as part of the composer install (tutorial includes standing up a Dev Fabric environment). Ps what OS distro did you use for the Lightsail service in the end? – Paul O'Mahony Aug 08 '17 at 16:04

1 Answers1

0

we recommend a memory footprint of at least 3.75Gb, so I suspect its failing to build the Fabric environment as part of the composer install (tutorial includes standing up a Dev Fabric environment).

Paul O'Mahony
  • 6,740
  • 1
  • 10
  • 15
  • Thank you. Memory is probably a critical success factor. Will try to use another server with more memory. Incidentally, can the various "deprecated" warnings signs of other problems? – Redscarfs Aug 10 '17 at 09:51
  • not really (where Composer is concerned) - these are 'standard' nodejs messages seen during the install. This warning is displayed because one of your direct dependency is out of date or one the npm packages in the dependency tree. This article will help explain -> https://www.triplet.fi/blog/how_node_package_deprecation_works/ – Paul O'Mahony Aug 11 '17 at 13:46