Cant edit ACIs after importing database

[Julian Kippels]

Hi,

I just installed a completely fresh system and created a new instance of 
389 with a single database (userroot). When I use this database 
everything works as expected. But after I imported an ldif-file which 
was exported from another instance of 389 (same version number) I can't 
edit/add/delete any ACIs anymore. Everything just stalls. This happenes 
both when I use ldapmodify and using the cockpit web interface.

Editing other entries still works, I have only encountered this problem 
with ACI-entries so far.

Does anyone have a clue what is happening here?

Thanks
Julian

[Mark Reynolds]

On 3/28/25 4:51 AM, Julian Kippels via 389-users wrote:
> Hi,
>
> I just installed a completely fresh system and created a new instance 
> of 389 with a single database (userroot). When I use this database 
> everything works as expected. But after I imported an ldif-file which 
> was exported from another instance of 389 (same version number) I 
> can't edit/add/delete any ACIs anymore. Everything just stalls. This 
> happenes both when I use ldapmodify and using the cockpit web interface.

I've never heard of this happening so it is very odd.  So you mean the 
modify operation hangs?  If so please grab a pstack or two.  Does CPU 
increase during this "hang"?  Is the entire server hung?

Thanks,

Mark
> Editing other entries still works, I have only encountered this 
> problem with ACI-entries so far.
>
> Does anyone have a clue what is happening here?
>
> Thanks
> Julian