:26 PM, William Brown wrote:
>
> Hey there,
>
>> On 19 Dec 2020, at 21:59, Oleg Cohen wrote:
>>
>> Greetings,
>>
>> I have a server that suddenly can be started due to the following error:
>>
>> PR_Bind() on All Interfaces port 389 failed: Ne
there.
Wonder if anyone has encountered a similar issue and if there are any ways
to further troubleshoot and fix the problem.
Thank you!
Oleg
--
*Oleg Cohen | Principal | **A S S U R E B R I D G E*
*Office: +1 617 564 0737 | Mobile: +1 617 455 7927 | Fax: +1 888 409
6995*
*Email: oleg.co
Greetings,
I run a Java application. From time to time I start seeing the following error
in the logs:
LDAP: error code 12 - Unavailable Critical Extension
I have a three node 389-DS cluster and don't see any errors in the respective
389 DS logs.
The restart of the Java application seems to
Thank you very much, William! I do see a stream of changes into the source
node. I think something ran amok :-( Again, thank you.
> On Nov 5, 2019, at 6:36 PM, William Brown wrote:
>
>
>
>> On 6 Nov 2019, at 09:29, Oleg Cohen wrote:
>>
>> Greetings,
>
Thank you very much, Mark! I will try this.
> On Nov 5, 2019, at 6:42 PM, Mark Reynolds wrote:
>
>
>
> On 11/5/19 6:29 PM, Oleg Cohen wrote:
>> Greetings,
>>
>> I am running 389-DS cluster v1.4.0.13 on CentOS 7. I have two nodes at the
>> moment w
Greetings,
I am running 389-DS cluster v1.4.0.13 on CentOS 7. I have two nodes at the
moment with a replication agreement set on both.
I have initialized replica on NODE2 from NODE1. A replication agreement
started from NODE2 to NODE1 and is now running non-stop for a number of
hours. The number
