SERVER-71449: log_successs_msg: not found #1500
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
when using service status command fixing "/etc/init.d/mongodb: 251: log_successs_msg: not found" error spelling mistake "log_successs_msg" to "log_success_msg"
Contributor
|
Thanks for making this pull request! We just need a couple of things from you to start our consideration of the PR. Can you please:
|
Contributor
|
AbdulrahmanKanaan, Just a reminder that we cannot merge your PR until you've signed the Contributor's Agreement. I've gone ahead and created the SERVER ticket for you here: SERVER-71449 |
kelly-cs
changed the title
Contributor
Author
|
Hello,
I signed the agreement, and sorry for the delay
Thanks
…On Thu, Nov 17, 2022 at 7:10 PM kelly-cs ***@***.***> wrote:
AbdulrahmanKanaan,
Just a reminder that we cannot merge your PR until you've signed the Contributor's
Agreement <https://www.mongodb.com/legal/contributor-agreement>.
I've gone ahead and created the SERVER ticket for you here: SERVER-71449
<https://jira.mongodb.org/browse/SERVER-71449>
—
Reply to this email directly, view it on GitHub
<#1500 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/APJOFL3LH6VHXHYRHNUT3BDWIZKG7ANCNFSM6AAAAAARI3F7SA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ghost
closed this
in
ghost
pushed a commit
that referenced
this pull request
Dec 13, 2022
when using service status command fixing "/etc/init.d/mongodb: 251: log_successs_msg: not found" error spelling mistake "log_successs_msg" to "log_success_msg" Closes #1500 Signed-off-by: Ryan Egesdahl <ryan.egesdahl@mongodb.com> (cherry picked from commit 852d4db) (cherry picked from commit 37a912f)
ghost
pushed a commit
that referenced
this pull request
Dec 13, 2022
when using service status command fixing "/etc/init.d/mongodb: 251: log_successs_msg: not found" error spelling mistake "log_successs_msg" to "log_success_msg" Closes #1500 Signed-off-by: Ryan Egesdahl <ryan.egesdahl@mongodb.com> (cherry picked from commit 852d4db) (cherry picked from commit 37a912f) (cherry picked from commit ed2e0d8)
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when using service status command
fixing "/etc/init.d/mongodb: 251: log_successs_msg: not found"
error spelling mistake, changed "log_successs_msg" to "log_success_msg"