| Issue Number | 4386 |
|---|---|
| Summary | [Gauss QA Testing] failure sending command error when searching in XMetal |
| Created | 2018-01-16 12:01:23 |
| Issue Type | Bug |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Osei-Poku, William (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2018-06-28 14:59:39 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.219791 |
We are getting a "failure sending command: A connection with the server could not be established" error when doing a CDR search.
I have attached a screenshot.
I haven't been able to reproduce this problem.
I am getting the error message each time I search. I am not sure if there is a way for me to let you see it.
You may need to consult with your networking folks. Neither Volker nor I are seeing the failure. I'll try from the VPN when I get home.
Sure. I will ask them to take a look. The error is happening on the site-to-site VPN and not Cisco AnyConnect client so your VPN may not help (have not tried it on the Cisco AnyConnect client yet).
I just tried it on the Cisco AnyConnect client it worked without any problem. I suspect that this is happening because the new API servers have not been added to the site-to-site VPN. Would you be able to provide me with the IP addresses of all the AP Servers? I need to create a ticket to add them before the Guass is installed on PROD.
~bryanp: Could you help us figure out how this would work, given that (as I am led to believe) the magic which CBIIT does to route traffic using the F5 is not IP-address--based? Basically, William's working from a site-to-site VPN, and from what he is telling me, I gather his networking folks need IP addresses.
Thanks!
~bryanpIncreased the priority of this ticket (regarding the request for IP addresses). We would need to schedule changes with NIH IT and it usually takes a long time for them to implement such changes so it may impact when Gauss can be installed on PROD.
DNS lookup of cdrapi-qa.cancer.gov gives 10.133.200.201. In general, you can have your network folks do the same thing I just did, using the API Server host name that appears when you select a tier in the CDR loader.
Hi, William. What's the progress on this ticket?
I submitted the ticket a while back and the NIH network team have scheduled February 15 to implement the changes. It should be right around when Gauss is planned for PROD so we should be fine.
The change to the site-to-site VPN is still ongoing. I am working with the ISSO office to renew the ISA/MOU for the VPN tunnel.
Moving this ticket to Hawking
Unless there's a component of which I'm unaware, I don't think this ticket is dependent on any release.
That is right. Moving it to the Release Independent queue.
~oseipokuw: What is the relationship between this ticket and OCECDR-4275?
This ticket is for fixing the problem with the new update server (introduced in GAUSS) that prevents us from updating documents in XMetal, while connected on the site-to-site VPN. While OCECDR4275 has to do with the display of the tier names in XMetal. But for OCECDR4275 being complicated by the introduction of the new update server, these two tickets shouldn't be related in any way.
Meanwhile, we are still in the process of getting approval from NIH CISO to include the update server on the site to site VPN.
The problem has been resolved by adding the new API server IPs to the CIAT site-to-site VPN.
| File Name | Posted | User |
|---|---|---|
| failuresendingcommanderror.JPG | 2018-01-16 12:00:51 | Osei-Poku, William (NIH/NCI) [C] |
Elapsed: 0:00:00.001445