[1.4] New & existing projects cannot be run after update

[TimeBandit]

Meteor updates to latest release after which projects exit with error when running meteor command. Same is seen when new a project is created using meteor create 1-4-update-fail

Error seen:

=> Started proxy.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Can't start Mongo server.
MongoDB had an unspecified uncaught exception.
This can be caused by MongoDB being unable to write to a local database.
Check that you have permissions to write to .meteor/local. MongoDB does
not support filesystems like NFS that do not allow file locking.

Initial Conditions

System

Disk Usage

File System

Observations

1. The automatic update repeated a few times and I hung once at which point I Ctrl^c out of it.

Things I’ve Tried

1. meteor update.
2. meteor reset
3. meteor --version 1.4 output 1.4
4. Ran export LC_ALL="en_US.UTF-8" command before meteor command as per this SO article.
5. Tried removing .meteor/local/db/mongod.lock as per this SO article but the file does not exist. Actually the db folder is empty with a new clean project.
6. A fresh install of meteor using curl https://install.meteor.com/ | sh

Reproduction

This issue is seen when creating a new project under 1.4. I have created a git repo. https://github.com/TimeBandit/meteor-1-4-update-fail

[palbergstrom]

Same problem.

[DerMarcus]

Same problem as well

[jeffcutten]

Same here.

[TimeBandit]

~/.meteor/dev_bundle does not exist in a new clean project. Deletion
of ~/.meteor/local had no effect, reported error still seen.

On 28/07/16 20:43, Derek Brown wrote:

Try removing ~/.meteor/dev_bundle and ~/.meteor/local and attempt to restart. Does this work?

---

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#7511 (comment)

[massimilianomarini]

Good to know I'm not the only with a 32bit and experiencing the same problem! :)

[tmeasday]

Confirmed, apologies for this folks.

[tmeasday]

The error message is

2016-07-29T02:44:20.826+0000 I STORAGE  [initandlisten] exception in initAndListen: 28663 Cannot start server. The default storage engine 'wiredTiger' is not available with this build of mongod. Please specify a different storage engine explicitly, e.g. --storageEngine=mmapv1., terminating

---

So a workaround for the problem:

1. When updating, don't migrate your database from mmapv1 (this means you can't meteor reset either).
2. If you want to create a new app, start with a 1.3 app and then update, respecting 1.

I'm looking into a proper fix.