Skip to Content.
Sympa Menu

dynes-deployments - Re: [dynes-deployments] Problems with testing FDT

Subject: DYNES-Deployments

List archive

Re: [dynes-deployments] Problems with testing FDT


Chronological Thread 
  • From: Ty Bell <>
  • To:
  • Cc: "Gray, Charles" <>
  • Subject: Re: [dynes-deployments] Problems with testing FDT
  • Date: Thu, 2 May 2013 16:54:39 -0400
  • Authentication-results: sfpop-ironport05.merit.edu; dkim=neutral (message not signed) header.i=none

Charles, 

There was an upgrade to the OSCARS Resource Manager package on the Internet2 IDC that should have resolved this issue.

--Ty

On May 1, 2013, at 3:26 PM, Ty Bell <> wrote:

Looking at the error message for tufts.edu-296 in your OSCARS UI (https://idc.tufts.edu:8443/OSCARS/)


Error Report
Error Code RESERVATION_CREATE_FAILED
Error Message OSCARSSoapService.invoke:Exception connecting to listReservations on https://localhost:9006/OSCARS/resourceManager Message is: Could not send Message. on reservation tufts.edu-269 in Bandwidth PCE
Error Type RESERVATION_CREATE_FAILED


This message (though the source of the message isn't viewable) is being caused by an intermittent bug with the Internet2 IDC that we're working through with ESnet.



--Ty

On May 1, 2013, at 2:26 PM, Ramiro Voicu <> wrote:

Hi Charles,

The first warning can be safely ignored. It's only related with logging.
It does not affect the normal operation.

The FDT software requests the circuit to your local IDC and then polls
the status of the circuit using the circuit identifier (in this case: tufts.edu-269).
If the reported status becomes ACTIVE, within the deadline (~20 minutes),
the transfer/ping starts.

Regarding the circuit failure it may be related with the OSCARS upgrade,
which has been announced. I hope someone on the list may be able to give
more details about the circuit (tufts.edu-269) failure.

Your DYNES installation should be fine. The site has been tested before being commissioned.
The circuit failure is most likely from the upstream OSCARS/IDCs.

Thanks
-/Ramiro


On 05/01/2013 04:31 PM, Gray, Charles wrote:
Hello,

I'm working with Rice U to test our Dynes installation.  Since I was not involved in the initial setup of these servers, I have no idea what steps were completed re: setting up and testing circuits and FDT.

As the dynes user on our FDT server, I can successfully issue a dynesfdt command to list sites and receive status on 23 cached agents with a warning as follows:

WARNING: [ AppConfig ] No lia.Monitor.ConfigURL specified. Using JVM & local env.

Should I be concerned about this message?

Then I attempt a dynesfdt ping command to Rice (and later UPenn) and it ultimately returns the messages:

INFO: Waiting for reservation tufts.edu-269 -- Current OSCARS/IDC status: FAILED; Deadline in: 17 minutes 18 seconds
Apr 30, 2013 4:26:03 PM fdt.agent.session.CreateCircuitTask run
WARNING: OSCARS/IDC status 'FAILED' to be notified to agent session
Apr 30, 2013 4:26:03 PM fdt.agent.session.AgentSession circuitCreationFinished
WARNING: Circuit creation failed. Shutting down the session. Circuit Status: FAILED

What is the status of the server/service?  Where do I pick-up the installation/testing thread?

Thanks,
Charles Gray
Tufts Technology Services (TTS)
(617) 627-5327 (w)
(617) 627-3307 (f)
it.tufts.edu







Archive powered by MHonArc 2.6.16.

Top of Page