Can't publish new package: Error: socket hang up

philipmjohnson · January 6, 2016, 9:40pm

I am trying to publish a package to Atmosphere for the first time. I have tried four times this morning from both home and work to run meteor publish --create, and it fails every time with a socket hang up error. The stack trace indicates a timeout during login, so I tried logging in first just to make sure that works OK. Here is the log:

[~/github/radgrad/core/app/packages/radgrad-lib]-> meteor login
Username: philipmjohnson
Password:                                     
warning: couldn't confirm logout with www.meteor.com
                                              
Logged in as philipmjohnson. Thanks for being a Meteor developer!

[~/github/radgrad/core/app/packages/radgrad-lib]-> meteor publish --create
It looks like you have been logged out! Please log in with your Meteor developer account. If you don't have one, you can quickly create
one at www.meteor.com.
Username: philipmjohnson
Password:                                     
                                              
/Users/philipjohnson/.meteor/packages/meteor-tool/.1.1.10.1i6toil++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
						throw(ex);
						      ^
Error: socket hang up
    at Object.Future.wait (/Users/philipjohnson/.meteor/packages/meteor-tool/.1.1.10.1i6toil++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
    at Object._.extend.request (/tools/utils/http-helpers.js:275:20)
    at sendAuthorizeRequest (/tools/meteor-services/auth.js:342:32)
    at oauthFlow (/tools/meteor-services/auth.js:382:25)
    at Object.exports.loginWithTokenOrOAuth (/tools/meteor-services/auth.js:956:17)
    at Object.exports.loggedInConnection (/tools/meteor-services/auth-client.js:87:12)
    at Object.exports.loggedInPackagesConnection (/tools/packaging/package-client.js:232:21)
    at Command.main.registerCommand.name [as func] (/tools/cli/commands-packages.js:305:32)
    at /tools/cli/main.js:1378:23
    - - - - -
    at createHangUpError (http.js:1473:15)
    at CleartextStream.socketCloseListener (http.js:1523:23)
    at CleartextStream.emit (events.js:117:20)
    at tls.js:694:10

The package I am trying to publish is at the following repo:

https://github.com/radgrad/core/tree/master/app/packages/radgrad-lib

Thanks for any help you can provide.

dpankros · January 6, 2016, 10:02pm

I’m getting this too. Tried throughout the day. For a while I was getting "access denied’ errors too.

I’m glad I’m not the only one, but I’m frustrated by it at the same time.

chap · January 6, 2016, 10:18pm

I have exactly the same problem but unfortunately I don’t know why.

mjmcee · January 7, 2016, 12:47am

Same here, thought it was my works firewall so I tried it elsewhere and still no luck.

blueknightone · January 7, 2016, 12:48am

Ditto here as well. Here’s the error I get.

C:\Users\blueknightone\AppData\Local\.meteor\packages\meteor-tool\1.1.10\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fibers\future.js:278
                                                throw(ex);
                                                      ^
Error: socket hang up
    at Object.Future.wait (C:\Users\blueknightone\AppData\Local\.meteor\packages\meteor-tool\1.1.10\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fibers\future.js:398:15)
    at Object._.extend.request (C:\tools\utils\http-helpers.js:275:20)
    at sendAuthorizeRequest (C:\tools\meteor-services\auth.js:342:32)
    at oauthFlow (C:\tools\meteor-services\auth.js:382:25)
    at Object.exports.loginWithTokenOrOAuth (C:\tools\meteor-services\auth.js:956:17)
    at Object.exports.loggedInConnection (C:\tools\meteor-services\auth-client.js:71:10)
    at Object.exports.loggedInPackagesConnection (C:\tools\packaging\package-client.js:232:21)
    at Command.main.registerCommand.name [as func] (C:\tools\cli\commands-packages.js:305:32)
    at C:\tools\cli\main.js:1378:23
    - - - - -
    at createHangUpError (http.js:1473:15)
    at CleartextStream.socketCloseListener (http.js:1523:23)
    at CleartextStream.emit (events.js:117:20)
    at tls.js:694:10
    at process._tickCallback (node.js:448:13)

nobutakaoshiro · January 7, 2016, 3:00am

I met the same problem.

$ meteor publish --create

/Users/nobutaka/.meteor/packages/meteor-tool/.1.1.10.uivzpm++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
                                                throw(ex);
                                                      ^
Error: socket hang up
    at Object.Future.wait (/Users/nobutaka/.meteor/packages/meteor-tool/.1.1.10.uivzpm++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
    at Object._.extend.request (/tools/utils/http-helpers.js:275:20)
    at sendAuthorizeRequest (/tools/meteor-services/auth.js:342:32)
    at oauthFlow (/tools/meteor-services/auth.js:382:25)
    at Object.exports.loginWithTokenOrOAuth (/tools/meteor-services/auth.js:956:17)
    at Object.exports.loggedInConnection (/tools/meteor-services/auth-client.js:71:10)
    at Object.exports.loggedInPackagesConnection (/tools/packaging/package-client.js:232:21)
    at Command.main.registerCommand.name [as func] (/tools/cli/commands-packages.js:305:32)
    at /tools/cli/main.js:1378:23
    - - - - -
    at createHangUpError (http.js:1473:15)
    at CleartextStream.socketCloseListener (http.js:1523:23)
    at CleartextStream.emit (events.js:117:20)
    at tls.js:694:10
    at process._tickCallback (node.js:448:13)

I’m using OS X El Capitan (10.11.2).

$ meteor --version
Meteor 1.2.1
$ node --version
v0.12.8
$ npm --version
2.14.9

MickaelFM · January 7, 2016, 9:59am

Same here. Is the atmospherejs team aware of this problem ?

sparaker · January 7, 2016, 10:50am

Me too same problem.

dpankros · January 7, 2016, 2:12pm

Slightly older versions of npm and node, but same errors on the exact same lines as nobutakaoshiro.

> meteor --version
Meteor 1.2.1
> node --version
v0.12.5
> npm --version
2.11.2

I also tried meteor logout followed by meteor login and that didn’t help. Seeing that the error is in OAuth, I thought maybe it was caching some old data.

I’m updating node now.

Another point: I thought it might be a firewall or IDS issue, but I disabled both the firewall and snort to no avail. Bummer.

nomoadler · January 7, 2016, 2:51pm

I was able to meteor publish --create successfully yesterday afternoon, but right after that, when I tried meteor admin get-machine os.linux.x86_64 I started getting the socket hangups.

Hoping this gets fixed soon!

galushkinaleksey · January 7, 2016, 2:58pm

The same problem. Appeared today.

philipmjohnson · January 7, 2016, 4:30pm

OK, it’s clear it’s not just me, so I’ve created an issue on Atmosphere’s github repo. If anyone has any other ideas about how to communicate this problem to those who can fix it, please pursue them.

mokolodi1 · January 7, 2016, 6:34pm

Same problem here. I’m not trying to create a new package, just publish an update to an old one. (regular old meteor publish)

evaisse · January 7, 2016, 6:48pm

Same here

/Users/evaisse/.meteor/packages/meteor-tool/.1.1.10.1jktoiy++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
						throw(ex);
						      ^
Error: socket hang up

at Object.Future.wait (/Users/evaisse/.meteor/packages/meteor-tool/.1.1.10.1jktoiy++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
at Object._.extend.request (/tools/utils/http-helpers.js:275:20)
at sendAuthorizeRequest (/tools/meteor-services/auth.js:342:32)
at oauthFlow (/tools/meteor-services/auth.js:382:25)
at Object.exports.loginWithTokenOrOAuth (/tools/meteor-services/auth.js:956:17)
at Object.exports.loggedInConnection (/tools/meteor-services/auth-client.js:71:10)
at Object.exports.loggedInPackagesConnection (/tools/packaging/package-client.js:232:21)
at Command.main.registerCommand.name [as func] (/tools/cli/commands-packages.js:305:32)
at /tools/cli/main.js:1378:23

at createHangUpError (http.js:1473:15)
at CleartextStream.socketCloseListener (http.js:1523:23)
at CleartextStream.emit (events.js:117:20)
at tls.js:694:10
at process._tickCallback (node.js:448:13)

albertoguerere · January 7, 2016, 11:05pm

Reporting the same issue here.
First it was socket hang up, now it is this:

/Users/beto/.meteor/packages/meteor-tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245
						throw(ex);
						      ^
Error: access-denied
    at sendAuthorizeRequest (/tools/meteor-services/auth.js:351:11)
    at oauthFlow (/tools/meteor-services/auth.js:382:25)
    at Object.exports.loginWithTokenOrOAuth (/tools/meteor-services/auth.js:956:17)
    at Object.exports.loggedInConnection (/tools/meteor-services/auth-client.js:87:12)
    at Object.exports.loggedInPackagesConnection (/tools/packaging/package-client.js:232:21)
    at Command.main.registerCommand.name [as func] (/tools/cli/commands-packages.js:305:32)
    at /tools/cli/main.js:1378:23

Please Atmosphere fix this! We are trying to publish our very own first Meteor package!

philipmjohnson · January 7, 2016, 11:54pm

OK, so let’s try asking for help this way:

ekate · January 8, 2016, 12:05am

Thanks for the report. We are looking into it.

pcarrier · January 8, 2016, 4:17am

Sorry about that! The issue should be fixed now; please let us know if you still run into issues.

MickaelFM · January 8, 2016, 7:45am

Thanks, it’s fixed for me !
Have a good day everybody

nobutakaoshiro · January 8, 2016, 7:54am

I was able to publish my package to Atmosphere. Thanks!