sdc-setup failed with an exception #10

Closed
edwardw opened this Issue Dec 2, 2011 · 7 comments

Comments

Projects
None yet
2 participants
@edwardw

edwardw commented Dec 2, 2011

I followed "Getting Started" instructions in http://api.joyentcloud.com/ and installed node, npm and smartdc package. But my very first run of sdc-setup failed with an exception:

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: No such module
    at Object.<anonymous> (/usr/local/lib/node_modules/smartdc/bin/sdc-setup:33:21)
    at Module._compile (module.js:432:26)
    at Object..js (module.js:450:10)
    at Module.load (module.js:351:31)
    at Function._load (module.js:310:12)
    at Array.0 (module.js:470:10)
    at EventEmitter._tickCallback (node.js:192:40)

I used:

Mac OS X 10.6.8
node 0.6.3
npm 1.0.106

and npm list gives me:

/Users/edward/ws/node
└─┬ smartdc@6.5.0-1 
  ├── lru-cache@1.0.4 
  ├─┬ nopt@1.0.10 
  │ └── abbrev@1.0.3 
  ├─┬ restify@0.4.4 
  │ ├── formidable@1.0.2 
  │ ├── httpu@0.0.1 
  │ ├── node-uuid@1.2.0 
  │ ├── retry@0.4.0 
  │ └── semver@1.0.12 
  ├── sprintf@0.1.1 
  └─┬ ssh-agent@0.1.0 
    └── ctype@0.3.1 

I also tried node 0.6.2 installed by homebrew. Same error.

@mcavage

This comment has been minimized.

Show comment Hide comment
@mcavage

mcavage Dec 2, 2011

Contributor

Hi,

I believe this is because you are on node 0.6, which this library has not yet been tested against (yet). I will investigate what is needed for it to run correctly on node 0.6.

Contributor

mcavage commented Dec 2, 2011

Hi,

I believe this is because you are on node 0.6, which this library has not yet been tested against (yet). I will investigate what is needed for it to run correctly on node 0.6.

@edwardw

This comment has been minimized.

Show comment Hide comment
@edwardw

edwardw Dec 3, 2011

Please do so. I installed node 0.5.9, but it didn't work with latest npm. I also tried to build and install npm from source. No luck either. None of tag v1.0.x, v0.3.x, or head worked with node 0.5.9; sudo make install under npm repository all ended up with a segmentation fault.

edwardw commented Dec 3, 2011

Please do so. I installed node 0.5.9, but it didn't work with latest npm. I also tried to build and install npm from source. No luck either. None of tag v1.0.x, v0.3.x, or head worked with node 0.5.9; sudo make install under npm repository all ended up with a segmentation fault.

@mcavage

This comment has been minimized.

Show comment Hide comment
@mcavage

mcavage Dec 3, 2011

Contributor

It's on my short term list - for now, try it with node 0.4.12 - this library was published when 0.4.x was current.

Contributor

mcavage commented Dec 3, 2011

It's on my short term list - for now, try it with node 0.4.12 - this library was published when 0.4.x was current.

@edwardw

This comment has been minimized.

Show comment Hide comment
@edwardw

edwardw Dec 3, 2011

Hurrah, it does work with node 0.4.12 and latest npm, although sdc-* commands all end up with a 'HTTP Client error event' error but that is a different matter.

node 0.4.12 is the workaround for now.

edwardw commented Dec 3, 2011

Hurrah, it does work with node 0.4.12 and latest npm, although sdc-* commands all end up with a 'HTTP Client error event' error but that is a different matter.

node 0.4.12 is the workaround for now.

@mcavage

This comment has been minimized.

Show comment Hide comment
@mcavage

mcavage Dec 3, 2011

Contributor

Ok great. For the error event, I'm going to bet you're using the wrong url (like http instead of https, perhaps?).

Contributor

mcavage commented Dec 3, 2011

Ok great. For the error event, I'm going to bet you're using the wrong url (like http instead of https, perhaps?).

mcavage pushed a commit that referenced this issue Dec 5, 2011

@mcavage

This comment has been minimized.

Show comment Hide comment
@mcavage

mcavage Dec 5, 2011

Contributor

This is now available in npm as 6.5.0-2. Thanks for the error report!

Contributor

mcavage commented Dec 5, 2011

This is now available in npm as 6.5.0-2. Thanks for the error report!

@mcavage mcavage closed this Dec 5, 2011

mcavage pushed a commit that referenced this issue Dec 5, 2011

@edwardw

This comment has been minimized.

Show comment Hide comment
@edwardw

edwardw Dec 6, 2011

Works like a charm!

edwardw commented Dec 6, 2011

Works like a charm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment