Replica changed IP and now can't connect

[news...@syslog.com]

The joys of EC2.

An instance running in EC2 was restarted and received a new IP, and
updated it's own DNS. The replica set config has the server listed by
domain name, which hasn't changed - just the IP has changed.

However, the replica log is full of:

Wed Apr 18 17:02:16 [rsStart] replSet error self not present in the
repl set configuration

I've tried rs.remove() and rs.add() of the replica, I've tried
deleting everything on the replica, but nothing will make the replica
reconnect.

Any clues appreciated.

[Eliot Horowitz]

Can you send:
rs.conf()
hostname
/sbin/ifconfig -a

Something probably isn't matching.

> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>

[news...@syslog.com]

This turned out to be a localized DNS issue - the remote DNS had
updated but the local hadn't updated. It started working after that
fix.

On Apr 19, 12:37 am, Eliot Horowitz <el...@10gen.com> wrote:
> Can you send:
> rs.conf()
> hostname
> /sbin/ifconfig -a
>
> Something probably isn't matching.
>

> On Wed, Apr 18, 2012 at 5:08 PM, newsgr...@syslog.com