Project

General

Profile

Actions

VM Creation #12030

closed

Upgrade VM with Resource Registry instance

Added by Manuele Simi about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Target version:
Start date:
Jun 26, 2018
Due date:
% Done:

100%

Infrastructure:
Development
RAM:
2
CPU:
2
DiskSpace:
10
Smartgears:
Yes
Smartgears Version:
Application Instructions:
Smartgears scopes:

/gcube, /gcube/devNext, /gcube/devNext/NextNext

Applications list and version:
Applications context path:
External storage data disk:
Smartgears auth connector:
data transfer enabled:
No
PostgreSQL database:
No
Number of VMs:
1

Description

The container and the RR instance hosted on manuele-registry.dev.d4science.org. I tried to replace manually the RR instance and few libs, but other webapps now do not start. The container was installed on Dec 2017 and definitely needs an upgrade to the most recent releases of the hosted software.


Related issues

Related to D4Science Infrastructure - VM Creation #10686: New VM with Resource Registry instanceClosed_InfraScience Systems EngineerDec 13, 2017Dec 19, 2017

Actions
Actions #1

Updated by Manuele Simi about 7 years ago

Actions #2

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

The VM is now running smartgears version 2.2.0-4.12.0-162179 and the latest version of the resource registry.

Actions #4

Updated by Manuele Simi about 7 years ago

  • Status changed from Feedback to Closed

It works like a charm. Thanks!

Actions #5

Updated by Manuele Simi about 7 years ago

  • Status changed from Closed to In Progress
  • % Done changed from 100 to 80

I'm reopening this because there did exist problems on the node.

Specifically, when I tried to delete contexts by contacting the RR instance:

  • The node was configured with duplicated and misspelled contexts. See this error:
2018-07-03 05:29:50,787 [catalina-exec-3] WARN  RequestValidator: rejecting call to resource-registry in invalid context /gcube, allowed context are [/gcube/devNext/NextNex, /gcube/devNext/NextNext]
  • Once this was fixed (thanks Luca), libs were missing. First error was:
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoClassDefFoundError: Could not initialize class org.gcube.informationsystem.impl.utils.ISMapper

For this, I manually put information-system-model-1.8.0.jar on the classpath.

  • Next, gcube-resources-1.7.0.jar was missing:
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoClassDefFoundError: org/gcube/informationsystem/model/entity/Facet

Again, to fix this, I put the jar manually on the classpath.

Now the node seems working as expected. Please, double check that if any of the above steps is performed by an ansible script, fixes are needed in the script itself. If they are all manual steps... well, keep this comment for future nodes to configure :)

Actions #6

Updated by Andrea Dell'Amico about 7 years ago

Manuele Simi wrote:

I'm reopening this because there did exist problems on the node.

Specifically, when I tried to delete contexts by contacting the RR instance:

  • The node was configured with duplicated and misspelled contexts. See this error:
2018-07-03 05:29:50,787 [catalina-exec-3] WARN  RequestValidator: rejecting call to resource-registry in invalid context /gcube, allowed context are [/gcube/devNext/NextNex, /gcube/devNext/NextNext]
  • Once this was fixed (thanks Luca), libs were missing. First error was:
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoClassDefFoundError: Could not initialize class org.gcube.informationsystem.impl.utils.ISMapper

For this, I manually put information-system-model-1.8.0.jar on the classpath.

  • Next, gcube-resources-1.7.0.jar was missing:
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoClassDefFoundError: org/gcube/informationsystem/model/entity/Facet

Again, to fix this, I put the jar manually on the classpath.

Now the node seems working as expected. Please, double check that if any of the above steps is performed by an ansible script, fixes are needed in the script itself. If they are all manual steps... well, keep this comment for future nodes to configure :)

The wrong scope was there since the VM was created, I fixed the ansible variables.

About the missing jar files, the playbook uses the ansible maven_artifact module to download the latest versions of smartgears and the resource registry war file. If some jars were missing, the problem lies in the distribution files:

  • the smartgears distribution is unpacked and its install script run
  • the war files are unpacked under webapps, no file is added/removed from the war file.
Actions #7

Updated by Manuele Simi about 7 years ago

  • Assignee changed from _InfraScience Systems Engineer to Luca Frosini

Andrea Dell'Amico wrote:

About the missing jar files, the playbook uses the ansible maven_artifact module to download the latest versions of smartgears and the resource registry war file. If some jars were missing, the problem lies in the distribution files:

  • the smartgears distribution is unpacked and its install script run
  • the war files are unpacked under webapps, no file is added/removed from the war file.

@luca.frosini@isti.cnr.it Are these missing dependencies in the RR service?

Actions #8

Updated by Luca Frosini about 7 years ago

The jar must be already present in smartgears, that's why it is not included in resource-registry.
How old is the smartgears distribution?

Actions #9

Updated by Manuele Simi about 7 years ago

Luca Frosini wrote:

The jar must be already present in smartgears, that's why it is not included in resource-registry.
How old is the smartgears distribution?

The version is 2.2.0-4.12.0-162179. Not sure when it was released.

Actions #10

Updated by Luca Frosini about 7 years ago

Manuele Simi wrote:

Luca Frosini wrote:

The jar must be already present in smartgears, that's why it is not included in resource-registry.
How old is the smartgears distribution?

The version is 2.2.0-4.12.0-162179. Not sure when it was released.

@manuele.simi@isti.cnr.it forget what I wrote. It was my mistake information-system-model jar file must be part of resource registry and must not be part of smartgears distribution.

Looking to your container (i.e. tomcat/lib )there are libraries should not be there:

  • resource-registry-publisher-2.0.0-SNAPSHOT.jar should not be present and I think it was manually added because it is not from release 4.12
  • gcube-resources-1.7.0-20180624.061044-208.jar the same of the previous library

Looking at resource-registry libraries (i.e. tomcat/webapps/resource-registry/WEB-INF/lib/) I noticed that there are two version of information-syste-model:

information-system-model-1.8.0-20180624.050218-159.jar
information-system-model-1.8.0-SNAPSHOT.jar

Moreover there is gcube-resources-1.7.0-20180624.061044-208.jar which should not be present.

To better understand if the area some issues I suggest to clean the home of the user and use the provisioning to have a fresh installation.

Actions #11

Updated by Manuele Simi about 7 years ago

  • Assignee changed from Luca Frosini to _InfraScience Systems Engineer

I manually added those jars for the reasons I explained few comments earlier.

Anyway, @andrea.dellamico@isti.cnr.it can you please wipe out this node and start again with a fresh installation as @luca.frosini@isti.cnr.it suggests. I really need it for my tests and it has been unavailable for a while now. Thanks!

Actions #12

Updated by Andrea Dell'Amico about 7 years ago

(sorry, wrong ticket).

I'm going to reinstall the services right now.

Actions #13

Updated by Andrea Dell'Amico about 7 years ago

Done. Can you check?

Actions #14

Updated by Manuele Simi about 7 years ago

Andrea Dell'Amico wrote:

Done. Can you check?

Thanks. I don't have chance to check the node right now. I will do it later today and give an update here.

Please, just make sure that the same authorized keys from the previous installation are available also in the new one!

Actions #15

Updated by Andrea Dell'Amico about 7 years ago

Manuele Simi wrote:

Andrea Dell'Amico wrote:

Done. Can you check?

Thanks. I don't have chance to check the node right now. I will do it later today and give an update here.

Please, just make sure that the same authorized keys from the previous installation are available also in the new one!

That part is also automated. The three dev keys are installed, if something was manually added it got lost.

Actions #16

Updated by Manuele Simi about 7 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100

All my unit tests passed and I can ssh the node. Also, the installation looks good for what I can tell.

Thanks!

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)