Task #12639
closed
DataMiner - Check the configuration of the algorithms for the Proto Generic Workers.
100%
Description
The Proto Generic Workers have been configured to use the algorithms of production:
gcube@dataminer0-gw-proto:~/wps_algorithms/algorithms$ ls prod gcube@dataminer1-gw-proto:~/wps_algorithms/algorithms$ ls prod gcube@dataminer2-gw-proto:~/wps_algorithms/algorithms$ ls prod gcube@dataminer3-gw-proto:~/wps_algorithms/algorithms$ ls prod gcube@dataminer4-gw-proto:~/wps_algorithms/algorithms$ ls prod gcube@dataminer5-gw-proto:~/wps_algorithms/algorithms$ ls prod
These DataMiner should use Proto algorithms.
Updated by Andrea Dell'Amico over 6 years ago
- Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo
Updated by Roberto Cirillo over 6 years ago
- Status changed from New to In Progress
I've never exectuted this kind of task. I hope it works as I expect
Updated by Roberto Cirillo over 6 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Roberto Cirillo to Giancarlo Panichi
- % Done changed from 0 to 20
For testing, I've modified only dataminer0-gw-proto.d4science.org
Please @g.panichi@isti.cnr.it could you check if it is ok for you? if it's ok, I'm going to upgrade the other instances.
Updated by Giancarlo Panichi over 6 years ago
- Status changed from Feedback to In Progress
- Assignee changed from Giancarlo Panichi to Roberto Cirillo
Please @roberto.cirillo@isti.cnr.it, can you restart all DataMiner so that tomcat instances load the correct jar? Thanks.
Updated by Roberto Cirillo over 6 years ago
For the moment, I've upgraded only dataminer0-gw-proto.d4science.org. I'm going to change the other instances and restart
Updated by Roberto Cirillo over 6 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Roberto Cirillo to Giancarlo Panichi
- % Done changed from 20 to 100
All the instances have been changed and restarted. Please close this ticket if it is ok for you.
Updated by Roberto Cirillo over 6 years ago
- % Done changed from 100 to 0
the GetCapabilities doesn't work now. I guess because after the restart the dataminer try to use the deleted folder /home/gcube/wps_algorithms/algorithms/prod/software
but I don't know where it is defined. Could anyone help me?
The exception is the following:
2018-10-10 11:36:29,776 [localhost-startStop-1] INFO org.apache.catalina.startup.HostConfig- Deploying web application directory /home/gcube/tomcat/webapps/wps
2018-10-10 11:36:41,524 [localhost-startStop-1] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/wps]- StandardWrapper.Throwable
java.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/gcube/wps_algorithms/algorithms/prod/software
at org.gcube.data.analysis.wps.repository.AlgorithmUpdater$WatcherThread.<init>(AlgorithmUpdater.java:88)
at org.gcube.data.analysis.wps.repository.AlgorithmUpdater.init(AlgorithmUpdater.java:54)
at org.gcube.data.analysis.wps.repository.GcubeAlgorithmRepository.<init>(GcubeAlgorithmRepository.java:32)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at org.n52.wps.server.RepositoryManager.loadAllRepositories(RepositoryManager.java:115)
at org.n52.wps.server.RepositoryManager.<init>(RepositoryManager.java:64)
at org.n52.wps.server.RepositoryManager.getInstance(RepositoryManager.java:170)
at org.n52.wps.server.CapabilitiesConfiguration.initProcessOfferings(CapabilitiesConfiguration.java:257)
at org.n52.wps.server.CapabilitiesConfiguration.initSkeleton(CapabilitiesConfiguration.java:245)
at org.n52.wps.server.CapabilitiesConfiguration.getInstance(CapabilitiesConfiguration.java:221)
at org.n52.wps.server.CapabilitiesConfiguration.getInstance(CapabilitiesConfiguration.java:180)
at org.n52.wps.server.CapabilitiesConfiguration.getInstance(CapabilitiesConfiguration.java:97)
at org.gcube.data.analysis.wps.WebProcessingService.init(WebProcessingService.java:183)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5247)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5530)
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.deployDirectory(HostConfig.java:1229)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1875)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Updated by Roberto Cirillo over 6 years ago
The problem is in the web.xml file that have the old folder inside... I'm going to update the web.xml and restart the instances
Updated by Roberto Cirillo over 6 years ago
- % Done changed from 0 to 100
All the instances have been updated. Please @g.panichi@isti.cnr.it could you perform the last check?
Updated by Giancarlo Panichi over 6 years ago
I can confirm that the proto algorithms are installed correctly.
Updated by Roberto Cirillo over 6 years ago
- Status changed from Feedback to Closed
