Hello, When I try to start the Haste-server, I'm getting this error:

I just did that, same error: <a href="http://puu.sh/5rYo1.png" rel="

<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto"

root@thezip:~/haste-server# npm install npm http GET <a href="https://registry.npm

Error on startup,about toptal/haste-server

Comments (27)

seejohnrun commented on July 21, 2024

are you sure redis is running and accessible?

from haste-server.

matthijs110 commented on July 21, 2024

I just did that, same error:

http://puu.sh/5rYo1.png

from haste-server.

seejohnrun commented on July 21, 2024

Please pull latest, and re-run so we can see the full error

from haste-server.

matthijs110 commented on July 21, 2024

How?

from haste-server.

seejohnrun commented on July 21, 2024

$ git pull origin master
$ npm start

from haste-server.

matthijs110 commented on July 21, 2024

Got this now:

http://puu.sh/5rZoX.png

from haste-server.

seejohnrun commented on July 21, 2024

The relevant part of that screenshot is cut off

from haste-server.

matthijs110 commented on July 21, 2024

http://puu.sh/5rZu2.png

from haste-server.

seejohnrun commented on July 21, 2024

you need to run npm install

On Sun, Nov 24, 2013 at 12:13 PM, Matthijs [email protected] wrote:

http://puu.sh/5rZu2.png

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-29160127
.

from haste-server.

matthijs110 commented on July 21, 2024

[email protected] node_modules/should

[email protected] node_modules/redis

[email protected] node_modules/uglify-js

[email protected] node_modules/winston
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[email protected] node_modules/connect
├── [email protected]
├── [email protected]
└── [email protected]

[email protected] node_modules/mocha
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected])
root@thezip:~/haste-server# npm start

[email protected] start /root/haste-server
node server.js

info: configuring redis
info: compressed application.js into application.min.js
info: loading static document name=about, path=./about.md
info: listening on 0.0.0.0:7777
error: error connecting to redis index 2 error=Redis connection to 0.0.0.0:6379 failed - connect ECONNREFUSED
npm ERR! [email protected] start: node server.js
npm ERR! sh "-c" "node server.js" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the haste package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls haste
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 2.6.32-042stab083.2
npm ERR! command "node" "/usr/local/bin/npm" "start"
npm ERR! cwd /root/haste-server
npm ERR! node -v v0.8.20
npm ERR! npm -v 1.1.71
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/haste-server/npm-debug.log
npm ERR! not ok code 0
root@thezip:~/haste-server#

from haste-server.

seejohnrun commented on July 21, 2024

ECONNREFUSED means it cannot connect to a redis instance on 6379
make sure redis is running, and that you can connect to it with redis-cli
without issue

On Sun, Nov 24, 2013 at 12:16 PM, Matthijs [email protected] wrote:

root@thezip:~/haste-server# npm install
npm http GET https://registry.npmjs.org/winston/0.6.2
npm http GET https://registry.npmjs.org/connect/1.9.2
npm http GET https://registry.npmjs.org/redis-url/0.1.0
npm http GET https://registry.npmjs.org/redis/0.8.1
npm http GET https://registry.npmjs.org/uglify-js/1.3.3
npm http GET https://registry.npmjs.org/mocha
npm http GET https://registry.npmjs.org/should
npm http 304 https://registry.npmjs.org/winston/0.6.2
npm http 304 https://registry.npmjs.org/connect/1.9.2
npm WARN package.json [email protected] No README.md file found!
npm http 304 https://registry.npmjs.org/mocha
npm http 304 https://registry.npmjs.org/redis/0.8.1
npm http 304 https://registry.npmjs.org/should
npm http 304 https://registry.npmjs.org/redis-url/0.1.0
npm http 304 https://registry.npmjs.org/uglify-js/1.3.3
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/cycle
npm http GET https://registry.npmjs.org/eyes
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/stack-trace
npm http GET https://registry.npmjs.org/commander/2.0.0
npm http GET https://registry.npmjs.org/growl
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/jade/0.26.3
npm http GET https://registry.npmjs.org/formidable
npm http GET https://registry.npmjs.org/diff/1.0.7
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/mkdirp/0.3.5
npm http GET https://registry.npmjs.org/glob/3.2.3
npm http 304 https://registry.npmjs.org/cycle
npm http 304 https://registry.npmjs.org/eyes
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/commander/2.0.0
npm http 304 https://registry.npmjs.org/stack-trace
npm http 304 https://registry.npmjs.org/growl
npm http 304 https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/jade/0.26.3
npm WARN package.json [email protected] No README.md file found!
npm http 304 https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/diff/1.0.7
npm http 304 https://registry.npmjs.org/formidable
npm http 304 https://registry.npmjs.org/mkdirp/0.3.5
npm http 304 https://registry.npmjs.org/glob/3.2.3
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/commander/0.6.1
npm http GET https://registry.npmjs.org/mkdirp/0.3.0
npm http GET https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/mkdirp/0.3.0
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/commander/0.6.1
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/lru-cache
[email protected] node_modules/redis-url

[email protected] node_modules/should

[email protected] node_modules/redis

[email protected] node_modules/uglify-js

[email protected] node_modules/winston
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[email protected] node_modules/connect
├── [email protected]
├── [email protected]
└── [email protected]

[email protected] node_modules/mocha
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected])
root@thezip:~/haste-server# npm start

[email protected] start /root/haste-server
node server.js

info: configuring redis
info: compressed application.js into application.min.js
info: loading static document name=about, path=./about.md
info: listening on 0.0.0.0:7777
error: error connecting to redis index 2 error=Redis connection to
0.0.0.0:6379 failed - connect ECONNREFUSED
npm ERR! [email protected] start: node server.js
npm ERR! sh "-c" "node server.js" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the haste package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls haste
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 2.6.32-042stab083.2
npm ERR! command "node" "/usr/local/bin/npm" "start"
npm ERR! cwd /root/haste-server
npm ERR! node -v v0.8.20
npm ERR! npm -v 1.1.71
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/haste-server/npm-debug.log
npm ERR! not ok code 0

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-29160198
.

from haste-server.

matthijs110 commented on July 21, 2024

When I do that, it says "Could not connect to Redis at 127.0.0.1:6379: Connection refused"

from haste-server.

seejohnrun commented on July 21, 2024

yep - sounds like you don't have a redis-server running (or it's not running properly).
ECONNREFUSED == Connection refused

not sure what could be wrong with your redis server, but I won't be of much help with that :(

from haste-server.

matthijs110 commented on July 21, 2024

Its running now , but I still got a error:

http://puu.sh/5s0uI.png

from haste-server.

matthijs110 commented on July 21, 2024

What could be wrong there? Redis is running now..

from haste-server.

seejohnrun commented on July 21, 2024

You're not in the right directory.

On Sun, Nov 24, 2013 at 12:44 PM, Matthijs [email protected] wrote:

What could be wrong there? Redis is running now..

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-29160926
.

from haste-server.

matthijs110 commented on July 21, 2024

Woops, my bad.. I think it is running now:

from haste-server.

seejohnrun commented on July 21, 2024

cool - glad to hear it :)

from haste-server.

matthijs110 commented on July 21, 2024

I changed the port, and since then I can't get it back to work :/

root@thezip:~/haste-server# npm start

[email protected] start /root/haste-server
node server.js

info: configuring redis
info: compressed application.js into application.min.js
info: loading static document name=about, path=./about.md
info: listening on 0.0.0.0:80

events.js:71
throw arguments[1]; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at errnoException (net.js:770:11)
at HTTPServer.Server._listen2 (net.js:910:14)
at listen (net.js:937:10)
at Server.listen (net.js:994:9)
at dns.js:72:18
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
npm ERR! [email protected] start: node server.js
npm ERR! sh "-c" "node server.js" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the haste package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls haste
npm ERR! There is likely additional logging output above.

from haste-server.

seejohnrun commented on July 21, 2024

You have something running on port 80 (probably apache or something)

from haste-server.

matthijs110 commented on July 21, 2024

If I put it back to 7777 then I still get the same error

from haste-server.

matthijs110 commented on July 21, 2024

And Apache isn't running

from haste-server.

seejohnrun commented on July 21, 2024

The error says "Error: listen EADDRINUSE" - meaning the port (whichever) is already used by another application.
On port 7777 it might be the previous instance you started, and maybe never terminated successfully.
On port 80, it could be anything - apache, nginx, etc. Visit http://localhost in a browser and see what comes back

from haste-server.

matthijs110 commented on July 21, 2024

Its running now on port 7777

I am using Apache, how can I do this:

hastebin.domain.com instead of domain.com:7777 ?

from haste-server.

seejohnrun commented on July 21, 2024

You'd have to turn off apache or run it through apache (look up passthrough virtual hosts in apache). I can't provide much advice on that, apache docs could help you more.

Sent from my iPhone

On Nov 24, 2013, at 2:45 PM, Matthijs [email protected] wrote:

Its running now on port 7777

I am using Apache, how can I do this:

hastebin.domain.com instead of domain.com:7777 ?

—
Reply to this email directly or view it on GitHub.

from haste-server.

davidjmorin commented on July 21, 2024

I get this error... anyone assist?

root@104:/var/www/mydroid/wiki/mediawiki/code# npm start

[email protected] start /var/www/mydroid/wiki/mediawiki/code
node server.js

npm ERR! [email protected] start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the haste package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls haste
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.2.0-4-amd64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! cwd /var/www/mydroid/wiki/mediawiki/code
npm ERR! node -v v0.13.0-pre
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /var/www/mydroid/wiki/mediawiki/code/npm-debug.log
npm ERR! not ok code 0

from haste-server.

seejohnrun commented on July 21, 2024

@davidjmorin looks like an issue connecting to redis - are you sure redis is running on the host and port you specified? check out redis-cli for more details

from haste-server.

Error on startup about haste-server HOT 27 CLOSED

Comments (27)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent