[SERVER-14031] Unexpected Shutdown in Replica Set Created: 22/May/14 Updated: 10/Dec/14 Resolved: 22/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | morteza irvani | Assignee: | Asya Kamsky |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Hi There is a replica set with 3 member (primary, secondary, arbiter ). in 2 month ago, this is the third time secondary shut down unexpectedly all three times [signalProcessingThread] caused shut down, i dont know what this means!!!! Server sources are very high, and i am not concern about |
| Comments |
| Comment by Eric Milkie [ 23/May/14 ] | |||||
|
Bash resends a SIGHUP to all jobs if it receives a SIGHUP itself; this would include mongod. | |||||
| Comment by morteza irvani [ 23/May/14 ] | |||||
|
Thanks Asya
it seems works. you said someone send signal to stop process!
so its not cause. 2. if someone use linux command "kill processId", It create such log lines
so, it may be the cause, but our NetWork Environment is very private and no one can access to linux shell and call kill command. 3.finally, remain one cause: linux automatically close the daemon!!!!! | |||||
| Comment by Asya Kamsky [ 22/May/14 ] | |||||
|
From your log file, I see that you are not starting your mongod process with the --fork option.
Since it's not forked, it's likely still attached to the tty of the shell that it was started in. This can cause it to be terminated when you log out. Starting it with fork option would resolve this issue. | |||||
| Comment by Asya Kamsky [ 22/May/14 ] | |||||
Usually this means that someone sent a signal to the process to stop it. Do you have any automation that shuts down processes that match some set of rules or thresholds? |