Lounge crashes when failing a DNS lookup
See original GitHub issueThe logs from the crash and the stack trace below:
2016-05-26 22:35:12 [DEBUG] IRC socket error { Error: getaddrinfo ENOTFOUND irc.canternet.net irc.canternet.net:6009
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:79:26)
code: 'ENOTFOUND',
errno: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'irc.canternet.net',
host: 'irc.canternet.net',
port: 6009 }
events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 54.244.255.81:6009
at Object.exports._errnoException (util.js:949:11)
at exports._exceptionWithHostPort (util.js:972:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
npm ERR! Linux 4.2.5-1-ARCH
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v6.1.0
npm ERR! npm v3.9.0
npm ERR! code ELIFECYCLE
npm ERR! thelounge@2.0.0-pre.1 start: `node index`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the thelounge@2.0.0-pre.1 start script 'node index'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the thelounge package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node index
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs thelounge
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls thelounge
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/dusk/lounge/npm-debug.log
NPM-DEBUG.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@3.9.0
3 info using node@v6.1.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle thelounge@2.0.0-pre.1~prestart: thelounge@2.0.0-pre.1
6 silly lifecycle thelounge@2.0.0-pre.1~prestart: no script for prestart, continuing
7 info lifecycle thelounge@2.0.0-pre.1~start: thelounge@2.0.0-pre.1
8 verbose lifecycle thelounge@2.0.0-pre.1~start: unsafe-perm in lifecycle true
9 verbose lifecycle thelounge@2.0.0-pre.1~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/dusk/lounge/node_modules/.bin:/usr/bin:/usr/local/sbin:/u$
10 verbose lifecycle thelounge@2.0.0-pre.1~start: CWD: /home/dusk/lounge
11 silly lifecycle thelounge@2.0.0-pre.1~start: Args: [ '-c', 'node index' ]
12 silly lifecycle thelounge@2.0.0-pre.1~start: Returned: code: 1 signal: null
13 info lifecycle thelounge@2.0.0-pre.1~start: Failed to exec start script
14 verbose stack Error: thelounge@2.0.0-pre.1 start: `node index`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:245:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:850:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid thelounge@2.0.0-pre.1
16 verbose cwd /home/dusk/lounge
17 error Linux 4.2.5-1-ARCH
18 error argv "/usr/bin/node" "/usr/bin/npm" "start"
19 error node v6.1.0
20 error npm v3.9.0
21 error code ELIFECYCLE
22 error thelounge@2.0.0-pre.1 start: `node index`
22 error Exit status 1
23 error Failed at the thelounge@2.0.0-pre.1 start script 'node index'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the thelounge package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node index
23 error You can get information on how to open an issue for this project with:
23 error npm bugs thelounge
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls thelounge
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
Identifying and Troubleshooting DNS Issues - N-able
See the steps on how to troubleshoot DNS issues and the first place you should go when you need to diagnose DNS issues...
Read more >DNS server logs event 7062 - Windows Server | Microsoft Learn
In this article. Symptoms; Cause; Resolution; More information. This article provides a solution to solve the DNS server logs event 7062.
Read more >How To Resolve DNS Issues | HP® Tech Takes
Often, connectivity problems are related to DNS issues. ... Type “cmd” in the Windows Start Search bar, and select Open Command Prompt.
Read more >How to Fix "DNS Lookup Failed" (And DHCP) Errors on ...
The first step is to verify that your connection is active. Check your local network on a different device and see if you...
Read more >TC7.3.0 codec fails after reset and power cycle - failed: dns ...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh I know, but the application should not crash upon a failed connection. That interrupts service for everyone.It’s not desirable to have an application crash due to a simple mistake that could happen to anyone.
On Wed, Jun 1, 2016 at 8:35 AM, Adam Morgan notifications@github.com wrote:
Hello
Version 2.2 give simillar error,
`dns.js:239 if (err) throw errnoException(err, bindingName); ^
Error: getHostByAddr EINVAL at Object.exports._errnoException (util.js:1018:11) at errnoException (dns.js:33:15) at Object.query [as reverse] (dns.js:239:20) at reverseDnsLookup (/usr/lib/node_modules/thelounge/src/server.js:258:6) at Socket.auth (/usr/lib/node_modules/thelounge/src/server.js:329:4) at Namespace.<anonymous> (/usr/lib/node_modules/thelounge/src/server.js:78:9) at emitOne (events.js:96:13) at Namespace.emit (events.js:188:7) at Namespace.emit (/usr/lib/node_modules/thelounge/node_modules/socket.io/lib/namespace.js:209:10) at /usr/lib/node_modules/thelounge/node_modules/socket.io/lib/namespace.js:176:14 `