[SERVER-40511] BadValue aborting after fassert() failure Created: 06/Apr/19 Updated: 08/Apr/19 Resolved: 08/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Saravanan Kuppusamy | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, I want to add a new field _cpy in all dbs and all collection documents. As it was running my replicaset primary stopped and when I attempt to restart I am getting this error. Please advise how to fix.
2019-04-06T02:22:52.616+0000 I CONTROL [initandlisten]2019-04-06T02:22:52.616+0000 I CONTROL [initandlisten] ** WARNING: soft rlimits too low. rlimits set to 29932 processes, 65536 files. Number of processes should be at least 32768 : 0.5 times$2019-04-06T02:22:52.616+0000 I CONTROL [initandlisten]2019-04-06T02:22:53.222+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/opt/mongodb-disk-3/data/diagnostic.data'2019-04-06T02:22:53.227+0000 F REPL [initandlisten] Error loading local voted for document at startup; BadValue: Unexpected field _cpy in LastVote2019-04-06T02:22:53.227+0000 F - [initandlisten] Fatal Assertion 40367 at src/mongo/db/repl/replication_coordinator_impl.cpp 4622019-04-06T02:22:53.227+0000 F - [initandlisten]***aborting after fassert() failure |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 08/Apr/19 ] |
|
Hello Saravanan, It looks like you added the new field to some of the system collections. You should never directly write to those collections and will need to adjust your query to only touch user-created collections if you want to run it again. If the other nodes in the replica set still work, I recommend that you perform an initial sync of this node to make it healthy again. If you have a viable backup, you may wish to use it as well. If neither of the above is an option, you may wish to try starting the node as a standalone and seeding a new replica set instead of using the existing broken one. Please note that the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Thanks, Danny |