[389-users] Re: Account Policy Plugin combined with user policy and "passwordexp: off" impossible?

Hi Simon, thanx for your help. But it is rather the other way round: The customer already has the policy for special users that must not be forced to change the password. In addition, the customer now wants "normal" users to be completely locked out when the password has expired, only

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Hi there, > On 18 Sep 2020, at 09:09, Fong, Trevor wrote: > > Hi Everyone, > > I'm having an issue re-initializing our secondary muti-master replicated 389 > DS provider node via 389-Console > replication agreement > "Initialize > Consumer". > It eventually aborts the update with an error

[389-users] Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Hi Everyone, I'm having an issue re-initializing our secondary muti-master replicated 389 DS provider node via 389-Console > replication agreement > "Initialize Consumer". It eventually aborts the update with an error "import userRoot: Thread monitoring returned: -23" Would anyone know how to

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Yes, I think it does. So in that case it would be good to check the replication configurations and connectivity between the servers is good to eliminate that as a possible cause. > On 18 Sep 2020, at 10:02, Fong, Trevor wrote: > > Hi William, > > Thanks for your suggestion about db2ldif.

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Hi William, Thanks for your suggestion about db2ldif. Doesn't db2ldif put the server into read-only mode? We would want to avoid that as that is our primary provider. Thanks, Trev On 2020-09-17, 4:52 PM, "William Brown" wrote: Hi there, > On 18 Sep 2020, at 09:09, Fong,

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

The below bug linked to this bug: https://pagure.io/389-ds-base/issue/49915 Running "top -H", I could see that a thread hit 100% CPU on the primary provider during re-initialization of the secondary provider: top - 19:14:37 up 13 days, 5:00, 2 users, load average: 0.75, 0.39, 0.64 Threads:

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Hi William, Connectivity between the two machines is good. The replication agreement from primary provider to secondary provider is OK too. It was working this morning until I decided to re-initialize the secondary provider to resolve some data inconsistencies. Trev On 2020-09-17, 5:05 PM,

[389-users] Re: Re-initialization Failure: Bulk Import Abandoned, Thread Monitoring Returned -23

Hi Marc, Thanks for your suggestions. We had disabled autotuning, but even re-enabling autotuning we are seeing the same errors. Just wondering if we are hitting this bug? https://pagure.io/389-ds-base/issue/49796 Thanks everyone! Trev From: Marc Sauton Reply-To: