[SERVER-9143] Could not start mongodb arbiter after hard reset because of mongod.lock exist. Created: 27/Mar/13  Updated: 27/Mar/13  Resolved: 27/Mar/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Antipenko Ilya Assignee: Unassigned
Resolution: Done Votes: 0
Labels: replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-9144 Non-data nodes (arbiter) should not c... Closed
Operating System: ALL
Participants:

 Description   

After hard reset and start mongodb arbiter, it not start, because mongod.lock exist.
After manually remove mongod.lock arbiter start fine.

Wed Mar 27 18:09:36.674 [initandlisten] MongoDB starting : pid=1960 port=27019 dbpath=/mongodb/arbdata 64-bit host=node61.cl$
Wed Mar 27 18:09:36.674 [initandlisten] db version v2.4.1
Wed Mar 27 18:09:36.674 [initandlisten] git version: 1560959e9ce11a693be8b4d0d160d633eee75110
Wed Mar 27 18:09:36.674 [initandlisten] build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:2$
Wed Mar 27 18:09:36.674 [initandlisten] allocator: tcmalloc
Wed Mar 27 18:09:36.674 [initandlisten] options: { auth: "true", config: "/etc/mongoarb.conf", dbpath: "/mongodb/arbdata", k$
**************
Unclean shutdown detected.
Please visit http://dochub.mongodb.org/core/repair for recovery instructions.
*************
Wed Mar 27 18:09:36.674 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
Wed Mar 27 18:09:36.674 dbexit:
Wed Mar 27 18:09:36.674 [initandlisten] shutdown: going to close listening sockets...
Wed Mar 27 18:09:36.674 [initandlisten] shutdown: going to flush diaglog...
Wed Mar 27 18:09:36.674 [initandlisten] shutdown: going to close sockets...
Wed Mar 27 18:09:36.675 [initandlisten] shutdown: waiting for fs preallocator...
Wed Mar 27 18:09:36.675 [initandlisten] shutdown: closing all files...
Wed Mar 27 18:09:36.675 [initandlisten] closeAllFiles() finished
Wed Mar 27 18:09:36.675 dbexit: really exiting now



 Comments   
Comment by Antipenko Ilya [ 27/Mar/13 ]

I mean mongodb (data) server, not arbiter mongodb, starts after unclean shutdown by itself.

Comment by Scott Hernandez (Inactive) [ 27/Mar/13 ]

Yes, once you removed the lock file it all worked; that is expected. During an unclean shutdown, like your hard reset, the lock file will not be cleaned up so you have to do it manually.

Comment by Antipenko Ilya [ 27/Mar/13 ]

But mongodb server works fine right away after hard reset.

Comment by Scott Hernandez (Inactive) [ 27/Mar/13 ]

You will need to manually remove the lock file before you can restart the process. Please let us know if you have any other issues once you remove the lock file.

Generated at Thu Feb 08 03:19:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.