>> > Shortly after, the slon instance connecting to the provider database
>> began
>> > emitting an error I'm not sure how to interpret:
>> >
>> >    ERROR  remoteListenThread_5: db_getLocalNodeId() returned 4 - wrong
>> > database?
>
>> This means that the sl_path.pa_conninfo on the node where you are
>> getting that error to connect to node 5 actually contains the
>> information how to connect to node 4.
>
>> So you are looking for an sl_path entry that has pa_server = 5 and
>> pa_client = <the one that spits the error>. Look twice, I know that is
>> is wrong :-)
>
> Oh, I do see a lot of incorrect connection information in sl_path.
> Thanks!  Can I fix this by updating sl_path.pa_conninfo directly on my
> one provider?
>
> Also, I notice one of my clients, only has one row, and the one row it
> does have, the pa_conninfo is set to '<event pending>'.
>
> I know this node hasn't been recieving transactions. Can I fix this
> somehow without dropping my nodes and adding them again?

I'd be inclined to fix this by doing a fresh set of STORE PATH requests,
and letting them propagate.

Write up one slonik script that has ALL the paths, the way they should be.

Submit it.  Maybe submit it twice, with some delay, as there will be some
delay in each STORE PATH request propagating across the cluster.

At any rate, but submitting it "en masse," that should get all nodes fixed
up all together.

If things remain "stuck," that may indicate you haven't got enough path
entries set up, and news isn't getting through somewhere.  But submitting
a full script of *all* the paths should blow through most of it...