"meteor mongo" doesn't work on METEOR@1.1.0.1

[delgermurun]

After upgrading from 1.1 to 1.1.0.1, meteor mongo doesn't work. Here is command output:

mongo: Meteor isn't running a local MongoDB server.

This command only works while Meteor is running your application locally. Start your application first. (This error will also occur if you asked Meteor to use a
different MongoDB server with $MONGO_URL when you ran your application.)

If you're trying to connect to the database of an app you deployed with 'meteor deploy', specify your site's name with this command.

Obviously I started application locally.

Backward to 1.1, it works.

OS: Ubuntu 14.10 64-bit

[scamianbas]

Same issue here.

[hamoid]

Same on Arch Linux. But mongo --port 3001 does work.
I downgraded to 1.1 and meteor mongo was still not working.

[scamianbas]

Downgrade to 1.1 doesn't work here as well.
Ubuntu 14.04 64b

[hasiya]

who can we contact about this? Im currently working on my Honours project.. I really need this..

[hamoid]

@hasiya As I mentioned, you can install mongodb and use that to connect. Not ideal, but works.

[hamoid]

Aren't there tests that prevent this kind of issues getting released?

[glasser]

Due to a mistake with git during the preparation of 1.1, some code that was not intended to go into 1.1 (and did not go into 1.1!) was accidentally placed onto master in git. So 1.1.0.1 was accidentally prepared with that additional change. Unfortunately, while there is a test of this exact issue that was added as part of the change, the same git mistake didn't add the new test.

Folks who are having issues: can you tell me what type pgrep; echo $?; pgrep -lf mongod; echo $? prints?

[scamianbas]

@glasser
pgrep is hashed (/usr/bin/pgrep)
0
1008 mongod
0

[delgermurun]

@glasser

pgrep is /usr/bin/pgrep
0
1141 mongod
18509 mongod
0

[hamoid]

pgrep is /usr/bin/pgrep
0
7961 mongod
0

(I had to put the code in a bash script, because by default I run fishshell)

[glasser]

OK, thanks. Looks like in addition to the differences between pgrep implementations on Mac and Linux, there are multiple Linux versions, and they changed the implementation in 2012 according to http://serverfault.com/questions/77162/how-to-get-pgrep-to-display-full-process-info

Since 3.3.4 (released in 2012), pgrep -a (--list-full) shows the full command line
...
In older versions ... pgrep -fl matched the pattern against full command line and showed the full command line.

Ah, and here's the change: https://gitorious.org/procps/procps/commit/f12277c74d591245767d77badb6bb6af91335656

The Linux machine I tested this change on (which again, only went out in 1.1.0.1 due to a git mistake) had an older pgrep without this flag.

Sorry. This usually would have been caught during the RC stage or QA, but we do less QA on releases that are intended to only contain a single tiny change.

[delgermurun]

@glasser I forgive you :). You are doing great job.

[stubailo]

@hasiya you might be able to use meteor shell instead of meteor mongo for doing stuff with the database.

[glasser]

I've fixed the underlying bug on devel, and @stubailo is putting out a 1.1.0.2 that doesn't have the relevant change (which was never intended to be in 1.1.0.1 in the first place).

[ghost]

Waiting for 1.1.0.2

[glasser]

@stubailo What happened to the 1.1.0.2 release process? I see that the release exists but has not yet been marked as recommended.

[stubailo]

The fix has just been released in 1.1.0.2.

[skagedal]

Got the fix, works great!

[delgermurun]

Thank you.

[etangreal]

Hi, I'm getting this "Unexpected mongo exit code 1. Restarting."

Runtime:
- Ubuntu 14.04 (running on my mac via vagrant & virtualbox)
- meteor version 1.1.0.2

Instructions:

• vagrant init ubuntu/trusty64
• vagrant up
• vagrant ssh
• curl https://install.meteor.com/ | sh
• meteor create test
• cd test
• meteor update
• meteor --version (is 1.1.0.2)
• meteor

after which I get this "Unexpected mongo exit code 1. Restarting."
Have been searching - but not much to go on ...

[stefanve]

I also get this error with Ubuntu 14.04 LTS and meteor 1.1.0.2
It worked at first start, but after a reboot I get the error

[stubailo]

@etangreal - there is a problem with running Mongo on shared file systems like Vagrant. Here are some directions I found on Google about moving the db out of the shared folder: https://gist.github.com/gabrielhpugliese/5855677

[stubailo]

@stefanve are you also in vagrant? Can you provide more details?

[stefanve]

Well, I don't know... :) I use a Hetzner EX40SSD, default install Ubuntu 14.04 64-bit minimal.
I installed meteor and git stuff from command line, so I just did minimal changes to the default install
https://www.hetzner.de/en/hosting/produkte_rootserver/ex40ssd

Seems like 14.04 is a common denominator though?
#4019

[stefanve]

It is not possible to do a reset either:
home/stefan/.meteor/packages/meteor-tool/.1.1.3.4sddkj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
throw(ex);
^
Error: EACCES, unlink '/home/appname/.meteor/local/build-garbage-os0e3h/README'

[stubailo]

oh @stefanve did you create an app somewhere where you don't have delete permissions? try creating the app in your personal home directory rather than /home/appname.

[stefanve]

Sorry, deleted part of the path. It is in my home, /home/myname/appname
After deleting build-garbage-os0e3h dir, reset worked but Mongo still refuses to play

[stefanve]

Update on my issue: Vagrant was not involved. The server had two mirrored SSD disks. I uninstalled Meteor according to official instructions, removed my project and reinstalled from scratch after doing all the official 14.04 updates. Still did not work.
I then deployed the app properly with meteor-up and all went well.
So my immediate problem is solved, but the "Unexpected mongo exit code 1. Restarting." is still a mystery.

[nickgio]

I am still having the same issue with 1.1.0.2 - running Meteor locally, but still getting the same error:

mongo: Meteor isn't running a local MongoDB server.

This command only works while Meteor is running your application
locally. Start your application first. (This error will also occur if
you asked Meteor to use a different MongoDB server with $MONGO_URL
when you ran your application.)

If you're trying to connect to the database of an app you deployed
with 'meteor deploy', specify your site's name with this command.

[glasser]

Can we keep the discussion of "Unexpected mongo exit code 1. Restarting" on #4019? I'm not sure why it started here, after a completely unrelated bug was solved and closed.

[spradnyesh]

i'm still facing the issue w/

• meteor 1.2.1
• mongo 2.4.14

on debian testing