Closed
Description
Uh... Why is this error happening? I did not even upgrade any of my Meteor apps at all. Why would this shell flow control be getting hit when I haven't even updated to the new version? This must have come up as a result of you pushing out this latest build.
Anyway, running this:
meteor run --unsafe-perm --port 3002
Does not fix the issue, and it's because I'm running an old version of Meteor and all I get is this:
You have run Meteor as root. Your permissions in your app directory will be incorrect if you ever attempt to perform any Meteor tasks
as your non-root user. You probably didn't want this, but you can fix it by running the following from the root of your project:
sudo chown -Rh <username> .meteor/local
--unsafe-perm: unknown option.
Usage: meteor run [target..] [options]
Searches upward from the current directory for the root directory of a
Meteor project, then runs that project in local development
mode. You can use the application by pointing your web browser at
localhost:3000. No internet connection is required.
Whenever you change any of the application's source files, the changes
are automatically detected and applied to the running application.
The application's database persists between runs. It's stored under
the .meteor directory in the root of the project.
If you have added a platform to your app with 'meteor add-platform', you can
pass one of the following targets as an argument to this command.
Targets:
android Run on the Android emulator.
android-device Run on a connected Android device.
ios Run on the iOS simulator.
ios-device Open Xcode with the iOS project for this app, where you can
run your app on a connected iOS device.
Options:
--port, -p Port to listen on (instead of the default 3000). Also
uses port N+1 and a port specified by --app-port.
Specify as --port=host:port to bind to a specific interface.
--debug-port Specify a port to enable server-side debugging. The
server will be paused at startup, waiting for incoming
connections from debugger clients on the specified port.
--mobile-server Location where mobile builds connect to the Meteor server.
Defaults to your local IP and the port that the Meteor
server binds to. Can include a URL scheme (for
example, --mobile-server=https://example.com:443).
--production Simulate production mode. Minify and bundle CSS and JS files.
--raw-logs Run without parsing logs from stdout and stderr.
--settings Set optional data for Meteor.settings on the server.
--release Specify the release of Meteor to use.
--verbose Print all output from builds logs.
--no-lint Don't run linters used by the app on every rebuild.
--allow-incompatible-update Allow packages in your project to be upgraded or
downgraded to versions that are potentially incompatible with
the current versions, if required to satisfy all package
version constraints.
--test [Experimental] Run Velocity tests using phantomjs and exit.
I know I shouldn't be running as root, but this just so happened to be the dev server I'm building in and don't have the flexibility to set up users on this server.
There seems to be some hijacking of the old Meteor versions in my server as a result of your update.