When issuing an rs.reconfig() in the primary's console where one of the hosts' IPs were changed (secondary had died and had to be stop/started, which issued a new IP), the primary segfaulted (log attached) and had to be re-started. However, it looks like the replication set info got saved properly, as when it was re-started it connected to the secondary's new IP.