new

Cannot connect to MongoDB

Last edited on 3/27/2013 by @yawnt
-18

Cause

MongoDB <0.9.9.8, 1.1.8-1.1.10 don't work on SunOS.

Solution

Roll back to MongoDB 1.1.7. MongoDB 1.1.11 should work also. if you're using mongoose, mongoose 2.5.13 - 3.2.1 should work

error:   Error: failed to connect to [mongo_host:port]

Redis

Last edited on 3/27/2013 by @yawnt
3

Cause

Hiredis is not compatible with smartOS

Solution

npm install hiredis; npm install redis; npm uninstall hiredis... Then add ['redis'] to bundledDependencies

error:  node: fatal: relocation error: 
file /opt/haibu/apps/hallijo/testapp/package/node_modules/redis/
node_modules/hiredis/build/Release/hiredis.node: symbol 
redisReaderCreate: referenced symbol not found"
new

Rackspace Error (404): Item not found

Last edited on 3/27/2013 by @yawnt
20

Cause

The Rackspace cloud files service is taking too long to report that the snapshot has indeed uploaded, since the nodejitsu stack can't download the snapshot from cloudfiles, the deploy fails.

Solution

Most likely the snapshot will be available moments after you recieve this error. To deploy your new snapshot, run `jitsu snapshots activate <[username/]appname>`. Once activated run `jitsu apps start` to start your app.

error:   Error running command deploy
error:   Nodejitsu Error (500): Internal Server Error
error:   There was an error while attempting to deploy the app
error:   
error:   Rackspace Error (404): Item not found
error:   Error output from Haibu:
error:   
error:   Error: Rackspace Error (404): Item not found
error:       at Request._callback (/root/haibu-orchestra/node_modules/
haibu/node_modules/cloudfiles/lib/cloudfiles/common.js:184:18)
error:       at Request.init.self.callback (/root/haibu-orchestra/
node_modules/haibu/node_modules/request/main.js:119:22)
error:       at Request.EventEmitter.emit (events.js:91:17)
error:       at Request.<anonymous> (/root/haibu-orchestra/node_modules/
haibu/node_modules/request/main.js:521:16)
error:       at Request.EventEmitter.emit (events.js:115:20)
error:       at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer 
(/root/haibu-orchestra/node_modules/haibu/node_modules/request/main.js:483:14)
error:       at IncomingMessage.EventEmitter.emit (events.js:115:20)
error:       at IncomingMessage._emitEnd (http.js:366:10)
error:       at IncomingMessage._emitPending (http.js:338:16)
error:       at process.startup.processNextTick.process._tickCallback (node.js:244:9)
new

Script took too long to listen on a socket

Last edited on 3/27/2013 by @yawnt
10

Cause

Your application is not listening to a port in less than 20 seconds.

Solution

Fix the bug in your application or make it listen to a port more earlier

error:   Error running command deploy
error:   Nodejitsu Error (500): Internal Server Error
error:   There was an error while attempting to deploy the app
error:   
error:   Error spawning drone
error:   Script took too long to listen on a socket
error:   
error:   This type of error is usually a user error.
error:   Error output from Haibu:
error:   
error:   Error: Error spawning drone
error:       at Object.onTimeout [as _onTimeout] (/root/haibu-orchestra/node_modules/haibu/lib/haibu/core/spawner.js:396:15)
error:       at Timer.list.ontimeout (timers.js:101:19)
new

Cannot install jitsu with npm 1.2.0 on OSX

Last edited on 3/27/2013 by @yawnt
31

Cause

It's an npm bug, see https://github.com/isaacs/npm/issues/3047 for more information

Solution

Do a `npm cache clean` and retry the installation. If it doesn't work just downgrade npm to 1.1.70 with `npm install -g npm@1.1.70` and retry again, it should work fine.

npm http GET https://registry.npmjs.org/prompt
/usr/local/share/npm/bin/jitsu -> /usr/local/share/npm/lib/node_modules/jitsu/bin/jitsu
npm ERR! Error: ENOENT, open '/usr/local/share/npm/lib/node_modules/jitsu/
node_modules/request/tests/test-https-strict.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Darwin 12.2.0
npm ERR! command "/usr/local/Cellar/node/0.8.17/bin/node" "/usr/local/bin/npm" 
"install" "jitsu" "-g"
npm ERR! cwd /Users/julianduque
npm ERR! node -v v0.8.17
npm ERR! npm -v 1.2.0
npm ERR! path /usr/local/share/npm/lib/node_modules/jitsu/node_modules/
request/tests/test-https-strict.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/usr/local/share/npm/lib/
node_modules/jitsu/node_modules/require-analyzer/test/fixtures/example-app1/node_modules'
npm ERR! error rolling back  jitsu@0.11.5 { [Error: ENOTEMPTY, rmdir '/usr/local/
share/npm/lib/node_modules/jitsu/node_modules/require-analyzer/test/
fixtures/example-app1/node_modules']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/usr/local/share/npm/lib/node_modules/
jitsu/node_modules/require-analyzer/test/fixtures/example-app1/node_modules' }
npm ERR! EEXIST, symlink '../lib/node_modules/jitsu/bin/jitsu'
File exists: ../lib/node_modules/jitsu/bin/jitsu
Move it away, and try again. 

npm ERR! System Darwin 12.2.0
npm ERR! command "/usr/local/Cellar/node/0.8.17/bin/node" "/usr/local/bin/npm" "install" "jitsu" "-g"
npm ERR! cwd /Users/julianduque
npm ERR! node -v v0.8.17
npm ERR! npm -v 1.2.0
npm ERR! path ../lib/node_modules/jitsu/bin/jitsu
npm ERR! code EEXIST
npm ERR! errno 47
npm ERR! Error: ENOENT, lstat '/usr/local/share/npm/lib/node_modules/jitsu/
node_modules/npm/man/man1/index.1'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

Connect ECONNREFUSED

Last edited on 3/27/2013 by @yawnt
0

Cause

The target drone server can't be contacted for network or capacity reasons.

Solution

Let support know, and try your deploy again.

error: Error running command deploy
error: Nodejitsu Error (500): Internal Server Error
warn: Error returned from Nodejitsu
error: Error: connect ECONNREFUSED
error: at errnoException (net.js:768:11)
error: at Object.afterConnect [as oncomplete] (net.js:759:19)

No matching versions found

Last edited on 3/27/2013 by @yawnt
0

Cause

Invalid version of something most likely in your package.json file.

Solution

Check your package.json file, especially the engine property. Make sure node is using "0.6.x" or "0.8.x" . Specific patch versions may not be supported as they may have vulnerabilities, or have not yet been tested.

error:   Error running command deploy
error:   Nodejitsu Error (500): Internal Server Error
error:   No matching versions found
new

App subdomain already exists

Last edited on 3/27/2013 by @yawnt
-28

Cause

There is a conflict with the subdomain set in your package.json. If somebody else has reserved this subdomain name before you have, you will see this error.

Solution

If this is your first time deploying the app, choose a different subdomain name. If, however, this is a subsequent deploy make sure you did not end up changing your app name.

Error: App subdomain already exists
new

Socket Hang Up

Last edited on 3/27/2013 by @yawnt
26

Cause

Varies. Bad Drone, network problems (client or server), Application takes up too much memory on spawn, or connection forcibly closed on a drone.

Solution

Use the command "jitsu logs" and see details of your problem.

error: Error running command deploy
error: Nodejitsu Error (500): Internal Server Error
warn: Error returned from Nodejitsu
error: Error: socket hang up
error: at createHangUpError (http.js:1263:15)
error: at Socket.socketOnEnd (http.js:1351:23)
error: at TCP.onread (net.js:417:26)
info: Nodejitsu not ok