Deployd won't start under MacOS X ML 10.8.1

[dseredinov]

Hey guys!

As mentioned in twitter (@DmitrySeredinov), here is a console log:

[dals@Dals-Mac-mini deployd-projects]$ DEBUG=* dpd create foo-world -d
starting deployd v0.6.7...
  mongod starting mongod +0ms
  mongod all output going to: /usr/local/var/log/mongodb/mongo.log
 +857ms

That's all. Nothing more is happens.
Tail of mongod log below:

[dals@Dals-Mac-mini deployd-projects]$ tail -F /usr/local/var/log/mongodb/mongo.log
Thu Oct 25 11:57:26 [initandlisten] MongoDB starting : pid=73136 port=4426 dbpath=./data 64-bit host=Dals-Mac-mini.local
Thu Oct 25 11:57:26 [initandlisten] 
Thu Oct 25 11:57:26 [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000
Thu Oct 25 11:57:26 [initandlisten] db version v2.2.0, pdfile version 4.5
Thu Oct 25 11:57:26 [initandlisten] git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207
Thu Oct 25 11:57:26 [initandlisten] build info: Darwin bs-osx-106-x86-64-1.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_49
Thu Oct 25 11:57:26 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/usr/local/etc/mongod.conf", dbpath: "./data", logappend: "true", logpath: "/usr/local/var/log/mongodb/mongo.log", nojournal: true, pidfilepath: "./.dpd/pids/mongod", port: 4426 }
Thu Oct 25 11:57:26 [initandlisten] Unable to check for journal files due to: boost::filesystem::basic_directory_iterator constructor: No such file or directory: "./data/journal"
Thu Oct 25 11:57:26 [websvr] admin web console waiting for connections on port 5426
Thu Oct 25 11:57:26 [initandlisten] waiting for connections on port 4426

System information:

• OS: MacOS X Mountain Lion 10.8.1, build 12B19 on Intel Core i5 CPU, 8 GB RAM.
• MongoDB (db version v2.2.0, pdfile version 4.5) installed with Homebrew
• Deployd installed with
  • npm directly (v0.6.6)
  • git clone -> npm install -> npm link (v.0.6.7)

For both versions of Deployd I've got the same issue as mentioned above: eternal 'starting deployd...' w/o errors, w/o web dashboard etc.

Thanks for reply on Twitter.

[ritch]

We haven't been testing with mongod 2.2.x. There might be an issue there. It looks like its an issue with our mongod loader. Can you try the following?

In a terminal tab:

mongod

In a separate tab (in your foo-world dir):

dpd -P 27017 -H localhost -n testing-deployd -d

If this works, it is certainly the mongod loader. Should be a quick fix.

[dseredinov]

It works, sir! Thanks!

[MariusCiocanel]

Using mongod 2.2.2 on OSX ML 10.8.2 and having the same issue.
I get the starting deployd v0.6.10... line but nothing happens after that.

The instructions ritch posted worked though..

[ritch]

@MariusCiocanel can you post the result of:

DEBUG=* dpd

[MariusCiocanel]

I get this and then nothing else happens:
starting deployd v0.6.10... mongod starting mongod +0ms mongod pid 1586 +60ms mongod all output going to: /usr/local/var/log/mongodb/mongo.log +143ms

Here's the contents of the mongo.log file:
Wed Feb 6 01:21:38 [initandlisten] MongoDB starting : pid=4198 port=7730 dbpath=./data 64-bit host=Marius-Ciocanels-MacBook-Pro.local Wed Feb 6 01:21:38 [initandlisten] Wed Feb 6 01:21:38 [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000 Wed Feb 6 01:21:38 [initandlisten] db version v2.2.2, pdfile version 4.5 Wed Feb 6 01:21:38 [initandlisten] git version: d1b43b61a5308c4ad0679d34b262c5af9d664267 Wed Feb 6 01:21:38 [initandlisten] build info: Darwin bs-osx-106-x86-64-1.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_49 Wed Feb 6 01:21:38 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/usr/local/etc/mongod.conf", dbpath: "./data", logappend: "true", logpath: "/usr/local/var/log/mongodb/mongo.log", nojournal: true, nssize: 4, pidfilepath: "./.dpd/pids/mongod", port: 7730, smallfiles: true } Wed Feb 6 01:21:38 [initandlisten] Unable to check for journal files due to: boost::filesystem::basic_directory_iterator constructor: No such file or directory: "./data/journal" Wed Feb 6 01:21:38 [websvr] admin web console waiting for connections on port 8730 Wed Feb 6 01:21:38 [initandlisten] waiting for connections on port 7730

[rsskga]

Having the same issue. When I run dpd -d, a mongod.lock file gets created in the /data directory. Launching with dpd -P 27017 -H localhost -n {project-name} -d also works for me, and no lock file is created.

[jxhn]

I encounter the same issue on Mac OS X Lion 10.7.5 so it's not specific to Mountain Lion anyway. It works fine doing the workaround above.

[zahlenhelfer]

Hi Guy, I encounter the same issue under Mac OS X Lion. With the Workaround of starting mongod in a seperate terminal it works like charm :)

[sebdeckers]

👍 New Deployd user here. This bug is still happening, workaround still works.

$ mongod --version
db version v2.4.0
Sun Mar 24 12:47:37.628 git version: ce2d666c04b4a80af58e8bbb3388b0680e8cfeb6
$ node --version
v0.8.19
$ npm --version
1.2.10
$ dpd --version
0.6.10
$ sw_vers -productVersion
10.8.3

[beshkenadze]

Yep. I encounter the same issue to on 10.8.3.

[utunga]

just another me too that I encountered this same problem. If I ran dpd then..

$ dpd -d
starting deployd v0.6.10...

.. and it would just hang indefinitely.

I'm also on mountain lion. The workaround described above namely starting mongod as a seperate process then running dpd as
$ dpd -P 27017 -H localhost -n newdb -d
also works for me. I installed from npm then when that didn't work tried installing from source download.

Taking a note out of cbas book here's all my version info.

$ node --version
v0.8.22
$ npm --version
1.2.14
$ dpd --version
0.6.10
$ sw_vers -productVersion
10.8.3

[Militia]

Any fix that does not have to be manually done?

[Sharondio]

Ran into this one...hard. The manual fix works, but I was hoping for an automated solution.

[utunga]

seriously guys *and gals, not starting up at all is not a good experience for first time developers you might want to fix this one

[eisisig]

Ditto

[KingScooty]

Any fix for this yet? I moved from the installer to the npm package for easier upgrading, and have just come across this issue. Bit of a pain in the arse having to manually load dpd.

[mauricesvay]

Voting up 👍

[dtrillian]

Same error here, your manual fix work but you should fix this for new users

[Neppord]

Great project.

But no error message?! Please fix at least that. And a link to this issue in that message would at least be a first aid.

That the experience differ this mouth between different installations is not good.

If you point me to what file to edit then I will make a pull request at least for the error message.

[NicolasRitouet]

We improved a bit the error message with this PR #434

[NicolasRitouet]

I'll close this since we improved the error handling and we have a new mongodb client (which should be more stable).
If necessary, after the 0.8 release, we can reopen this and keep improvement error messages.