grouper-users - Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope
Subject: Grouper Users - Open Discussion List
List archive
Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope
Chronological Thread
- From: Sebastien Gagne <>
- To: David Langenberg <>
- Cc: Dominique Petitpierre <>, "" <>
- Subject: Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope
- Date: Sun, 28 Apr 2013 13:28:37 -0400
- Authentication-results: sfpop-ironport02.merit.edu; dkim=pass (signature verified)
Hi,
This error message will happen for any object for which no PSO definition is defined. I get the same message with attribute assignements (which don't have any PSO defined) I figure these will also be taken into account in the JIRA.---
Sébastien Gagné, M.Ing., ing. jr
Analyste en informatique - Université de Montréal
Sébastien Gagné, M.Ing., ing. jr
Analyste en informatique - Université de Montréal
On Sat, Apr 27, 2013 at 10:33 PM, David Langenberg <> wrote:
Hi Dominique,
Yes, we're aware of this issue https://bugs.internet2.edu/jira/browse/GRP-811 and I totally agree -- it's quite annoying.
Thanks for the report.
Dave
--
David Langenberg
Identity & Access Management
The University of Chicago
On Apr 27, 2013, at 5:44 PM, Dominique Petitpierre <>
> <grouper_error.log_extract2.txt><grouper_error.log_extract3.txt>wrote:
> Hello,
>
> in Grouper 2.1.3 PSP logs an ERROR level message when it processes a
> change that occured in a branch that is not synchronized. For example,
> the log in annexe shows such a error message for a change occurring in
> etc:sysadmingroup, while the branch "etc" is explicitly excluded in
> the rules of psp-resolver.xml:
>
> ERROR .... status=failure,error=noSuchIdentifier,errorMessages={Unable to calculate provisioned object.}
>
> In my case there is a large number of non synchronized branches thus
> causing a lot of these systematic spurious ERROR messages.
>
> The same thing happens when one adds a new folder or group that does
> not occur yet in the target LDAP directory (cf. extract in second
> annexe):
>
> ERROR .... status=failure,error=noSuchIdentifier,errorMessages={}
>
> In both cases the situation is completely normal and it is annoying to
> have to sort out the real ERROR level messages from these spurious ones.
>
> It would be better that, in these cases, PSP would only log a message
> reporting such information (i.e. the fact that a branch is not
> synchronized or that the folder is inexistent in the LDAP directory)
> at INFO or even DEBUG level.
>
> Best regards,
> Dominique
> --
> Mr Dominique Petitpierre, user=Dominique.Petitpierre domain=unige.ch
> IT Division, University of Geneva, Switzerland
- [grouper-users] PSP: spurious error messages for changes not in synchronized scope, Dominique Petitpierre, 04/27/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, David Langenberg, 04/27/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, Sebastien Gagne, 04/28/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, David Langenberg, 04/28/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, Dominique Petitpierre, 04/29/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, Sebastien Gagne, 04/28/2013
- Re: [grouper-users] PSP: spurious error messages for changes not in synchronized scope, David Langenberg, 04/27/2013
Archive powered by MHonArc 2.6.16.