diff options
| author | Will Kahn-Greene <willg@bluesock.org> | 2011-05-07 09:56:39 -0400 |
|---|---|---|
| committer | Will Kahn-Greene <willg@bluesock.org> | 2011-05-07 09:57:02 -0400 |
| commit | 2704f7a6cbe274b5d1969d511564f928e0ba5d29 (patch) | |
| tree | e82d2e3da680df3882103845f648f23fa979a31a | |
| parent | 7501000353ed20eda9b2b32e9a0aba63df88f1b5 (diff) | |
| download | mediagoblin-2704f7a6cbe274b5d1969d511564f928e0ba5d29.tar.lz mediagoblin-2704f7a6cbe274b5d1969d511564f928e0ba5d29.tar.xz mediagoblin-2704f7a6cbe274b5d1969d511564f928e0ba5d29.zip | |
Tweaks the "if mongodb isn't working" troubleshooting section
| -rw-r--r-- | docs/hackinghowto.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/hackinghowto.rst b/docs/hackinghowto.rst index 2e6d0d14..dcade418 100644 --- a/docs/hackinghowto.rst +++ b/docs/hackinghowto.rst @@ -258,6 +258,12 @@ If you see this:: then make sure mongodb is installed and running. +If it's installed, check the mongodb log. On my machine, that's ``/var/log/mongodb/mongodb.log``. If you see something like:: + + old lock file: /var/lib/mongodb/mongod.lock. probably means... + +Then delete the lock file and relaunch mongodb. + Wiping your user data ===================== |