Thelounge: Lounge crashes when failing a DNS lookup
The 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! [email protected] start: `node index`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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 [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~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 [email protected]~start: CWD: /home/dusk/lounge
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node index' ]
12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] 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 [email protected]
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 [email protected] start: `node index`
22 error Exit status 1
23 error Failed at the [email protected] 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 ]
omnicons
All 16 comments
I just tried this, I can see the [DEBUG] IRC socket error (which is expected), but it did not crash, and the client is still running fine.
The crash in your log seems unrelated, and due to Error: connect ETIMEDOUT 54.244.255.81
However I tried connecting to something that has no IRC, and did not crash either, and just got a [DEBUG] IRC socket error { Error: connect ETIMEDOUT 93.184.216.34.
Can you try to reproduce this issue on latest master (make sure to run npm install)?
xPaw
on 28 May 2016
No no, I was only on 1.3 yesterday after I restarted it in tmux instead.
omnicons
on 28 May 2016
Yeah I deleted my comment right after posting it, realizing it had obvious 2.0.0 traits. My bad, sorry for the false alarm :)
maxpoulin64
on 28 May 2016
RE: Deleted comment; I was mistaken, as I submitted the comment Lounge crashed. It took it a good minute or so for it to die once I made it try to connect, to be clear this is a fresh install of 'master' having run 'npm install' and everything else seems to be relatively normal.
2016-06-01 11:32:09 [DEBUG] IRC socket error { Error: getaddrinfo ENOTFOUND irc.canternet.net irc.canternet.net:6697
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: 6697 }
events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 54.228.211.168:6009
at Object.exports._errnoException (util.js:953:11)
at exports._exceptionWithHostPort (util.js:976: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.2.0
npm ERR! npm v3.9.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `node index`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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 [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/dusk/lounge/node_modules/.bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
10 verbose lifecycle [email protected]~start: CWD: /home/dusk/lounge
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node index' ]
12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] 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 [email protected]
16 verbose cwd /home/dusk/lounge
17 error Linux 4.2.5-1-ARCH
I think you maybe using the wrong connection settings... possibly "irc.canternet.org" not .net?
morgzz
on 1 Jun 2016
Actually what I previously mentioned wouldn't make sense.
You had to have the correct settings as 54.244.255.81 maintained by canternet.org
canternet.net doesn't exist.
54.244.255.81 is from United States (US) in region North America
Input: 54.244.255.81
canonical name: chrysalis.canternet.org
Registered Domain: canternet.org
I'm guessing something possibly on their end is miss routing you to irc.canternet.net.
In your Stack Trace, see the bold below.
016-06-01 11:32:09 [DEBUG] IRC socket error { Error: getaddrinfo ENOTFOUND irc.canternet.net irc.canternet.net:6697
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup as oncomplete
code: 'ENOTFOUND',
errno: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'irc.canternet.net',
host: 'irc.canternet.net',
port: 6697 }
events.js:160
Admittedly I'm completely new to this project. I'm guessing this could have something to do with why it's crashing. Possibly a misconfigured load balancer on canternet's side.
morgzz
on 1 Jun 2016
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 [email protected]
wrote:
Actually what I previously mentioned wouldn't make sense.
I'm now guessing you had the correct settings as 54.244.255.81 maintained
by canternet.org54.244.255.81 is from United States (US) in region North America
Input: 54.244.255.81
canonical name: chrysalis.canternet.org
Registered Domain: canternet.orgI'm guessing something possibly on their end is miss routing you to
irc.canternet.net.In your Stack Trace, see the _bold_ below.
016-06-01 11:32:09 [DEBUG] IRC socket error { Error: getaddrinfo ENOTFOUND irc.canternet.net irc.canternet.net:6697
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup as oncomplete
code: 'ENOTFOUND',
errno: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'irc.canternet.net',
host: 'irc.canternet.net',
port: 6697 }
events.js:160Admittedly I'm completely new to this project. I'm guessing this could
have something to do with why it's crashing. Possibly a misconfigured load
balancer on canternet's side.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thelounge/lounge/issues/352#issuecomment-222978970,
or mute the thread
https://github.com/notifications/unsubscribe/AGtbL_ZbEniFPewwwJP5H9MXxkOUUEFMks5qHXymgaJpZM4IoD9m
.
omnicons
on 1 Jun 2016
I can't seem to reproduce either. I reproduced both stack traces, without a crash.
2016-06-05 00:33:10 [DEBUG] IRC socket error { Error: getaddrinfo ENOTFOUND irc.max-p.me irc.max-p.me:6667
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:79:26)
code: 'ENOTFOUND',
errno: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'irc.max-p.me',
host: 'irc.max-p.me',
port: 6667 }
2016-06-05 00:38:55 [DEBUG] IRC socket error { Error: connect ETIMEDOUT 167.114.206.88:6667
at Object.exports._errnoException (util.js:953:11)
at exports._exceptionWithHostPort (util.js:976:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
code: 'ETIMEDOUT',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '167.114.206.88',
port: 6667 }
Using npm 3.9.3 and node 6.2.0, fresh master install. Seems like an error is not caught somewhere where it should, but the stack trace doesn't point to any of our code at all. I would like to blame node itself for that, but considering I also run Arch and thus in theory the same packages, I should get the error too. But I don't.
I did manage to get this crash:
2016-06-05 00:56:11 [DEBUG] IRC socket error Error: write after end
at writeAfterEnd (_stream_writable.js:166:12)
at Socket.Writable.write (_stream_writable.js:217:5)
at Socket.write (net.js:650:40)
at Connection._write (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/connection.js:180:24)
at doWrite (_stream_writable.js:307:12)
at writeOrBuffer (_stream_writable.js:293:5)
at Connection.Writable.write (_stream_writable.js:220:11)
at IrcCommandHandler.handlers.PING (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handlers/misc.js:79:25)
at IrcCommandHandler.dispatch (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handler.js:49:37)
at IrcCommandHandler._write (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handler.js:35:10)
events.js:160
throw er; // Unhandled 'error' event
^
Error: write after end
at writeAfterEnd (_stream_writable.js:166:12)
at Socket.Writable.write (_stream_writable.js:217:5)
at Socket.write (net.js:650:40)
at Connection._write (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/connection.js:180:24)
at doWrite (_stream_writable.js:307:12)
at writeOrBuffer (_stream_writable.js:293:5)
at Connection.Writable.write (_stream_writable.js:220:11)
at IrcCommandHandler.handlers.PING (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handlers/misc.js:79:25)
at IrcCommandHandler.dispatch (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handler.js:49:37)
at IrcCommandHandler._write (/mnt/storage/max-p/Sync/remote/Projects/lounge/node_modules/irc-framework/src/commands/handler.js:35:10)
But it's the one @MaxLeiter is having, and unrelated to this issue.
maxpoulin64
on 5 Jun 2016
So, if we can't reproduce, shall we just throw some catcher around where it is being thrown and just leave it like that? It's obviously not ideal, but it'll be something, at least...
McInkay
on 4 Jul 2016
@YaManicKill, vectr0n hit this issue yesterday while debugging.
xPaw
on 4 Jul 2016
@xPaw Great, do we have more data then? Enough to know what is happening?
McInkay
on 4 Jul 2016
@YaManicKill somewhat.
xPaw
on 4 Jul 2016
Found the problem and fixed it: https://github.com/kiwiirc/irc-framework/pull/61
xPaw
on 4 Jul 2016
This issue will be resolved only when https://github.com/kiwiirc/irc-framework/pull/61 gets merged, makes it into a release and we pull that new version in our package.json.
astorije
on 20 Aug 2016
I am removing 2.0.0 milestone for now. If by any luck it gets released before we ship it, then we'll add it back, otherwise it will be for later. I am really willing to ship 2.0.0 in a matter of days now.
astorije
on 15 Sep 2016
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.
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
`
TuSuNaMi
on 12 May 2017
Related issues
zeten30
·
15Comments
McInkay
·
25Comments
ziyadparekh
·
22Comments
Jay2k1
·
24Comments
Komic
·
18Comments
Most helpful comment
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 [email protected]
wrote: