[SERVER-3280] rpm/init.d-mongod is not able to stop mongod on Centos/Redhat 5 Created: 17/Jun/11 Updated: 16/Nov/21 Resolved: 17/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris Angove | Assignee: | Michael A. Fiedler |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 5.5 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Running /etc/init.d/mongod stop with the init.d script supplied in the RPM fails because it is not using the proper config for killproc. It seems to expect a different version of killproc macro. The version installed on Centos 5 has a -t not -d and some restrictions on ordering. |
| Comments |
| Comment by Michael A. Fiedler [ 17/May/12 ] |
|
This has been resolved in a prior revision - I haven't found the exact one, but it's correct now. |
| Comment by Reid Morrison [ 26/Aug/11 ] |
|
We have updated the standard mongod init.d script with a few features and tested it thoroughly on Red Hat EL 5. This version is attached. It addresses the problem where the stop does not work if the mongo database is not in the default location. We have thoroughly tested this init.d and can test it again if it is included in the 2.0 RC releases. |