Hi Nick
Yes, Jan helped me to find it and it's now working.
Thanks a lot for your help
Paul
On Wed, 3 Jan 2024 at 21:33, Nick Vatamaniuc wrote:
> That looks like a DNS or other network problem where some nodes cannot
> be reached by other nodes.
>
> If I am not mistaken I think you and Jan already debugged this issue
> in Slack and it turned out to be that one of the nodes was
> couchdb@127.0.0.1 instead of a proper hostname.
>
> Regards,
> -Nick
>
> On Fri, Dec 29, 2023 at 8:05 AM Paul Milner wrote:
> >
> > Hello there
> >
> > I have a 3 node couchdb cluster and in every node of the cluster I get
> the
> > following error every minute:
> >
> > ** Cannot get connection id for node 'couchdb@*dns of node''
> >
> > dns of node is also the node name on which the error occurs. So I get 1
> > message for each node on that particular node.
> >
> > On node 1:
> > ** Cannot get connection id for node 'couchdb@*dns of node1''
> >
> > On node 2
> > ** Cannot get connection id for node 'couchdb@*dns of node2''
> >
> > On node 3:
> > ** Cannot get connection id for node 'couchdb@*dns of node3''
> >
> >
> > Everything seems to work, but I get this error message.
> >
> > Can someone tell me what I should do please?
> >
> > Thanks
> > Paul
>
