5.3 deploy failed on RedHat 7.5

[Jamie Jamison]

To prepare I installed fresh payara5 5.2020.6.  That seems to be running ok. However I'm getting 'deploy failed' for the dataverse-5.3 war file.  

I tried following the install exactly but I'm not quite sure what I did incorrectly. I'm not seeing anything useful in the server.log. 

Are there any suggestions where I should look next?  This is the test server so there isn't a huge hurry.

Thank you,

Jamie Jamison

UCLA Dataverse

[Jamie Jamison]

I have a more useful error message from attempting a deploy from the payara web interface:   : EJB Timer Service is not available. 

 An error has occurred

Error occurred during deployment: Exception while loading the app : EJB Timer Service is not available. Please see server.log for more details. PER01003: Deployment encountered SQL Exceptions: PER01000: Got SQLException executing statement "CREATE TABLE EXTERNALTOOLTYPE (ID SERIAL NOT NULL, TYPE VARCHAR(255) NOT NULL, EXTERNALTOOL_ID BIGINT NOT NULL, PRIMARY KEY (ID))": org.postgresql.util.PSQLException: ERROR: relation "externaltooltype" already exists PER01000: Got SQLException executing statement "CREATE INDEX INDEX_EXTERNALTOOLTYPE_externaltool_id ON EXTERNALTOOLTYPE (externaltool_id)": org.postgresql.util.PSQLException: ERROR: relation "index_externaltooltype_externaltool_id" already exists PER01000: Got SQLException executing statement "CREATE TABLE DATAVERSETHEME (ID SERIAL NOT NULL, BACKGROUNDCOLOR VARCHAR(255), LINKCOLOR VARCHAR(255), LINKURL VARCHAR(255), LOGO VARCHAR(255), LOGOALIGNMENT VARCHAR(255), LOGOBACKGROUNDCOLOR VARCHAR(255), LOGOFOOTER VARCHAR(255), LOGOFOOTER .... msg.seeServerLog

[James Myers]

Jamie,

This looks like the problem I mentioned in the community call. I think Gustavo’s answer in https://groups.google.com/g/dataverse-community/c/hpfJ-jqnst8/m/1b-NNJy1BAAJ should work for you. (Note that issue was about 5.0 (and setting up distributed servers) but the fix described works for an update from 5.2 to 5.3. I had to do this on a QDR dev server.

 

-- Jim

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/c7522fff-e3c4-49a6-b530-e569e6b65d31n%40googlegroups.com.

[Jamie Jamison]

Saw that one.  Wasn't quite sure since I'm not going  4.something to 5.0 but I'm going to try that again.  

[Durand, Gustavo]

Jim, you beat me to it, I was about to start looking up what I needed to cut and paste. :)

Jamie, let us know if switching that value in the domain.xml works for you.

Gustavo

On Tue, Dec 15, 2020 at 9:07 PM James Myers <qqm...@hotmail.com> wrote:

Jamie,

This looks like the problem I mentioned in the community call. I think Gustavo’s answer in https://groups.google.com/g/dataverse-community/c/hpfJ-jqnst8/m/1b-NNJy1BAAJ should work for you. (Note that issue was about 5.0 (and setting up distributed servers) but the fix described works for an update from 5.2 to 5.3. I had to do this on a QDR dev server.

 

-- Jim

 

From: dataverse...@googlegroups.com [mailto:dataverse...@googlegroups.com] On Behalf Of Jamie Jamison
Sent: Tuesday, December 15, 2020 9:03 PM
To: Dataverse Users Community
Subject: [Dataverse-Users] Re: 5.3 deploy failed on RedHat 7.5

 

I have a more useful error message from attempting a deploy from the payara web interface:   : EJB Timer Service is not available. 

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/c7522fff-e3c4-49a6-b530-e569e6b65d31n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/DM5PR07MB410487D6618583226987211CBFC50%40DM5PR07MB4104.namprd07.prod.outlook.com.

[Durand, Gustavo]

Jamie,

If this had orginally started out as gf4 installation, even if you'd previously done the gf4 to p5 upgrade, then it would be necessary. We're in the process of working on adding this into the release notes. 

On Tue, Dec 15, 2020 at 9:22 PM Jamie Jamison <jam...@g.ucla.edu> wrote:

Saw that one.  Wasn't quite sure since I'm not going  4.something to 5.0 but I'm going to try that again.  

On Tuesday, December 15, 2020 at 6:07:22 PM UTC-8 Jim Myers wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/7182eafc-c952-47e3-9a1a-c4caa0d225d7n%40googlegroups.com.

[Jamie Jamison]

Success!  This time  Gustavo’s  fix  worked though per the payara github issues I also had to get rid of '  \payara5\glassfish\domains\local\lib\databases delete folder ejbtimer '  I didn't delete the ejbtimer, just renamed it hide-ejbtimer.   I'm not sure about the latter step.

Thanks again,

jamie

UCLA Dataverse

[o.be...@fz-juelich.de]

Sorry for the mess folks. Real life deployments show more errors than testing...

Gustavo should we update the release notes on GitHub with what has been discovered so far?

[o.be...@fz-juelich.de]

My bad, just saw https://github.com/IQSS/dataverse/pull/7481

[Jamie Jamison]

What about the   ejbtimer  folder in    \payara5\glassfish\domains\local\lib\databases ?  I don't want to be deleting things that might be necessary in the future.   I'm trying to be  careful before I update the production system.

[Durand, Gustavo]

Hi Jamie,

Sorry for the delay - I was doing some due diligence to make sure I understood exactly what that directory was. On my local, I had also deleted it (having found the same reference in that payara issue), but I'm generally more willing to be cavalier about my dev environment.

After further research, yes, it is safe to delete that directory. It is the database that Payara sets up for ejb timers. But a) it gets recreated if it's not there, and b) we don't have persistent timers any more, as of 5.3.

(note, I also just added this to a PR for 5.3 release notes, since you and I discovered that it's a (sometimes needed) step)

Thanks,

Gustavo

On Wed, Dec 16, 2020 at 12:25 PM Jamie Jamison <jam...@g.ucla.edu> wrote:

What about the   ejbtimer  folder in    \payara5\glassfish\domains\local\lib\databases ?  I don't want to be deleting things that might be necessary in the future.   I'm trying to be  careful before I update the production system.

 

On Wednesday, December 16, 2020 at 1:39:09 AM UTC-8 o.be...@fz-juelich.de wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/634f4633-bb76-4389-a1c2-7c8dba76082bn%40googlegroups.com.

[Jamie Jamison]

I'll rename/hide that directory when I do production.  

Thank you,

Jamie