-
Type:
Bug
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Duplicate
-
Affects Version/s: 2.4.9
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.5 (Final)
Release: 6.5
Codename: Final
Linux db-server 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Mongo 2.4.9 standalone host with user authentication.LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.5 (Final) Release: 6.5 Codename: Final Linux db-server 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Mongo 2.4.9 standalone host with user authentication.
-
Operating System:Linux
-
Steps To Reproduce:
After executing $sudo service mongod stop the stop process got stuck.
The last line in mongod.log says:
Mon Feb 3 14:59:33.237 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
The process is not responding to kill command (not kill -9).
Mongo client tool is able to connect but is not responding to any input. The connection is logged in the log file.
$mongod -f /etc/mongod.conf --shutdown gets stuck too and nothing good is happening.
netstat shows that it's listening on tcp/27017 and tcp/28017.
Eventually executed $kill -9 and started the service with no problem.
Stopped it again cleanly.
- duplicates
-
SERVER-1423 reads often aren't possible while in fsync and lock mode
-
- Closed
-