I would have been delighted for you to be right about that, but it doesn’t fix my situation, unfortunately.
I just started up a completely fresh Xubuntu Xenial virtual machine, installed git and meteor and tried again.
=> Started proxy.
… and …
=> Started MongoDB.
… it gets stuck doing …
Starting your app \
Is there something “wrong” with Xubuntu? with Qemu/KVM virtual machines?
Just tried for the heck of it and you’re right, any other port fails to start meteor server.
Truth is, most of us don’t care about dev port (this is why maybe no one noticed till now), as we set the port in production with PORT env variable.
meteor run --port 666
That is a devlishly ambiguous post. Beastly … one might say!
I like to run two sites simultaneously when comparing behavior of different bits of sample code and that sort of thing.
So, do I post an issue about it? or did you do that?
Oh and thanks so much for giving it a try.
I thought I had a very weird defect in my work environment.
I have the same issue on two different Ubuntu servers since the upgrade to Meteor 22.214.171.124.
Is there any workaround or fix about this issue you had ?
Or is there any opened issue on Meteor Github about that ?
I didn’t open an issue. I don’t know if anyone else did.
It is not a big concern for me. If you are having problems as a consequence you should report it.
imho, it is as much a bug in release testing as it is a run time bug. iow, seems all tests are done only on port 3000.
Okay, thanks for your answer.
I’ll post a detailled issue about that since a lot has been discovered since my post on gitter.
You could try running it with
METEOR_PROFILE=1 METEOR_LOG=debug meteor --verbose (source: Meteor stuck at starting your app)
Gee Willikers, @merlinpatt ! That actually worked !
But I had to do :
meteor reset METEOR_PROFILE=1 METEOR_LOG=debug meteor --verbose -p 3001
Ok that’s weird. I just tried
meteor reset on its own and . . .
. . . Bingo! It seems that that’s all that’s required if you want to switch ports.
( The other thread you cited had that suggestion. Thanks! )
I’m reviewing the issue right now, but I can see some obvious problems in this post:
- You cannot* run two different Meteor projects on 3000 and 3001 because Meteor uses
PORT+1for the Mongo server it uses. You should use ports that are further away from each other. (Personally, I use 3100, 3200, 3300, etc.)
* = Unless you use your own Mongo server with
MONGO_URL, which prevents starting a Mongo server on
- You cannot run two different versions of the same project from the same folder unless you specify a new
MONGO_LOCAL_DIRenvironment variable. (i.e.
MONGO_LOCAL_DIR=.meteor/local2 meteor --port 3600
I run multiple reproductions all day long (on Mac) and have not run into the problems you’re describing.
I did not try to run two at once. I tried to run on some other port than 3000.
As the thread subject, and my original post, states, " . . . I can run Meteor only out of port 3000".
The trick, to running on a different port, is to do
meteor reset before switching.
Thanks for the clarification - I’m just pointing out some potential problems due to some not-entirely-clear wording in the issue.
Anyhow, I’ve just confirmed that this is occurring on Ubuntu 14.04 – presumably other versions too, but I cannot get it to happen in Windows or OS X.
In regards to your other comments:
It’s a shame that you’re disappointed in the release testing. There are, in fact, tests in place to run the tool on different ports. I’m not entirely sure why those are passing but this problem still occurring, especially since they run in a CI environment that I’m almost entirely sure is Ubuntu. Hopefully this can be figured out!
If you have suggestions for better tests to prevent this in the future please do file issues and pull-requests accordingly. Also, involving yourself in public betas and filing issues is a great way to help identify these problems before they are officially released.
Thanks very much for stepping in and looking at this.
I’m not disappointed! In fact, I’m overwhelmed by the quality of the Meteor release process.
I was just pointing out a miniscule, apparent deficiency. I believe the test needs to start Meteor on port 3000, stop it, then try to start it again, specifying some other port. That seems to be the prerequisite for recreating the failure.
Ok, super clear understanding of the problem now, I swear! Confirmed on OS X and Ubuntu plus probably others. See issue for updates.
You are impressively thorough.
Thanks to those who reported this! This will be fixed in a future stable release of Meteor but is available in beta right now (specifically,
The beta channel isn’t always bug free and you may run into unrelated bugs, but if you’re in a position to test that this particular feature has been fixed for you, it would certainly be appreciated. You can find instructions for using the current beta release in https://github.com/meteor/meteor/pull/7668.
Please report back if you still have problems with this!
Also had this problem on OS X in Meteor 126.96.36.199
Fixed after updating to Meteor 1.4.2-beta.9