Troubleshooting Network Connectivity Issues for the Connector in Agile Central

Document ID : KB000073194
Last Modified Date : 14/03/2018
Show Technical Document Details
Introduction:
  • After initial install, connection fails to either Rally or the server that you are integrating with
  • Messages such as the following are recognized in the rallylog.log:
    • Cannot connect to 'rally1.rallydev.com'
    • Cannot connect to server name specified for the system to be integrated
Instructions:
  • Perform each of the following troubleshooting steps in succession to determine if there is an environmental issue causing the problem
  • These steps may be performed to either the Rally Server, or the server which houses the integration platform
  • If you are unclear on what action to perform if one of the tests is unsuccessful, consult with your IT & IT Networking teams for assistance

1) Disable 3rd-Party Security Applications

3rd-party security applications that may be running on the system for which the connector is installed can include but are not limited to:
  • Software Firewalls (This also includes Windows Firewall)
  • Antivirus Software
  • Spyware, Adware and Malware Protection
When performing network connectivity testing between the server and client systems, ensure that all programs that meet the above criteria are disabled.

2) "ping" Command:

The "ping" utility is used to determine if there is a network path from your client to Rally's server.
This may be executed from a Windows or Linux command-line depending on your integration client system.
 
Type the following command from command-line (Note: If you are testing an On-Premises version of Rally, change "rally1.rallydev.com" to your server name) : Successful "ping" Command Example:
 
Pinging rally1.rallydev.com [63.146.121.7] with 32 bytes of data: 

Reply from 63.146.121.7: bytes=32 time=39ms TTL=127 
Reply from 63.146.121.7: bytes=32 time=37ms TTL=127 
Reply from 63.146.121.7: bytes=32 time=40ms TTL=127 
Reply from 63.146.121.7: bytes=32 time=37ms TTL=127 

Ping statistics for 63.146.121.7: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
Minimum = 37ms, Maximum = 40ms, Average = 38ms 


Unsuccessful "ping" Command Example:

Pinging rally1.rallydev.com [63.146.121.7] with 32 bytes of data: 

Request timed out.

Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.146.121.7: 
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), 


3) "nslookup" Command:

The "nslookup" utility is used to query your site's DNS server for the IP address of Rally's server.
This may be executed from a Windows or Linux command-line depending on your integration client system.

Type the following command from command-line (Note: If you are testing an On-Premises version of Rally, change "rally1.rallydev.com" to your server name) :
Successful "nslookup" Command Example:

Server: efg-corpdomain-01.domain.com 
Address: 10.30.0.28 

Name: rally1.rallydev.com 

Address: 63.146.121.7 

Unsuccessful "nslookup" Command Example:

Server: efg-corpdomain-01.domain.com 
Address: 
10.30.0.28 

*** dsc-corpdom-01.f4tech.com can't find rally1.rallydev.com: Server failed

-OR-

Server: efg-corpdomain-01.domain.com 
Address: 10.32.0.13 

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
   timeout was 2 seconds.
*** Request to dsc-corpdom-01.f4tech.com timed-out

 

4) Using a Proxy Server

Please refer to the following KB article:

Configuring a Proxy Server via Operating System Environment Variable for Connectors


5) "telnet" Command:

Using the "telnet" utility will allow for testing on the port-level to ensure there are no firewall rules restricting access.
This may be executed from a Windows or Linux command-line depending on your integration client system. If when
running in Windows it reports "telnet command not found", refer to your operating systems documentation for how
to enable this functionality.

Type the following command from command-line (Note: If you are testing an On-Premises version of Rally, change "rally1.rallydev.com" to your server name) :
Successful "telnet" Command Example:

Trying 63.146.121.7... 
Connected to rally1.rallydev.com
Escape character is '^]'. 
  • At this point, telnet is waiting for input from you
  • Enter this line, and hit enter/return twice
    • GET / HTTP/1.0 
If you have connected to Rally successfully, you should see output similar to this: 

HTTP/1.1 302 Found 
Date: Tue, 15 May 2012 21:53:43 GMT 
Server: Apache 
Location: https:/// 
Content-Length: 193 
Connection: close 
Content-Type: text/html; charset=iso-8859-1 

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 
<html><head> 
<title>302 Found</title> 
</head><body> 
<h1>Found</h1> 
<p>The document has moved <a href="https:///">here</a>.</p> 
</body></html> 
Connection closed by foreign host. 
  • To exit telnet, enter "Control-[" (hold down the control key while pressing "]"), then enter "quit": 
^] 
telnet> quit 
Connection closed. 


Unsuccessful "telnet" Command Example:

Trying 63.146.121.7...Could not open connection to the host, on connect failed


6) "traceroute" Command:

The traceroute command will show a listing of each network "hop" required to send a packet from your system to the destination host.
This command is especially effective for understanding if there is a problem with your ISP, or even a latency issue.

Type the following command from command-line (Note: If you are testing an On-Premises version of Rally, change "rally1.rallydev.com" to your server name) : Successful "traceroute" Command Example:

Tracing route to rally1.rallydev.com [63.150.172.9] 
over a maximum of 30 hops: 
1 2 ms <1 ms <1 ms 10.0.2.2 
2 2 ms 1 ms 1 ms 10.32.33.1 
3 6 ms 5 ms 3 ms dvr-edge-12.inet.qwest.net [207.225.124.209] 
4 5 ms 7 ms 8 ms dvr-core-02.inet.qwest.net [205.171.10.65] 
5 3 ms 11 ms 3 ms hlr-core-01.inet.qwest.net [67.14.15.2] 
6 168 ms 52 ms 194 ms hlr2-cntr-01.inet.qwest.net [205.171.18.214] 
7 * * * Request timed out. 
8 6 ms 13 ms 6 ms qd-sweb-01.rallydev.com [63.150.172.9] 
Trace complete. 


Unsuccessful "traceroute" Command Example:

Tracing route to rally1.rallydev.com [63.150.172.9] 
over a maximum of 30 hops: 
1 2 ms <1 ms <1 ms 10.0.2.2 
2 2 ms 1 ms 1 ms 10.32.33.1 
* * * Request timed out. 
* * * Request timed out. 
* * * Request timed out. 
* * * Request timed out. 


7) "curl" Command (Linux):

"curl" is a tool to transfer data from or to a server, using one of the supported protocols (in this case HTTP)

Type the following command from command-line (Note: If you are testing an On-Premises version of Rally, change "rally1.rallydev.com" to your server name) : Successful "curl" Command Example: 

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 
<html><head> 
<title>302 Found</title> 
</head><body> 
<h1>Found</h1> 
<p>The document has moved <a href="https://rally1.rallydev.com/">here</a>.</p> 
</body></html> 


8) Workspace/Project Print via Ruby Script:

Run the following Ruby script, exactly as is. There is no need to change the username, password or URL as they are a valid read-only user: 

(Note: If you are testing an On-Premises version of Rally, change "demo.rallydev.com" to your server name, 
and change the $un / $pw to a Username and Password which are valid for your server) 

#---Begin code 
require 'rubygems'; require 'rally_rest_api' 
$un = "evan@acme.com
$pw = "RallyON!" 
r=RallyRestAPI.new(:base_url=>"https://demo.rallydev.com/slm",:username=>$un,:password=>$pw) 
puts "Username: '#{r.user.name}', Subscription: '#{r.user.subscription.name}'" 
r.user.subscription.workspaces.each_with_index do |w,i| 
puts "Workspace #{i+1} - #{w}" 
w.projects.each_with_index do |p,j| puts " Project #{j+1} - #{p}"; end 
end 
#---End code 
  • When the above Ruby code runs, it should connect to Rally and print the workspaces and projects: 
C:\Documents and Settings\Administrator>ruby rubytest.rb 
Username: 'Evan', Subscription: 'Company 1' 
Workspace 1 - Healthcare Story Pattern 1 
Project 1 - Big Healthcare 
Project 2 - ChartFX 
Project 3 - Global IT Project 
Project 4 - Ultrasound Device 2000X 
Project 5 - IT Project Agile Team 
Project 6 - Compliance Team 
Project 7 - Display Team 
Project 8 - Image Processing Team 
Project 9 - Software Control System Team 
Project 10 - Transducer Firmware Team 
Workspace 2 - Healthcare Story Pattern 2 
Project 1 - Big Healthcare 
.... 
Workspace 3 - Integrations 
Project 1 - Online Store 
.... 
Workspace 4 - Schneider 
Project 1 - Shopping Team 
.... 
Workspace 5 - Workspace #2 
Project 1 - Shopping Team 
.... 
Workspace 6 - Workspace #3 
Project 1 - Shopping Team 
.... 
Workspace 7 - Sprinting Safaris 
Project 1 - Shopping Team 
.... 


Type the following command from command-line:
  • gem install builder rally_rest_api 
Fetching: builder-3.0.0.gem (100%) 
Successfully installed builder-3.0.0 
Fetching: rally_rest_api-1.0.3.gem (100%) 
Successfully installed rally_rest_api-1.0.3 
2 gems installed 
Installing ri documentation for builder-3.0.0... 
Installing ri documentation for rally_rest_api-1.0.3... 
Installing RDoc documentation for builder-3.0.0... 
Installing RDoc documentation for rally_rest_api-1.0.3... 


You can verify the required Ruby Gems are installed via this command: 
  • gem list 

*** LOCAL GEMS *** 

builder (3.0.0) 
rally_rest_api (1.0.3) 


A pre-packaged (including Ruby) Windows version of the above script can be found at: