Mongo replica set with no PRIMARY/SECONDARY, members are STARTUP2 and RECOVERING
I was able to resolve this by Breaking the Mirror.  Essentially, I picked one of the members, turned it off, removed the /data/local* files, turned it on, and did a rs.initiate().  At this point, I was a replica set of 1 (myself) and primary (obviously).  Then, for the other two guys, I turned them off, wiped their entire /data/* files and turned them back on.  From the original primary member, I simply added added the two new guys with rs.add("mongo_rs_5_member_1:27018") and rs.add("mongo_rs_5_member_2:27019").  Then the primary synced all the content to the other guys (many hours) and the replica set was health.  No more errors in the relevant application.