[SERVER-24282] mongod terminates upon receiving signal 1 (Hangup) Created: 25/May/16  Updated: 26/May/16  Resolved: 25/May/16

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.0.12
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Karisiddappa Shiva Kumar Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

"system" :

{ "currentTime" : ISODate("2016-05-25T09:31:36.534Z"), "cpuAddrSize" : 64, "memSizeMB" : 14026, "numCores" : 2, "cpuArch" : "x86_64", "numaEnabled" : false }

,
"os" : {
"type" : "Linux",
"name" : "CentOS Linux release 7.0.1406 (Core) ",
"version" : "Kernel 3.10.0-123.20.1.el7.x86_64"


Operating System: ALL
Steps To Reproduce:

intermittent

Participants:

 Description   

we have 3 node replication .

mongdb primary failed many times with the below error

CONTROL  [signalProcessingThread] got signal 1 (Hangup), will terminate after current cmd ends
 
2016-05-25T02:51:11.226+0000 I NETWORK  [initandlisten] connection accepted from 172.25.0.6:34372 #5004 (2 connections now open)
2016-05-25T02:51:11.488+0000 I CONTROL  [signalProcessingThread] got signal 1 (Hangup), will terminate after current cmd ends
2016-05-25T02:51:11.506+0000 I REPL     [signalProcessingThread] Stopping replication applier threads
2016-05-25T02:51:11.673+0000 I STORAGE  [WiredTigerRecordStoreThread for local.oplog.rs] shutting down
2016-05-25T02:51:12.329+0000 I CONTROL  [signalProcessingThread] now exiting
2016-05-25T02:51:12.329+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2016-05-25T02:51:12.329+0000 I NETWORK  [signalProcessingThread] closing listening socket: 6
2016-05-25T02:51:12.329+0000 I NETWORK  [signalProcessingThread] closing listening socket: 7
2016-05-25T02:51:12.329+0000 I NETWORK  [signalProcessingThread] closing listening socket: 8
2016-05-25T02:51:12.329+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2016-05-25T02:51:12.330+0000 I NETWORK  [signalProcessingThread] shutdown: going to flush diaglog...
2016-05-25T02:51:12.330+0000 I NETWORK  [signalProcessingThread] shutdown: going to close sockets...
2016-05-25T02:51:12.337+0000 I STORAGE  [signalProcessingThread] WiredTigerKVEngine shutting down
2016-05-25T02:51:12.338+0000 I NETWORK  [conn5004] end connection 172.25.0.6:34372 (1 connection now open)
2016-05-25T02:51:12.338+0000 I NETWORK  [conn5003] end connection 172.25.0.7:58624 (0 connections now open)
2016-05-25T02:51:12.814+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2016-05-25T02:51:12.814+0000 I CONTROL  [signalProcessingThread] dbexit:  rc: 0

set1:PRIMARY> rs.conf();
{
        "_id" : "set1",
        "version" : 2,
        "members" : [
                {
                        "_id" : 0,
                        "host" : "xxxxxx:27017",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 3,
                        "tags" : {
 
                        },
                        "slaveDelay" : 0,
                        "votes" : 1
                },
                {
                        "_id" : 1,
                        "host" : "xxxxxx:27018",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 2,
                        "tags" : {
 
                        },
                        "slaveDelay" : 0,
                        "votes" : 1
                },
                {
                        "_id" : 2,
                        "host" : "xxxxxxxx:27019",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 1,
                        "tags" : {
 
                        },
                        "slaveDelay" : 0,
                        "votes" : 1
                }
        ],
        "settings" : {
                "chainingAllowed" : true,
                "heartbeatTimeoutSecs" : 10,
                "getLastErrorModes" : {
 
                },
                "getLastErrorDefaults" : {
                        "w" : 1,
                        "wtimeout" : 0
                }
        }
}



 Comments   
Comment by Ramon Fernandez Marina [ 26/May/16 ]

The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by Karisiddappa Shiva Kumar [ 26/May/16 ]

Thanks, what is your advice on Root Cause Analysis. need to check who or what is sending this signal.
what other log files we need to check at OS or at MongoDB.

Comment by Ramon Fernandez Marina [ 25/May/16 ]

kumar_kshiva, seems like mongod is receiving the SIGHUP signal and terminating, which is expected behavior. You need to check who or what is sending this signal.

Regards,
Ramón.

Generated at Thu Feb 08 04:05:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.