Opened 6 years ago

Closed 5 years ago

#1953 closed defect (fixed)

petascope_insertdemo.sh wrong secore port

Reported by: Dimitar Misev Owned by: dkamov
Priority: minor Milestone: 9.8
Component: petascope Version: development
Keywords: Cc:
Complexity: Medium

Description

I'm running embedded petascope on 8080 and secore on 8081. On petascope_insertdemo.sh I get this (in couple of places it's using wrong secore port 8080):

petascope_insertdemo.sh: Petascope service endpoint is: http://localhost:8080/rasdaman/ows
petascope_insertdemo.sh: Secore service endpoint is: http://localhost:8080/def

petascope_insertdemo.sh: Starting to ingest example coverages to petascope...
petascope_insertdemo.sh: Ingesting AverageChlorophyll to petascope by wcst_import...Collected files: ['/opt/rasdaman/share/rasdaman/petascope/petascope_insertdemo_data/3D_Timeseries_Irregular/SCALED_CHLORA_2015-01.TIFF', '/opt/rasdaman/share/rasdaman/petascope/petascope_insertdemo_data/3D_Timeseries_Irregular/SCALED_CHLORA_2015-02.TIFF', '/opt/rasdaman/share/rasdaman/petascope/petascope_insertdemo_data/3D_Timeseries_Irregular/SCALED_CHLORA_2015-03.TIFF', '/opt/rasdaman/share/rasdaman/petascope/petascope_insertdemo_data/3D_Timeseries_Irregular/SCALED_CHLORA_2015-04.TIFF']...
The recipe has been validated and is ready to run.
Recipe: time_series_irregular
Coverage: AverageChlorophyll
WCS Service: http://localhost:8080/rasdaman/ows
Operation: INSERT
Subset Correction: False
Mocked: False
Track files: True
Runtime error: Failed parsing the compound crs at: http://localhost:8081/def/crs-compound?1=http://localhost:8080/def/crs/OGC/0/AnsiDate&2=http://localhost:8081/def/crs/EPSG/0/4326. Detailed error: Runtime error: Failed parsing the crs at: http://localhost:8080/def/crs/OGC/0/AnsiDate. Detail error: Runtime error: Failed opening connection to 'http://localhost:8080/def/crs/OGC/0/AnsiDate'. Check that the service is up and running.Detail error: .

Port 8080 is not used anywhere in secore.properties, and in petascope.properties only for the server.port.

Change History (6)

comment:1 by Dimitar Misev, 6 years ago

I think it's because petascope_insertdemo.sh doesn't support separate endpoints, you can set one endpoint for both petascope and secore.

The best is to remove this endpoint option and read the endpoints from the properties files.

comment:2 by Bang Pham Huu, 6 years ago

Priority: majorminor

It should use secore configured in petascope.properties not from port in secore.properties file because port only has effect if running as an embedded application.

comment:3 by Bang Pham Huu, 5 years ago

Owner: changed from Bang Pham Huu to dkamov
Status: newassigned

comment:4 by Dimitar Misev, 5 years ago

It should use secore configured in petascope.properties not from port in secore.properties file because port only has effect if running as an embedded application.

There's already code in start_rasdaman.sh that reads the port from petascope.properties or secore.properties so it can be copied. The ingredients files need to be updated in this case.

comment:5 by Bang Pham Huu, 5 years ago

@Dragi: The original script is at rasdaman/applications/petascope/coverages_example/petascope_insertdemo.sh.in and you need to update SECORE_URL=$SERVICE_ENDPOINT/def with the replacement for port 8080 from the configured value for key secore_urls= in /opt/rasdaman/etc/petascope.properties (default this value is: http://localhost:8080/def).

This value can be changed to something like http://localhost:8081/def, hence, the port is '8081'.

comment:6 by dkamov, 5 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.