VM Creation #13149: perform-service production instance - D4Science Infrastructure - D4science

Actions

Copy link

VM Creation #13149

closed

perform-service production instance

Added by Fabio Sinibaldi over 6 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

_InfraScience Systems Engineer

Target version:

PerformFish

Start date:

Jan 08, 2019

Due date:

% Done:

100%

Infrastructure:

Production

RAM:

CPU:

DiskSpace:

Smartgears:

Yes

Smartgears Version:

LATEST

Application Instructions:

Smartgears scopes:

/d4science.research-infrastructures.eu/FARM/PerformFISH-KPIs

Applications list and version:

Applications context path:

perform-service

External storage data disk:

Smartgears auth connector:

data transfer enabled:

PostgreSQL database:

Number of VMs:

Description

A new VM is needed in order to test the new service 'perform-service'.

Such service needs to connect to the VRE's perform-fish-db as manager (see ticket #13111 for database details).

Related issues

Actions

Copy link

Updated by Fabio Sinibaldi over 6 years ago

Copied from VM Creation #13112: perform-service development instance added

Actions

Copy link

Updated by Andrea Dell'Amico over 6 years ago

Is there a production DB or is it meant to connect to the dev one?

Actions

Copy link

Updated by Fabio Sinibaldi over 6 years ago

The production DB published as Service Endpoint

Category = Database
Name = PF_DB

is currently pf_kpi_apps hosted on postgresql-srv.d4science.org:5432

Please take #13111 into account for database configuration.

Actions

Copy link

Updated by Tommaso Piccioli over 6 years ago

Status changed from New to In Progress
% Done changed from 0 to 40

new VM perform.d4science.org ready to be provided

Actions

Copy link

Updated by Andrea Dell'Amico over 6 years ago

% Done changed from 40 to 90

There's a problem with the container. The error below is from the production instance, but I expect an identical one on preproduction:

2019-01-15 17:36:11,941 [localhost-startStop-1] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/perform-service]- Exception sending context initialized event to listener instance of class org.gcube.smartgears.ContextListener
java.lang.RuntimeException: /perform-service is a gCube-aware application but is not managed as a gCube resource: missing or invalid context attribute gcube-application-context
        at org.gcube.smartgears.ContextListener.contextInitialized(ContextListener.java:35)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5019)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2019-01-15 17:36:11,943 [localhost-startStop-1] ERROR org.apache.catalina.core.StandardContext- Error listenerStart
2019-01-15 17:36:11,944 [localhost-startStop-1] ERROR org.apache.catalina.core.StandardContext- Context [/perform-service] startup failed due to previous errors

Actions

Copy link