Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

You can clone a DB and point to it I believe.

There should be a lot more stacks in the logs.  Can you look at or send the 
full log?

You can check the db, put -deep on it too, but don't runscript.  You cloned 
all tables/views/constraints/foreignkeys?  

You shouldn't need to do this, but if you want to migrate from one env to 
another, run the changelog to changelog temp and you can try to 
export/import.  Or try to export to GSH script if you are fully patched...

Thanks
Chris


-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Baron Fujimoto
Sent: Monday, April 11, 2016 11:13 PM
To: Grouper Users 
<>
Subject: [grouper-users] Re: problem running grouper on copy of its database

On Mon, Apr 11, 2016 at 09:56:57AM -1000, Baron Fujimoto wrote:
>On Mon, Apr 11, 2016 at 09:12:01AM -1000, Baron Fujimoto wrote:
>>We've been running Grouper 2.2.2 successfully in a test environment.
>>We're now attempting to promote this to a production environment. One of
>>our steps was to take the MySQL db used in the test env, and clone it to
>>its own production env db. This is where we have run into a problem. Our
>>DBA has exported the old/test grouper db and imported it to a
>>new/production db. However, when we configure Grouper to point to the new
>>production db, we get the following errors:
>>
>>Couldnt startup grouper: Problem in HibernateSession: HibernateSession 
>>(7b6e5c12): notNew, notReadonly, READ_WRITE_NEW, activeTransaction, session 
>>(1f0b3cfe),
>>Exception in save: edu.internet2.middleware.grouper.Membership, 
>>ByObjectStatic, query: ', cacheable: null, cacheRegion: null, entityName: 
>>ImmediateMembershipEntry, tx type: null,
>>Problem in HibernateSession: HibernateSession (10c07b8d): new, notReadonly, 
>>READ_WRITE_NEW, notActiveTransaction, session (1f0b3cfe)
>>[...]
>>
>>Does anyone have any ideas or suggestions as to what the problem is?
>
>Sorry to follow up my own post so soon, but searches seem to indicate
>that running "gsh -registry -check" may be of some use? I seem to see
>it in reference to new installs and upgrades. This isn't an upgrade,
>but might the check be useful nonetheless to resolve this? Given
>that it's unable to start now anyway, is there any harm to running
>this and the resulting SQL file for the DDL?

While I'm on the topic, generally what is the recommended method for this
sort of task (copying the Grouper registry)? This seemed like a reasonable
(naive?) approach, yet apparently failed for as yet unknown reasons in
practice. We'd like to have a better understanding of this.  Is what we're
doing so unusual that others have neither tried nor encountered this?

Unless anyone can provide some guidance on this, we'll probably fall back
on re-provisioning the new registry from scratch with the data, which we
expect will take quite a long time. :(

Aloha,
-baron
-- 
Baron Fujimoto 
<>
 :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum