API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 3rd, 2012
40
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.43 KB | None | 0 0
raw download clone embed print report
  1. $ make deploy
  2. yes | jitsu deploy
  3. info: Welcome to Nodejitsu jetienne
  4. info: jitsu v0.9.7
  5. info: It worked if it ends with Nodejitsu ok
  6. info: Executing command deploy
  7. info: Analyzing your application dependencies in server.js
  8. warn: Local package version appears to be old
  9. warn: The package.json version will be incremented automatically
  10. warn: About to write /Users/jeromeetienne/webwork/tquery-multiplayerserver/package.json
  11. warn: Using '*' as a version for dependencies may eventually cause issues
  12. warn: Use specific versions for dependencies to avoid future problems
  13. warn: See: http://package.json.jit.su for more information
  14. data:
  15. data: {
  16. data: dependencies: {
  17. data: socket.io: '0.9.x',
  18. data: jade: '*',
  19. data: express: '3.0.0rc3'
  20. data: },
  21. data: engines: { node: '0.8.x' },
  22. data: version: '0.0.0-17',
  23. data: subdomain: 'jetienne.tquery-multiplayerserver',
  24. data: scripts: { start: 'server.js' },
  25. data: private: true,
  26. data: name: 'tquery-multiplayerserver'
  27. data: }
  28. data:
  29. prompt: Is this ok?: (yes) info: Creating snapshot 0.0.0-17
  30. info: Updating app tquery-multiplayerserver
  31. info: Activating snapshot 0.0.0-17 for tquery-multiplayerserver
  32. info: Starting app tquery-multiplayerserver
  33. error: Error running command deploy
  34. error: Nodejitsu Error (500): Internal Server Error
  35. error: There was an error while attempting to deploy your application.
  36. error:
  37. error: NPM Install failed
  38. error: NPM failed to install dependencies
  39. error:
  40. error: This type of error is usually a user error.
  41. error: Error output from Haibu:
  42. error:
  43. error: npm http GET https://registry.npmjs.org/express/3.0.0rc3
  44. error: npm http GET https://registry.npmjs.org/jade
  45. error: npm http GET https://registry.npmjs.org/socket.io
  46. error: npm http 200 https://registry.npmjs.org/jade
  47. error: npm http 200 https://registry.npmjs.org/express/3.0.0rc3
  48. error: npm http GET https://registry.npmjs.org/jade/-/jade-0.27.2.tgz
  49. error: npm http GET https://registry.npmjs.org/express/-/express-3.0.0rc3.tgz
  50. error: npm http 200 https://registry.npmjs.org/socket.io
  51. error: npm http GET https://registry.npmjs.org/socket.io/-/socket.io-0.9.10.tgz
  52. error: npm http 200 https://registry.npmjs.org/jade/-/jade-0.27.2.tgz
  53. error: npm http 200 https://registry.npmjs.org/express/-/express-3.0.0rc3.tgz
  54. error: npm http 200 https://registry.npmjs.org/socket.io/-/socket.io-0.9.10.tgz
  55. error: npm WARN package.json jade@0.27.2 No README.md file found!
  56. error: npm http GET https://registry.npmjs.org/connect/2.4.3
  57. error: npm http GET https://registry.npmjs.org/commander/0.6.1
  58. error: npm http GET https://registry.npmjs.org/range-parser/0.0.4
  59. error: npm http GET https://registry.npmjs.org/mkdirp/0.3.3
  60. error: npm http GET https://registry.npmjs.org/cookie/0.0.4
  61. error: npm http GET https://registry.npmjs.org/crc/0.2.0
  62. error: npm http GET https://registry.npmjs.org/fresh/0.1.0
  63. error: npm http GET https://registry.npmjs.org/methods/0.0.1
  64. error: npm http GET https://registry.npmjs.org/send/0.0.3
  65. error: npm http GET https://registry.npmjs.org/debug
  66. error: npm http GET https://registry.npmjs.org/socket.io-client/0.9.10
  67. error: npm http GET https://registry.npmjs.org/policyfile/0.0.4
  68. error: npm http GET https://registry.npmjs.org/redis/0.7.2
  69. error: npm http GET https://registry.npmjs.org/mkdirp/0.3.0
  70. error: npm http 200 https://registry.npmjs.org/mkdirp/0.3.3
  71. error: npm http 200 https://registry.npmjs.org/commander/0.6.1
  72. error: npm http GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.3.tgz
  73. error: npm http GET https://registry.npmjs.org/commander/-/commander-0.6.1.tgz
  74. error: npm http 200 https://registry.npmjs.org/connect/2.4.3
  75. error: npm http 200 https://registry.npmjs.org/range-parser/0.0.4
  76. error: npm http GET https://registry.npmjs.org/connect/-/connect-2.4.3.tgz
  77. error: npm http GET https://registry.npmjs.org/range-parser/-/range-parser-0.0.4.tgz
  78. error: npm http 200 https://registry.npmjs.org/cookie/0.0.4
  79. error: npm http GET https://registry.npmjs.org/cookie/-/cookie-0.0.4.tgz
  80. error: npm http 200 https://registry.npmjs.org/crc/0.2.0
  81. error: npm http GET https://registry.npmjs.org/crc/-/crc-0.2.0.tgz
  82. error: npm http 200 https://registry.npmjs.org/debug
  83. error: npm http GET https://registry.npmjs.org/debug/-/debug-0.7.0.tgz
  84. error: npm http 200 https://registry.npmjs.org/fresh/0.1.0
  85. error: npm http GET https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz
  86. error: npm http 200 https://registry.npmjs.org/send/0.0.3
  87. error: npm http GET https://registry.npmjs.org/send/-/send-0.0.3.tgz
  88. error: npm http 200 https://registry.npmjs.org/socket.io-client/0.9.10
  89. error: npm http 200 https://registry.npmjs.org/redis/0.7.2
  90. error: npm http GET https://registry.npmjs.org/socket.io-client/-/socket.io-client-0.9.10.tgz
  91. error: npm http GET https://registry.npmjs.org/redis/-/redis-0.7.2.tgz
  92. error: npm http 200 https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.3.tgz
  93. error: npm http 200 https://registry.npmjs.org/commander/-/commander-0.6.1.tgz
  94. error: npm http 200 https://registry.npmjs.org/methods/0.0.1
  95. error: npm http GET https://registry.npmjs.org/methods/-/methods-0.0.1.tgz
  96. error: npm http 200 https://registry.npmjs.org/connect/-/connect-2.4.3.tgz
  97. error: npm http 200 https://registry.npmjs.org/range-parser/-/range-parser-0.0.4.tgz
  98. error: npm http 200 https://registry.npmjs.org/mkdirp/0.3.0
  99. error: npm http GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz
  100. error: npm http 200 https://registry.npmjs.org/crc/-/crc-0.2.0.tgz
  101. error: npm http 200 https://registry.npmjs.org/policyfile/0.0.4
  102. error: npm http 200 https://registry.npmjs.org/cookie/-/cookie-0.0.4.tgz
  103. error: npm http GET https://registry.npmjs.org/policyfile/-/policyfile-0.0.4.tgz
  104. error: npm http 200 https://registry.npmjs.org/debug/-/debug-0.7.0.tgz
  105. error: npm http 200 https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz
  106. error: npm http 200 https://registry.npmjs.org/send/-/send-0.0.3.tgz
  107. error: npm http 200 https://registry.npmjs.org/socket.io-client/-/socket.io-client-0.9.10.tgz
  108. error: npm http 200 https://registry.npmjs.org/redis/-/redis-0.7.2.tgz
  109. error: npm http 200 https://registry.npmjs.org/policyfile/-/policyfile-0.0.4.tgz
  110. error: npm http 200 https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz
  111. error: npm http 200 https://registry.npmjs.org/methods/-/methods-0.0.1.tgz
  112. error: npm WARN package.json methods@0.0.1 No README.md file found!
  113. error: FATAL ERROR: Malloced operator new Allocation failed - process out of memory
  114. error:
  115. help: For help with this error contact Nodejitsu Support:
  116. help: webchat: <http://webchat.nodejitsu.com/>
  117. help: irc: <irc://chat.freenode.net/#nodejitsu>
  118. help: email: <support@nodejitsu.com>
  119. help:
  120. help: Copy and paste this output to a gist (http://gist.github.com/)
  121. info: Nodejitsu not ok
  122. make: *** [deploy] Error 1
  123. jeromeetienne@jmemacgpu:~/webwork/tquery-multiplayerserver$ make deploy
  124. yes | jitsu deploy
  125. info: Welcome to Nodejitsu jetienne
  126. info: jitsu v0.9.7
  127. info: It worked if it ends with Nodejitsu ok
  128. info: Executing command deploy
  129. info: Analyzing your application dependencies in server.js
  130. warn: Local package version appears to be old
  131. warn: The package.json version will be incremented automatically
  132. warn: About to write /Users/jeromeetienne/webwork/tquery-multiplayerserver/package.json
  133. warn: Using '*' as a version for dependencies may eventually cause issues
  134. warn: Use specific versions for dependencies to avoid future problems
  135. warn: See: http://package.json.jit.su for more information
  136. data:
  137. data: {
  138. data: version: '0.0.0-18',
  139. data: private: true,
  140. data: name: 'tquery-multiplayerserver',
  141. data: subdomain: 'jetienne.tquery-multiplayerserver',
  142. data: dependencies: {
  143. data: jade: '*',
  144. data: socket.io: '0.9.x',
  145. data: express: '3.0.0rc3'
  146. data: },
  147. data: scripts: { start: 'server.js' },
  148. data: engines: { node: '0.8.x' }
  149. data: }
  150. data:
  151. prompt: Is this ok?: (yes) info: Creating snapshot 0.0.0-18
  152. info: Updating app tquery-multiplayerserver
  153. info: Activating snapshot 0.0.0-18 for tquery-multiplayerserver
  154. info: Starting app tquery-multiplayerserver
  155. error: Error running command deploy
  156. error: socket hang up
  157. help: For help with this error contact Nodejitsu Support:
  158. help: webchat: <http://webchat.nodejitsu.com/>
  159. help: irc: <irc://chat.freenode.net/#nodejitsu>
  160. help: email: <support@nodejitsu.com>
  161. help:
  162. help: Copy and paste this output to a gist (http://gist.github.com/)
  163. info: Nodejitsu not ok
  164. make: *** [deploy] Error 1
  165. jeromeetienne@jmemacgpu:~/webwork/tquery-multiplayerserver$ make deploy
  166. yes | jitsu deploy
  167. info: Welcome to Nodejitsu jetienne
  168. info: jitsu v0.9.7
  169. info: It worked if it ends with Nodejitsu ok
  170. info: Executing command deploy
  171. info: Analyzing your application dependencies in server.js
  172. warn: Local package version appears to be old
  173. warn: The package.json version will be incremented automatically
  174. warn: About to write /Users/jeromeetienne/webwork/tquery-multiplayerserver/package.json
  175. warn: Using '*' as a version for dependencies may eventually cause issues
  176. warn: Use specific versions for dependencies to avoid future problems
  177. warn: See: http://package.json.jit.su for more information
  178. data:
  179. data: {
  180. data: version: '0.0.0-19',
  181. data: name: 'tquery-multiplayerserver',
  182. data: private: true,
  183. data: subdomain: 'jetienne.tquery-multiplayerserver',
  184. data: scripts: { start: 'server.js' },
  185. data: dependencies: {
  186. data: express: '3.0.0rc3',
  187. data: jade: '*',
  188. data: socket.io: '0.9.x'
  189. data: },
  190. data: engines: { node: '0.8.x' }
  191. data: }
  192. data:
  193. prompt: Is this ok?: (yes) info: Creating snapshot 0.0.0-19
  194. info: Updating app tquery-multiplayerserver
  195. info: Activating snapshot 0.0.0-19 for tquery-multiplayerserver
  196. info: Starting app tquery-multiplayerserver
  197. error: Error running command deploy
  198. error: socket hang up
  199. help: For help with this error contact Nodejitsu Support:
  200. help: webchat: <http://webchat.nodejitsu.com/>
  201. help: irc: <irc://chat.freenode.net/#nodejitsu>
  202. help: email: <support@nodejitsu.com>
  203. help:
  204. help: Copy and paste this output to a gist (http://gist.github.com/)
  205. info: Nodejitsu not ok
  206. make: *** [deploy] Error 1
  207. jeromeetienne@jmemacgpu:~/webwork/tquery-multiplayerserver$ make deploy
  208. yes | jitsu deploy
  209. info: Welcome to Nodejitsu jetienne
  210. info: jitsu v0.9.7
  211. info: It worked if it ends with Nodejitsu ok
  212. info: Executing command deploy
  213. info: Analyzing your application dependencies in server.js
  214. warn: Local package version appears to be old
  215. warn: The package.json version will be incremented automatically
  216. warn: About to write /Users/jeromeetienne/webwork/tquery-multiplayerserver/package.json
  217. warn: Using '*' as a version for dependencies may eventually cause issues
  218. warn: Use specific versions for dependencies to avoid future problems
  219. warn: See: http://package.json.jit.su for more information
  220. data:
  221. data: {
  222. data: dependencies: {
  223. data: jade: '*',
  224. data: socket.io: '0.9.x',
  225. data: express: '3.0.0rc3'
  226. data: },
  227. data: private: true,
  228. data: engines: { node: '0.8.x' },
  229. data: version: '0.0.0-20',
  230. data: scripts: { start: 'server.js' },
  231. data: name: 'tquery-multiplayerserver',
  232. data: subdomain: 'jetienne.tquery-multiplayerserver'
  233. data: }
  234. data:
  235. prompt: Is this ok?: (yes) info: Creating snapshot 0.0.0-20
  236. info: Updating app tquery-multiplayerserver
  237. info: Activating snapshot 0.0.0-20 for tquery-multiplayerserver
  238. info: Starting app tquery-multiplayerserver
  239. error: Error running command deploy
  240. error: socket hang up
  241. help: For help with this error contact Nodejitsu Support:
  242. help: webchat: <http://webchat.nodejitsu.com/>
  243. help: irc: <irc://chat.freenode.net/#nodejitsu>
  244. help: email: <support@nodejitsu.com>
  245. help:
  246. help: Copy and paste this output to a gist (http://gist.github.com/)
  247. info: Nodejitsu not ok
  248. make: *** [deploy] Error 1
  249. jeromeetienne@jmemacgpu:~/webwork/tquery-multiplayerserver$
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!