yhat/rodeo

Crashed on startup with exception

Open

#443 opened on Aug 30, 2016

View on GitHub
 (10 comments) (0 reactions) (0 assignees)JavaScript (3,934 stars) (473 forks)batch import
bughelp wanted

Description

➜ Rodeo ./Rodeo error: uncaughtException: listen EADDRINUSE :::9356 date=Tue Aug 30 2016 14:18:14 GMT+0800 (CST), pid=21420, uid=1000, gid=1000, cwd=/opt/Rodeo, execPath=/opt/Rodeo/Rodeo, version=v6.1.0, argv=[/opt/Rodeo/Rodeo], rss=76107776, heapTotal=27303936, heapUsed=19576576, loadavg=[1.6904296875, 2.2021484375, 2.14697265625], uptime=100301 Error: listen EADDRINUSE :::9356 at Object.exports._errnoException (util.js:949:11) at exports._exceptionWithHostPort (util.js:972:20) at Server._listen2 (net.js:1253:14) at listen (net.js:1289:10) at Server.listen (net.js:1385:5) at EventEmitter.listen (/opt/Rodeo/resources/app/node_modules/express/lib/application.js:617:24) at /opt/Rodeo/resources/app/node/services/server.js:16:9 at Promise._execute (/opt/Rodeo/resources/app/node_modules/bluebird/js/release/debuggability.js:272:9) at Promise._resolveFromExecutor (/opt/Rodeo/resources/app/node_modules/bluebird/js/release/promise.js:475:18) at new Promise (/opt/Rodeo/resources/app/node_modules/bluebird/js/release/promise.js:77:14) at Object.start (/opt/Rodeo/resources/app/node/services/server.js:13:10) at attachAppEvents (/opt/Rodeo/resources/app/node/index.js:782:34) at Object. (/opt/Rodeo/resources/app/node/index.js:811:1) at Module._compile (module.js:541:32) at Object.Module._extensions..js (module.js:550:10) at Module.load (module.js:456:32)

Contributor guide

Tech stack
nodejsexpresspython
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Node.js and Express knowledgeUnderstanding of port conflicts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the server startup in `/opt/Rodeo/resources/app/node/services/server.js` line 16. The issue is caused by port 9356 already in use. Consider adding error handling for EADDRINUSE (e.g., retry with a different port or prompt the user). Alternatively, make the port configurable via environment variable or command line argument. Check if any existing PRs address this (none linked). The fix is localized and the error is clear.