Actions
Incident #12915
closedRandom authorization error when invoking DM
Status:
Closed
Priority:
Normal
Assignee:
Category:
High-Throughput-Computing
Target version:
Start date:
Nov 20, 2018
Due date:
Nov 20, 2018
% Done:
100%
Estimated time:
Infrastructure:
Production
Description
Randomly, DataMiner cannot be contacted because it reports an authorization error, which prevents the service to be invoked in the PerformFISH-KPIs VRE:
Error (400) : this resource cannot process this request because it is malformed Stacktrace: org.gcube.smartgears.handlers.application.request.RequestException: DataMiner cannot be called in scope /d4science.research-infrastructures.eu/FARM/PerformFISH-KPIs at org.gcube.smartgears.handlers.application.request.RequestError.toException(RequestError.java:110) at org.gcube.smartgears.handlers.application.request.RequestError.fire(RequestError.java:94) at org.gcube.smartgears.handlers.application.request.RequestValidator.validateScopeCall(RequestValidator.java:98) at org.gcube.smartgears.handlers.application.request.RequestValidator.handleRequest(RequestValidator.java:59) at org.gcube.smartgears.handlers.application.RequestHandler.onEvent(RequestHandler.java:58) at org.gcube.smartgears.handlers.application.RequestHandler.onEvent(RequestHandler.java:21) at org.gcube.smartgears.handlers.Pipeline.forward(Pipeline.java:65) at org.gcube.smartgears.handlers.Pipeline.forward(Pipeline.java:72) at org.gcube.smartgears.managers.RequestManager.doFilter(RequestManager.java:86) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) 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)
I'm using this call to test:
http://dataminer.garr.d4science.org/wps/WebProcessingService?request=Execute&service=WPS&Version=1.0.0&gcube-token=<token>&lang=en-US&Identifier=org.gcube.dataanalysis.wps.statisticalmanager.synchserver.mappedclasses.transducerers.PERFORMFISH_DATA_VALIDATOR_V2&DataInputs=CompanyData=https%3A%2F%2Fdata.d4science.org%2Fshub%2Fa858c0cb-5d88-4ac9-892d-335e2a7fe949;Template=HATCHERY_INDIVIDUAL;Overwrite=true;LatestCompanyData=https%3A%2F%2Fdata.d4science.org%2Fshub%2Fa858c0cb-5d88-4ac9-892d-335e2a7fe949;
Updated by Giancarlo Panichi almost 7 years ago
I did some tests and the machines are these:
http://dm-192-168-100-3.garr.d4science.org/ http://dm-192-168-100-7.garr.d4science.org/ http://dm-192-168-100-13.garr.d4science.org http://dm-192-168-100-14.garr.d4science.org http://dm-192-168-100-6.garr.d4science.org/
Updated by Giancarlo Panichi almost 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
@roberto.cirillo@isti.cnr.it has canceled the status of the services and now these machines are back to work properly.
Updated by Giancarlo Panichi almost 7 years ago
- Due date set to Nov 20, 2018
- Status changed from In Progress to Resolved
Updated by Giancarlo Panichi almost 7 years ago
- Status changed from Resolved to Closed
Actions