The day has come that Meteor suddenly didn’t work…
=> Started proxy.
=> A patch (Meteor 22.214.171.124) for your current release is available!
Update this project now with 'meteor update --patch'.
Starting your app
Hangs forever and ever and ever…
So I tried to install the patch
meteor update --patch
Unable to update package catalog (are you offline?)
If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY environment variables or see this page for more details:
Sorry, Meteor 126.96.36.199 is not installed and could not be downloaded. Please check to make sure that you are online.
Yeah, sure I’m offline. That’s why I’m able to post this
Checking http://status.meteor.com/ All systems are operational…uhmmmmm
Nothing changed from my site today. What’s going on Meteor / @sashko?
Running Meteor works again for me. Patch still hangs.
You can generally get some information on the Meteor github page:
Reverted #8213 as the change was deemed too significant for this release.
Note: The decision to revert the above change was made late in the Meteor 188.8.131.52 release process, before it was ever recommended but too late in the process to avoid the additional increment of the version number. See #8311 for additional information. This change will still be released in an upcoming version of Meteor with a more seamless upgrade.
I’m inclined to believe that this must be related to a (temporary?) connectivity issue with the package server. We certainly updated a number of applications to Meteor 184.108.40.206 before officially recommending it and didn’t encounter any problems.
Things to remember:
If your proxy blocks websockets, this could cause a problem as Meteor uses its DDP protocol to speak with the package server to find information about upgrades. Check your WebSocket abilities by going to this site and pressing the “Connect” button. You should see a message which says “CONNECTED” in the “Log”.
The meteor-tool is over 100MB so Downloading can actually take some time if you’re on a slow connection
If you’re getting Unable to update package catalog adding the --verbose flag to the meteor update command could provide additional information about why the connection failed.
If you’re getting anything besides Unable to update package catalog, please give the specific output of your error where possible!
@oliverlloyd It sounds like you’re definitely experiencing a different error than this issue was originally referring to? See my last bullet point above.
@Siyfion Are you getting the message originally reported in this thread or something else entirely?
I noticed that 220.127.116.11 was taking an inordinate amount of time to update (I killed and restarted it a couple of times). Then while it was downloading I took a look at the task manager and was reminded that on Windows the antimalware process swamps the CPU and slows the extraction of the data considerably.
Finally, I just waited ~20 min and it all worked out.
Meteor Update Tip: as an optimization…
I recommend doing a meteor create newproject as a way to install the new builds. It is a minimum project and it is mostly about installing the new version of meteor on my machine. I have never had a problem installing new versions when I do it for a new project.
I have found in the past that doing a meteor update on my larger projects before meteor-tool is loaded on my machine can get a little tangled up and throw weird errors that turn out to not be true.
If this is an approach that you want to take, another option would be to just run meteor --release <new-version-number> --help, which in the same manner, will actually ONLY install the new version of the meteor-tool on your machine and not make any changes to the project itself.