Unable to access SSH workspace


#1

Hi Team,

I’m trying to access an SSH workspace on EC2 that I’ve successfully used for a number of days, and for some reason now it fails during the “installation” process. The error console shows the following:

Installation Started

Package Cloud9 IDE 1
--------------------

Installing Node.js
+ SOURCE=-1
+ TARGET=/home/ec2-user/.c9/node
+ URL=http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz
+ DIR=node-v4.4.6-linux-x64
+ '[' '!' -1 ']'
+ '[' '!' http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz ']'
+ '[' '!' /home/ec2-user/.c9/node ']'
+ '[' node-v4.4.6-linux-x64 ']'
+ set +e
+ rm -Rf /home/ec2-user/.c9/node
+ set -e
+ mkdir -p /home/ec2-user/.c9/node
+ cd /home/ec2-user/.c9/node
+ '[' http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz ']'
+ has wget
+ type wget
+ return 1
+ has curl
+ type curl
+ return 0
+ DOWNLOAD='curl -sSOL'
+ echo 'Downloading... http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz'
+ printf '\e[01;30m'
+ curl -sSOL http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz
Downloading... http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz
curl: (18) transfer closed with 11972845 bytes remaining to read
+ printf '\e[0m'
++ basename http://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.gz
+ SOURCE=/home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz
++ dirname /home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz
++ dirname /home/ec2-user/.c9/node/x
+ '[' /home/ec2-user/.c9/node '!=' /home/ec2-user/.c9/node ']'
+ echo 'Unpacking... /home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz'
+ printf '\e[01;30m'
+ tar -U -zxf /home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz
Unpacking... /home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
+ printf '\e[0m'
+ rm -Rf /home/ec2-user/.c9/node/node-v4.4.6-linux-x64.tar.gz
+ '[' node-v4.4.6-linux-x64 ']'
+ echo 'Merging... /home/ec2-user/.c9/node/node-v4.4.6-linux-x64 in /home/ec2-user/.c9/node'
+ printf '\e[01;30m'
+ merge
+ mkdir -p c9_tmp
Merging... /home/ec2-user/.c9/node/node-v4.4.6-linux-x64 in /home/ec2-user/.c9/node
+ rm -rf c9_tmp/node-v4.4.6-linux-x64
+ mv node-v4.4.6-linux-x64 c9_tmp/node-v4.4.6-linux-x64
+ mv c9_tmp/node-v4.4.6-linux-x64/bin .
+ set +e
+ mv c9_tmp/node-v4.4.6-linux-x64/. c9_tmp/node-v4.4.6-linux-x64/.. .
+ set -e
+ rm -rf c9_tmp
+ printf '\e[0m'

+ echo $'\303\237'
bash: line 75: /home/ec2-user/.c9/node/bin/npm: No such file or directory
bash: line 70: /home/ec2-user/.c9/node/bin/npm: No such file or directory
bash: line 71: /home/ec2-user/.c9/node/bin/npm: No such file or directory

Failed Bash. Exit code 1

One or more errors occured. Please try to resolve them and restart Cloud9 or contact support@c9.io.

It looks like it’s trying to download Node 4 (to upgrade 0.10 installed as a system package), fails, and precipitates after that.

Has something changed on c9.io that resulted in this error? I can download NodeJS using the same link without a problem, so it doesn’t seem to be that repo’s problem.

Thanks!


#2

Ok, looks like it has been resolved. I had to install npm as a system package (not previously required).