[SERVER-16240] RHEL sysvinit script causes error on el6.6 Created: 19/Nov/14 Updated: 09/Feb/15 Resolved: 19/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jakov Sosic | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | 1) upgrade RHEL/CentOS/Scientific to 6.6 |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Mongo 2.6.x sysv init script for EL6 isn't working correctly on 6u6. This is the output that standard start call returns:
Problem is that RedHat changed /etc/rc.d/init.d/functions, in a way that function __pids_var_run() contains new entry:
This is wrongly interpreted in daemon() function that Mongo uses. Problem is that $base is considered complete line:
This causes side effect:
and thus spitting out errors. Solution is to use '--check' parameter for daemon() call. Here is proposing patch:
|
| Comments |
| Comment by Ramon Fernandez Marina [ 21/Dec/14 ] |
|
smowtion, note also there's a possible workaround posted in |
| Comment by Daniel Pasette (Inactive) [ 21/Dec/14 ] |
|
The work is being tracked in the duplicate issue: |
| Comment by Smowtion [ 21/Dec/14 ] |
|
Hello, What's happen? I have same issue and can't start mongodb ? What's solution for that ? |
| Comment by Ramon Fernandez Marina [ 19/Nov/14 ] |
|
No problem jsosic@neogov.net, some times is not easy to find if something has been reported before. Thanks for taking the time to open a detailed ticket, and specially for putting together a tentative patch! |
| Comment by Jakov Sosic [ 19/Nov/14 ] |
|
Sorry, didn't found other bug... |
| Comment by Ramon Fernandez Marina [ 19/Nov/14 ] |
|
Thanks for your report jsosic@neogov.net, and for the proposed patch. This issue was recently reported in |