[SERVER-2041] mongod service doesn't start correctly after update Created: 30/Oct/10 Updated: 30/Mar/12 Resolved: 17/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mars Cheng | Assignee: | Richard Kreuter (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ubuntu 10.04 32bit desktop |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
The mongo-stable package is updated so frequently. I try to catch up as the following sudo apt-get upgrade The mongod supposed to start after I update the mongo-stable. However, I cannot connect it with mongo, the shell. I have to start it manually, which totally sucks. After that it can work. I advise that you should build a smoke test to verify if the package is good. It's easy to do that, install the package on the target machine, and then run mongo to check if it can connect the server correctly. At least the package should pass this verification, and then it can be deliveried. This bug lasts from 1.6.0. And moreover it's really annoying. |
| Comments |
| Comment by auto [ 25/Apr/11 ] |
|
Author: {u'login': u'kreuter', u'name': u'Richard Kreuter', u'email': u'richard@10gen.com'}Message: Wait 300s for server shutdown in deb initscripts. Re: |
| Comment by auto [ 25/Apr/11 ] |
|
Author: {u'login': u'kreuter', u'name': u'Richard Kreuter', u'email': u'richard@10gen.com'}Message: Wait 300s for server shutdown in deb initscripts. Re: |
| Comment by Mars Cheng [ 23/Mar/11 ] |
|
I have got the reason. Mongo went down for some reasons, and after that it needs to repair. There are no messages to the admin. Therefore admin have no idea about that. When applications failed to connect, the admin tried to start it manually. it would be ok if the admin started with no arguments, because it will use another database by default. The admin try to start the service mongodb, and everything seems ok. however it cannot start. the admin will find this issue until he/she checks the log. |
| Comment by Richard Kreuter (Inactive) [ 17/Mar/11 ] |
|
I've never been able to reproduce this issue, but just thought up a way that it might be a timing bug in the initscripts. I've changed the relevant init scripts; please let us know if this issue recurs. |
| Comment by auto [ 17/Mar/11 ] |
|
Author: {u'login': u'kreuter', u'name': u'Richard Kreuter', u'email': u'richard@10gen.com'}Message: Wait 300s for server shutdown in deb initscripts. Re: |
| Comment by auto [ 17/Mar/11 ] |
|
Author: {u'login': u'kreuter', u'name': u'Richard Kreuter', u'email': u'richard@10gen.com'}Message: Wait 300s for server shutdown in deb initscripts. Re: |