Ticket #288 (closed new task: fixed)

Opened 6 months ago

Last modified 5 weeks ago

SDO6 testing

Reported by: jennifer Owned by: jennifer
Priority: normal Milestone:
Component: SDAC Servers Version: 1.4
Severity: normal Keywords:


Goddard server sdo6 needs testing from extermal sources for both load testing and basic "can I see you" testing. This needs to be done in Python and IDL.

Change History

comment:1 Changed 3 months ago by ed

Three types of test need to be done to confirm sdo6 will fully function in production.

1) Website Query Test:

Adjust the Registry file on vso1 to permit testing of sdo6 with an AIA query.

Tested successfully once the line "Require all granted" was added to Apache's perl.conf config file for directory /var/www/mod_perl.

2) Python query from SunPy:

Adjusted my installation of SunPy to route the query to my local test VSO where, in turn, the AIA query is routed to sdo6 instead of sdo4. SOAP Query does go off to sdo6 correctly, gets redirected to use https correctly, then fails due to a handshake error in SSL.

Checked the CAs on sdo6 via openssl s_client -connect sdo6.nascom.nasa.gov:443 and they seem fine. The issue may be local to my test env.

Setting up a 2nd test env on my CentOS 6.8 partition for further testing.

3) IDL/SSW (SolarSoft) query:

Adjusted my SSW configuration to use sdo6. Initial http query hits sdo6, gets redirected correctly to https. Final call to the main mod_perl CGI script JSOCi never occurs on sdo6, whereas it does on sdo4. No error messages in either ssl_error_log or modsec_audit.log occur.

Cleared up a couple of warnings in the Apache ssl_error_log after moving the ScriptAlias? commands further up in the perl.conf config file.

Once the JSOCi script is executed, we should get data returned, once Postgres can be logged into.

Continuing to work on debugging the IDL/SSW query.

NOTE: AIA query used is for 12/17/17, for which we have data on both sdo4 & sdo6.

comment:2 Changed 3 months ago by ed

Update to Test #2 (SunPy):

Got the new test env Apache installation to correctly respond to remote queries via browsers. Testing uncovered an additional test that will need to be added to the VSO install script to test for the "other" execute privilege on the parent directory of the target install folder.

Now getting an error from the Python query lookup during the first "hop" to the test env, before the final "hop" to sdo6.

comment:3 Changed 3 months ago by alisdair

  • Status changed from new to assigned

comment:4 Changed 2 months ago by ed

Completed testing of SunPy and IDL/SSW on sdo6.

Both work as expected.

sdo6 is ready to be moved into production once the SUMS DB on sdo6 is ready. This final move will be done after Jennifer gets back from vacation.

Test #2 SunPy:

Completed setting up Python test env on Linux machine to test end-to-end a SunPy/VSO setup. One key point in setting up a 2nd Python Linux that was independent of the system-supplied Python (needed since the system-supplied one was too old), was configuring and building Python using gcc compiler option "rpath" to point at runtime the location of the new libraries for the new Python binary. The second point was to update the jsoc.xml registry file to use as an endpoint the JSOCi CGI script in the mod_perl folder instead of the cgi-bin folder as is done on sdo4.

With those 2 changes the test query of AIA data for 12/17/17 returned the same data from SunPy as obtained from the web interface.

Test #3 IDL/SSW:

Adjusting my test IDL/SSW setup to send the AIA query to vso1 instead of directly to sdo6 resulted in the same AIA query returning the same test results as the web interface and SunPy.

Working now on documenting a checklist of items for activating a new VSO/NetDRMS server, together with details on techniques for testing the server.

comment:5 Changed 6 weeks ago by ed

Working with Jennifer and Marc on the final checklist for moving sdo6 into production and making sdo4 the backup.

comment:6 Changed 5 weeks ago by ed

sdo6 was moved into production on 8/15/18 and the JMD is now running and all tests completed successfully.

Any issues going forward will be logged to new tickets.

This one can be closed.

comment:7 Changed 5 weeks ago by ed

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.