Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Grouper 2.4 to 2.5 stategy

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Grouper 2.4 to 2.5 stategy


Chronological Thread 
    < Chronological >      < Thread >
  • From: "Hyzer, Chris" <>
  • To: "Redman, Chad" <>, "" <>, "O'Dowd, Josh" <>
  • Subject: RE: [grouper-users] Grouper 2.4 to 2.5 stategy
  • Date: Mon, 13 Apr 2020 20:04:07 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isc.upenn.edu; dmarc=pass action=none header.from=isc.upenn.edu; dkim=pass header.d=isc.upenn.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BavpmPPkXmpeWe04VisFQuT5msP8+22WVj0Y3H2f1Y8=; b=K94kgIJRI1N37j0rGDd0m0fUxRg2AKB7GPI7mWOlJgBiMyT8slHWtOA0oF1VObpC3Rxp8Kmr02ZhHx716U9oQBQE++/jaTPihZoUQpuIVQLRZIHC7FUMzZEcZyGCGGKY08j0CpsFWybt14xhPcEoNLnWOG5fOFHQkvCvEMO57MlnUWdVC5CWgUljw/MKIfENINbunORQiEw/UXxusPM30ghI2kxZa/z/+bSNMKXnTdLdjLkVmARkuvinmbh8f+Xldg4qd3xlzI00jhnGHFCGaAb+KYa+Wu5HIAqkLJwhSP0Vnwxh2r47uOc7pAZqS1Uat3hQYWOeDjtl/TxoIkqm9w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W2jynFthxe4jMFn2h8MjxCg9o8mq6/ZZ/UZ6qh0Ol30SVtW5OtS47Tji6D75p6EXVAs/Mk3qxMkr4b6bpayvPKD5ZKwwccepcZBZkgezy3XcFFDcH//ZCboOiCCO60zuwM2ZjTSYG+46I2qNybKH+N0+uvnlj6r1B+k4ykVTjbwtVM5dOxKKR8uM89BOyTg+3CEJYQ6WL+JDGSruPB5JVbPBSyyan9EmYCegNcsu8MVKnCjLLPsxtyTp432Vgl5c2s2W9xfn+K7rkeeYdxm5wKYRegqqkEVRps21+sowmP3upRfuc7HXSWGBxIAoB8E2bBdoYfpZi5QIbweW+0W3rA==

Yes, go to v2.5.  You will be in a container v2.5, so there wont be much of the old server as far as where your configs are and stuff.  If that container is on the old server or on a different server it’s a similar experience.  If you want to discuss the specifics message me on slack.

 

Thanks!

 

From: On Behalf Of Redman, Chad
Sent: Monday, April 13, 2020 3:13 PM
To: ; O'Dowd, Josh <>
Subject: Re: [grouper-users] Grouper 2.4 to 2.5 stategy

 

If the api is patched and doesn't have issues, there shouldn't be issues upgrading. So I would recommend the first method, although I would have a back up as insurance.

 

I couldn't find the previous emails you mentioned. Was it hibernate caching or hibernate session errors? The HibernateSession error can sometimes hide the real error, so it's not always obvious what the real issue is. If you're going to upgrade it's not worth the effort, but I'm curious what the error was.

 

-Chad

 

From: <> on behalf of O'Dowd, Josh <>
Sent: Monday, April 13, 2020 11:35 AM
To: <>
Subject: [grouper-users] Grouper 2.4 to 2.5 stategy

 

Hello,

 

We have been running v2.4 for the past year or so.  While we have been successful patching the API, fully, we have been unable to patch the UI beyond #34 without fatal startup; something that appears to occur during some hibernate caching process, where it closes sessions and then tries to use them again.  I have mailed a couple of requests(since the first of the year) for help with that issue, that have garnered no response, as yet.

 

I think at this point, I have spent so much time failing to get v2.4 fully patched, that I would like to consider just moving forward with v2.5.

 

My question is, would it be recommended to upgrade the current database(v2.4 on postgres) to v2.5, then build a new Grouper server and connect it to the existing database, or would it be better to build an entirely new v2.5 environment and then do a gsh export from v2.4 and import to v2.5?

 

Any thoughts?

 

Thanks,

 

Josh O'Dowd
Software Systems Engineer
Identity & Access Management Systems, IT Central

 


Archive powered by MHonArc 2.6.19.

Top of Page