Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update to node 0.12 hubot will no longer start #155

Closed
khera opened this issue Feb 12, 2015 · 3 comments
Closed

update to node 0.12 hubot will no longer start #155

khera opened this issue Feb 12, 2015 · 3 comments

Comments

@khera
Copy link

khera commented Feb 12, 2015

Today I updated node from 0.10.35 to 0.12.0. Restart of the hubot results in the following error. I did a manual npm update in the hubot home directory, and it rebuilt a lot of stuff. I also did a force reinstall of the slack integration using npm install hubot-slack --save yet the error persists.

Running Node 0.12.0, npm 2.2.0, hubot-slack updated to latest release. All on FreeBSD 10.1.

2015-02-12 15:53:40.551898500 Thu, 12 Feb 2015 20:53:40 GMT connect deprecated multipart: use parser (multiparty, busboy, formidable) npm module instead at node_modules/hubot/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:56:20
2015-02-12 15:53:40.552746500 Thu, 12 Feb 2015 20:53:40 GMT connect deprecated limit: Restrict request size at location of read at node_modules/hubot/node_modules/express/node_modules/connect/lib/middleware/multipart.js:86:15
2015-02-12 15:53:40.703328500 [Thu Feb 12 2015 15:53:40 GMT-0500 (EST)] INFO Connecting...
2015-02-12 15:53:40.722137500 [Thu Feb 12 2015 15:53:40 GMT-0500 (EST)] ERROR Received error EAI_BADFLAGS
2015-02-12 15:53:40.722590500 [Thu Feb 12 2015 15:53:40 GMT-0500 (EST)] ERROR undefined
2015-02-12 15:53:40.722630500 [Thu Feb 12 2015 15:53:40 GMT-0500 (EST)] ERROR Exiting in 1 second
2015-02-12 15:53:40.724862500 [Thu Feb 12 2015 15:53:40 GMT-0500 (EST)] ERROR TypeError: Cannot read property 'close' of null
2015-02-12 15:53:40.724863500   at Client.reconnect (/u/lorax1/home/hubot/hal/node_modules/hubot-slack/node_modules/slack-client/src/client.js:187:12)
2015-02-12 15:53:40.724864500   at Client._onLogin (/u/lorax1/home/hubot/hal/node_modules/hubot-slack/node_modules/slack-client/src/client.js:77:23)
2015-02-12 15:53:40.724866500   at /u/lorax1/home/hubot/hal/node_modules/hubot-slack/node_modules/slack-client/src/client.js:2:59
2015-02-12 15:53:40.724871500   at ClientRequest.<anonymous> (/u/lorax1/home/hubot/hal/node_modules/hubot-slack/node_modules/slack-client/src/client.js:638:18)
2015-02-12 15:53:40.724872500   at ClientRequest.emit (events.js:107:17)
2015-02-12 15:53:40.724873500   at TLSSocket.socketErrorListener (_http_client.js:272:9)
2015-02-12 15:53:40.724874500   at TLSSocket.emit (events.js:129:20)
2015-02-12 15:53:40.724874500   at net.js:923:16
2015-02-12 15:53:40.724877500   at process._tickCallback (node.js:355:11)
2015-02-12 15:53:40.724877500
@khera
Copy link
Author

khera commented Feb 12, 2015

Seems to be a known issue with Node: nodejs/node-v0.x-archive#8540

@evansolomon
Copy link
Contributor

From the discussion on joyent/node it sounds like this is a Node core and/or FreeBSD bug, so I'm guessing we can't do much about it here.

Does that sound right? If so, it's probably best to close this issue since it's really just a symptom of the other one(s).

Let me know if I'm missing anything though.

@khera
Copy link
Author

khera commented Feb 13, 2015

I agree with your assessment. For now I backed down to node 0.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants