Project

General

Profile

Task #8597

MNDeployment #2564: ORNL DAAC

DAAC: not updating

Added by Amy Forrester almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
2018-05-24
Due date:
% Done:

100%

Story Points:

Description

Apparently the node is not being harvested, we need to determine if that actually is the case and if so, diagnose why.need to determine if that actually is the case and if so, diagnose why.

History

#1 Updated by Dave Vieglais almost 6 years ago

  • % Done changed from 0 to 30
  • Status changed from New to In Progress

Member Node URLs are listed in the CN node list:

https://cn.dataone.org/cn/v2/node

Which shows the DAAC MN URL to be:

http://mercury-ops2.ornl.gov/ornldaac/mn

Accessing DataONE service endpoints at that location, e.g.:

http://mercury-ops2.ornl.gov/ornldaac/mn/v1/node/

returns a redirect to:

https://mercury-ops2.ornl.gov/ornldaac/mn/v1/node/

which then returns a 404 error.

The registered node is not operational, hence it is not being harvested.

#2 Updated by Amy Forrester almost 6 years ago

  • Assignee changed from Dave Vieglais to Rob Nahf

Rob will jump in to help DAAC diagnose why they aren't working.

#3 Updated by Amy Forrester almost 6 years ago

6/20/18: (Rob, Amy) call with Alison Boyer & Daine Wright wrightdm@ornl.gov
* something wrong with their endpoint. The server is reachable, but their DataONE API isn't reachable.

#4 Updated by Amy Forrester over 5 years ago

6/21 - most probable scenario to to re-deploy MN with GMN. Setting up planning meeting.

#5 Updated by Amy Forrester over 5 years ago

  • % Done changed from 30 to 100
  • Status changed from In Progress to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)