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

iron mongo hanging at "connecting to" #136

Closed
seangrogg opened this issue Mar 31, 2015 · 17 comments
Closed

iron mongo hanging at "connecting to" #136

seangrogg opened this issue Mar 31, 2015 · 17 comments

Comments

@seangrogg
Copy link

Currently trying to use "$iron mongo" to access a collection; I appear to be hanging at "connecting to: 127.0.0.1/meteor". When I run the application through meteor itself, using "$meteor mongo" the collection connects just fine.

@chrisbutler
Copy link
Contributor

noticed this also

@shails
Copy link

shails commented Apr 18, 2015

I am having the same issue with iron mongo command hangs on
connecting to: 127.0.0.1:3001/meteor

@nerdy-sam
Copy link

Confirmed OSX 10.10, Meteor 1.1.0.2, Iron 1.1.2

I think the problem is here somewhere maybe...
https://github.com/iron-meteor/iron-cli/blob/master/lib/tools/meteor.js#L160

@therinken
Copy link

No connection to mongo, yet. Same issue... just hangs without resolve

[osx-10.10.3/node-0.12.1/zsh-5.0.5/meteor-1.1.0.2/iron-1.1.2]

@connor11528
Copy link

same issue. any update? I can get it going by cd app and then meteor mongo

@ghost
Copy link

ghost commented Jun 15, 2015

+1 same issue here. If you cd app then meteor mongo it connects ok.

@jLouzado
Copy link
Contributor

jLouzado commented Jul 3, 2015

I'm getting the same error with iron mongo.

Unfortunately the meteor mongo is also failing with error message:

mongo: You're not in a Meteor project directory.

@chrisbutler
Copy link
Contributor

@Mitzip any ideas for how to fix this?

@josephdburdick
Copy link
Contributor

This might be a crazy idea but should there be a way to just pass the normal command into the .meteor child directory if the command is not found in Iron's list of commands as some sort of main catch-all fallback?

It just seems like about half the issues I see with Iron is that Iron doesn't recognize a baked-in meteor command. These commands should be tried by Meteor as a last resort.

@chrisbutler
Copy link
Contributor

@josephdburdick i think that's the general idea, and what currently happens in the code

the issue with mongo is that it creates an interactive shell, which is different than just passing back the output from a command

@josephdburdick
Copy link
Contributor

Ohh, I understand the scale of complexity now. Thanks for clearing that up, @chrisbutler.

@jchan202
Copy link

I just started using iron-cli, and ran into the same issue. So I installed MongoDB, and connected using:
mongo 127.0.0.1:3001/meteor

@jLouzado
Copy link
Contributor

@jchan202 but it's not affecting your app's functionality right?

@jchan202
Copy link

@jLouzado I don't notice any 'side effect' so far.

@jLouzado
Copy link
Contributor

just realized that the solution was listed several months months ago... cd app/ and then run meteor mongo

chrisbutler pushed a commit that referenced this issue Jan 27, 2016

Verified

This commit was signed with the committer’s verified signature.
navidemad Navid EMAD
Update README.md regarding issue #136
chrisbutler added a commit that referenced this issue Jan 12, 2017

Verified

This commit was signed with the committer’s verified signature.
navidemad Navid EMAD
@chrisbutler
Copy link
Contributor

@kuba-04
Copy link

kuba-04 commented Oct 16, 2017

Do you mean this directory? /.meteor/local/build/programs/server/app ?
I can't find any other app/ folder. Anyway this one doesn't work for me, still have the same issue.
Did it work for everyone here?

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

10 participants