[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-10 Thread Ludwig Krispenz 


On 09/10/2019 02:37 AM, William Brown wrote:



On 10 Sep 2019, at 09:58, Morgan, Iain (ARC-TN)[InuTeq, LLC] 
 wrote:



On 9/8/19, 15:40, "William Brown"  wrote:




On 7 Sep 2019, at 08:33, Morgan, Iain (ARC-TN)[InuTeq, LLC] 
 wrote:

Hello Marc,

Yes, it is 389-ds-base1.3.9.1-10.el7, but we are not using IPA and there are no 
memberOf plugin errors. The actual modrdn operations have error=0.

If we may, can we ask what the modrdn operations were, and to ask a little 
about your tree layout so we could try to understand more about this?


Sure, there's nothing unusual regarding the tree layout. There's a single 
backend with ou=People, and ou=Groups, One thing that may be relevant 
is that this is a stand-alone server -- replication has not been configured.

Have you configured the replica id, replication agreement or changelog though? 
I want to follow up with our replication expert about why URP is getting 
involved here, when you say replication isn't configured.
if this is really a standalone consumer without replication configured, 
this is probably a consequence of splitting the multimaster(mmr) and the 
other plugin calls and the mmr plugin could be called and do nothing, 
just try :-(

so the messages is harmless although annoying and we should fix it.



 From the access log:

[09/Sep/2019:15:05:08.577399600 -0700] conn=2233897 op=2 SRCH 
base="ou=Groups,dc=nas,dc=nasa,dc=gov" scope=2 filter="(|(cn=temp)(cn=testgroup))" 
attrs="cn"
[09/Sep/2019:15:05:08.577630700 -0700] conn=2233897 op=2 RESULT err=0 tag=101 
nentries=1 etime=0.323261
[09/Sep/2019:15:05:08.578316196 -0700] conn=2233897 op=3 MODRDN 
dn="cn=temp,ou=Groups,dc=nas,dc=nasa,dc=gov" newrdn="cn=testgroup" 
newsuperior="(null)"
[09/Sep/2019:15:05:08.581595207 -0700] conn=2233897 op=3 RESULT err=0 tag=109 
nentries=0 etime=0.0003326527

 From the errors log:

[09/Sep/2019:15:05:08.580235717 -0700] - ERR - conn=2233897 op=3 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

I think you can ignore this - with no replication cenotaphs not being added is 
not an issue. If you were in a replication topology this would be a more 
significant error. Cenotaphs are needed to resolve some replication edge cases 
in update resolution and are an internal part of our replication system. But as 
mentioned, I will follow up why URP is being accessed here, so I need some more 
information from you.

Thanks, hope this helps,




--
Iain Morgan

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org


--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-10 Thread Ludwig Krispenz 

Is this a reeadonly consumer ? we had

https://pagure.io/389-ds-base/issue/50078

It was fixed, but I am not sure into what versions it was included

On 09/06/2019 07:29 PM, Morgan, Iain (ARC-TN)[InuTeq, LLC] wrote:


On 9/5/19, 18:11, "Iain Morgan"  wrote:

 Hello,
 
 While testing 389-ds 1.3.9.1 on RHEL 7.7, I noticed the the errors

 listed below. The actual LDAP operations all succeed, but I find the
 errors disconcerting.
 
 
 [28/Aug/2019:10:42:13.446609256 -0700] - ERR - conn=44 op=5 - urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

 [28/Aug/2019:10:42:14.202854398 -0700] - ERR - conn=52 op=5 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
 [28/Aug/2019:10:42:18.504412946 -0700] - ERR - conn=95 op=3 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
 [28/Aug/2019:10:42:24.412896470 -0700] - ERR - conn=160 op=8 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
 
These all appear to be related to modrdn operations.




--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-09 Thread William Brown 


> On 10 Sep 2019, at 09:58, Morgan, Iain (ARC-TN)[InuTeq, LLC] 
>  wrote:
> 
> 
> 
> On 9/8/19, 15:40, "William Brown"  wrote:
> 
> 
> 
>> On 7 Sep 2019, at 08:33, Morgan, Iain (ARC-TN)[InuTeq, LLC] 
>>  wrote:
>> 
>> Hello Marc,
>> 
>> Yes, it is 389-ds-base1.3.9.1-10.el7, but we are not using IPA and there are 
>> no memberOf plugin errors. The actual modrdn operations have error=0.
> 
>If we may, can we ask what the modrdn operations were, and to ask a little 
> about your tree layout so we could try to understand more about this?
> 
> 
> Sure, there's nothing unusual regarding the tree layout. There's a single 
> backend with ou=People, and ou=Groups, One thing that may be relevant 
> is that this is a stand-alone server -- replication has not been configured.

Have you configured the replica id, replication agreement or changelog though? 
I want to follow up with our replication expert about why URP is getting 
involved here, when you say replication isn't configured. 

> 
> From the access log:
> 
> [09/Sep/2019:15:05:08.577399600 -0700] conn=2233897 op=2 SRCH 
> base="ou=Groups,dc=nas,dc=nasa,dc=gov" scope=2 
> filter="(|(cn=temp)(cn=testgroup))" attrs="cn"
> [09/Sep/2019:15:05:08.577630700 -0700] conn=2233897 op=2 RESULT err=0 tag=101 
> nentries=1 etime=0.323261
> [09/Sep/2019:15:05:08.578316196 -0700] conn=2233897 op=3 MODRDN 
> dn="cn=temp,ou=Groups,dc=nas,dc=nasa,dc=gov" newrdn="cn=testgroup" 
> newsuperior="(null)"
> [09/Sep/2019:15:05:08.581595207 -0700] conn=2233897 op=3 RESULT err=0 tag=109 
> nentries=0 etime=0.0003326527
> 
> From the errors log:
> 
> [09/Sep/2019:15:05:08.580235717 -0700] - ERR - conn=2233897 op=3 - 
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

I think you can ignore this - with no replication cenotaphs not being added is 
not an issue. If you were in a replication topology this would be a more 
significant error. Cenotaphs are needed to resolve some replication edge cases 
in update resolution and are an internal part of our replication system. But as 
mentioned, I will follow up why URP is being accessed here, so I need some more 
information from you.

Thanks, hope this helps,



> 
> -- 
> Iain Morgan
> 
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-08 Thread William Brown 


> On 7 Sep 2019, at 08:33, Morgan, Iain (ARC-TN)[InuTeq, LLC] 
>  wrote:
> 
> Hello Marc,
> 
> Yes, it is 389-ds-base1.3.9.1-10.el7, but we are not using IPA and there are 
> no memberOf plugin errors. The actual modrdn operations have error=0.

If we may, can we ask what the modrdn operations were, and to ask a little 
about your tree layout so we could try to understand more about this?


> 
> -- 
> Iain Morgan
> 
> On 9/6/19, 15:05, "Marc Sauton"  wrote:
> 
>could you check the system has 389-ds-base-1.3.9.1-10.el7 
> 
>  or
> above?
>do the MODRDN fail with err=53?
>is it in IPA context with memberof-plugin errors?
>there was a bug fix in bz 1680245 that seem related to this, may be there 
> is till something going on, or may be it can be ignored.
> 
>we would likely need to privately review more logs to tell (open a RH 
> case?)
>Thanks,
>M.
> 
> 
>On Fri, Sep 6, 2019 at 10:38 AM Morgan, Iain (ARC-TN)[InuTeq, LLC] 
>  wrote:
> 
> 
> 
> 
>On 9/5/19, 18:11, "Iain Morgan"  wrote:
> 
>Hello,
> 
>While testing 389-ds 1.3.9.1 on RHEL 7.7, I noticed the the errors
>listed below. The actual LDAP operations all succeed, but I find the
>errors disconcerting.
> 
> 
>[28/Aug/2019:10:42:13.446609256 -0700] - ERR - conn=44 op=5 - 
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
>[28/Aug/2019:10:42:14.202854398 -0700] - ERR - conn=52 op=5 - 
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
>[28/Aug/2019:10:42:18.504412946 -0700] - ERR - conn=95 op=3 - 
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
>[28/Aug/2019:10:42:24.412896470 -0700] - ERR - conn=160 op=8 - 
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
> 
>These all appear to be related to modrdn operations.
> 
>-- 
>Iain Morgan
> 
>___
>389-users mailing list -- 
>389-users@lists.fedoraproject.org 
> 
>To unsubscribe send an email to 
>389-users-le...@lists.fedoraproject.org 
> 
>Fedora Code of Conduct: 
>https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 
> 
>List Guidelines: 
>https://fedoraproject.org/wiki/Mailing_list_guidelines 
> 
>List Archives: 
>
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>  
> 
> 
> 
> 
> 
> 
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-06 Thread Morgan, Iain (ARC-TN)[InuTeq, LLC] 
Hello Marc,

Yes, it is 389-ds-base1.3.9.1-10.el7, but we are not using IPA and there are no 
memberOf plugin errors. The actual modrdn operations have error=0.

-- 
Iain Morgan

On 9/6/19, 15:05, "Marc Sauton"  wrote:

could you check the system has 389-ds-base-1.3.9.1-10.el7 

 or
 above?
do the MODRDN fail with err=53?
is it in IPA context with memberof-plugin errors?
there was a bug fix in bz 1680245 that seem related to this, may be there 
is till something going on, or may be it can be ignored.

we would likely need to privately review more logs to tell (open a RH case?)
Thanks,
M.


On Fri, Sep 6, 2019 at 10:38 AM Morgan, Iain (ARC-TN)[InuTeq, LLC] 
 wrote:




On 9/5/19, 18:11, "Iain Morgan"  wrote:

Hello,

While testing 389-ds 1.3.9.1 on RHEL 7.7, I noticed the the errors
listed below. The actual LDAP operations all succeed, but I find the
errors disconcerting.


[28/Aug/2019:10:42:13.446609256 -0700] - ERR - conn=44 op=5 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:14.202854398 -0700] - ERR - conn=52 op=5 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:18.504412946 -0700] - ERR - conn=95 op=3 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:24.412896470 -0700] - ERR - conn=160 op=8 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

These all appear to be related to modrdn operations.

-- 
Iain Morgan

___
389-users mailing list -- 
389-users@lists.fedoraproject.org 
To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org 

Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 

List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines 

List Archives: 

https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org 






___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-06 Thread Marc Sauton 
could you check the system has 389-ds-base-1.3.9.1-10.el7

or
above?
do the MODRDN fail with err=53?
is it in IPA context with memberof-plugin errors?
there was a bug fix in bz 1680245 that seem related to this, may be there
is till something going on, or may be it can be ignored.
we would likely need to privately review more logs to tell (open a RH case?)
Thanks,
M.

On Fri, Sep 6, 2019 at 10:38 AM Morgan, Iain (ARC-TN)[InuTeq, LLC] <
iain.mor...@nasa.gov> wrote:

>
>
> On 9/5/19, 18:11, "Iain Morgan"  wrote:
>
> Hello,
>
> While testing 389-ds 1.3.9.1 on RHEL 7.7, I noticed the the errors
> listed below. The actual LDAP operations all succeed, but I find the
> errors disconcerting.
>
>
> [28/Aug/2019:10:42:13.446609256 -0700] - ERR - conn=44 op=5 -
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
> [28/Aug/2019:10:42:14.202854398 -0700] - ERR - conn=52 op=5 -
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
> [28/Aug/2019:10:42:18.504412946 -0700] - ERR - conn=95 op=3 -
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
> [28/Aug/2019:10:42:24.412896470 -0700] - ERR - conn=160 op=8 -
> urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
>
> These all appear to be related to modrdn operations.
>
> --
> Iain Morgan
>
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: urp_fixup_add_cenotaph errors

2019-09-06 Thread Morgan, Iain (ARC-TN)[InuTeq, LLC] 


On 9/5/19, 18:11, "Iain Morgan"  wrote:

Hello,

While testing 389-ds 1.3.9.1 on RHEL 7.7, I noticed the the errors
listed below. The actual LDAP operations all succeed, but I find the
errors disconcerting.


[28/Aug/2019:10:42:13.446609256 -0700] - ERR - conn=44 op=5 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:14.202854398 -0700] - ERR - conn=52 op=5 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:18.504412946 -0700] - ERR - conn=95 op=3 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21
[28/Aug/2019:10:42:24.412896470 -0700] - ERR - conn=160 op=8 - 
urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

These all appear to be related to modrdn operations.

-- 
Iain Morgan

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org