Grouper Users - Open Discussion List

["Gettes, Michael" <>]

I withdraw this problem report.  Carey Black’s inquiries have essentially 
proven to me what I thought wasn’t a memory problem in fact must be as I can 
no longer recreate the problem and I believe he was right.

My apologies if I wasted the value time of any members of the grouper dev 
team.

/mrg

> On May 23, 2018, at 9:04 AM, Gettes, Michael 
> <>
>  wrote:
> 
> Good morning all,
> 
> Lately, I have been doing a lot of testing using the TIER Grouper package.  
> Part of the package includes a 389 directory server (great choice!) and I 
> have configured the environment to publish groups to 389 using PSPNG.  I 
> have getting more and more intense with the work as time goes on to be able 
> to effectively demo Grouper on my laptop.  Over time, the “daemon” 
> container is killed.  I haven’t been able to figure out what is going on or 
> why.  I decided to remove the “provision_to” attributes from the folder 
> hierarchy I was putting into 389 and noticed the daemon container wasn’t 
> being killed any longer.  The daemon container essentially runs gsh -loader 
> and that is all.  Turning PSPNG back on again, and the daemon container 
> gets killed again.  By “killed” I mean the container generates an error 
> message indicating “killed” and the entire docker container process 
> disappears - the gsh -loader is no longer running.
> 
> I hope this helps point in the direction of a problem.  I would really like 
> to be able to reliably run PSPNG.  I am including my PSPNG config below.  
> When PSPNG is running, it works great with this config.  If anyone is 
> curious, givenName is being used because eduPerson is not yet part of the 
> 389 config within the TIER Grouper package.
> 
> /mrg
> 
> <pspng.config>