[SERVER-2176] mongod does not start after package upgrade - misleading error messages!! Created: 06/Dec/10 Updated: 21/Feb/12 Resolved: 15/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tilo S | Assignee: | Michael A. Fiedler |
| Resolution: | Done | Votes: | 0 |
| Labels: | packaging | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Fedora 13 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Environment: Fedora 13 + mongo-stable-server == 1.6.4 Symptom: /etc/init.d/mongod does not start the server after upgrading package via 'yum update mongod-stable-server' Cause: all files under the $dbpath have "root" ownership - mongod bails out during start-up and does not report it correctly BUG DESCRIPTION: there are two problems associated with this bug: Problem1) Problem2) 1) /var/log/mongod.log just mentions that mongod.lock file is still there.. this is pretty mis-leading! Tue Nov 23 16:19:40 MongoDB starting : pid=1818 port=63336 dbpath=/data/mongo/db 64-bit
Tue Nov 23 16:19:40 shutdown: going to close listening sockets... 2) "/etc/inid.d/mongod status" merely says: same thing.. misleading / not pointing to the root cause - It should at least say: "check /var/log/mongod.conf for more information" |
| Comments |
| Comment by Michael A. Fiedler [ 21/Feb/12 ] |
|
Doc update request submitted, closing issue. |
| Comment by Michael A. Fiedler [ 15/Feb/12 ] |
|
I have confirmed that the startup behavior of the current packages is as desired, along with retaining the correct permissions between package upgrades. I believe the only problem remaining would be to have the "repair" documentation updated to reflect verifying that permissions are preserved post-repair. |
| Comment by Tilo S [ 02/Apr/11 ] |
|
this also happens by accident sometimes when a user does a 'mongod --repair' as root, and then forgets to do a 'chown -R mongod:mongod $dbpath' |
| Comment by Tilo S [ 06/Dec/10 ] |
|
I marked the bug as major, because this will silently affect running mongod systems in production!!! [beware!] e.g. long time after the 'yum update' , when the system reboots the next time, mongod will fail to start up.. This could severely break production systems which use mongod |
| Comment by Tilo S [ 06/Dec/10 ] |
|
forgot to mention: I had the exact same problem on two FC13 desktop systems, as well as three FC13 Linodes after upgrading to the latest stable mongod (=1.6.4) one can assume that this affects all linux upgrades |