x
login Signup

ElectricFlow server to agent communication information

I am having sporadic communication failures between the ElectricFlow server and ElectricFlow agents (on VMs). The failure I see during pingResource is the following...

 <alive>0</alive>
 <code>AGENT_IO_ERROR</code>
 <details>Unspecified network error reaching agent machine: Unspecified network error reaching agent machine</details>
 <hostOS>Microsoft Windows [Version 6.3.9600]</hostOS>
 <hostPlatform>windows</hostPlatform>
 <message>Unspecified network error reaching agent machine</message>
 <pingToken>131548883984235070</pingToken>
 <protocolVersion>6</protocolVersion>
 <state>down</state>
 <time>2017-11-20T22:44:08.539Z</time>
  

Telnet to the Agent machine with the Agent port (7800) is successful

netstat -a shows port 7800 is listening

The agent is running

One question I have is why this appears in the agent log...when the configured port is 7800...

 2017-11-20T12:54:36.270 | INFO  | 0xc91ee0   | Agent user: yytcadm
 2017-11-20T12:54:36.863 | INFO  | 0xc91ee0   | PingRequest::init: sEcProxy: C:/apps/Electric Cloud/ElectricCommander/bin/ecproxy
                   sPlatform: windows
                         sOS: Microsoft Windows [Version 6.1.7601]
 2017-11-20T12:54:36.863 | DEBUG | 0xc91ee0   | About to map persistent drives
 2017-11-20T12:54:36.863 | DEBUG | 0xc91ee0   | Done with persistent drives
 2017-11-20T12:54:37.034 | DEBUG | 0xc91ee0   | Pre-existing drive mappings:
 
 2017-11-20T12:54:37.112 | INFO  | 0xc91ee0   | Successfully listening on port 49175.



Plus this...

 2017-11-20T12:54:36.129 | INFO  | 0xc91ee0   | --- Begin processing config file ---
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | port: 7800
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | pluginsPath: C:/apps/Electric Cloud/ElectricCommander/plugins
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | artifactCache: C:/apps/Electric Cloud/ElectricCommander/artifact-cache
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | logFile: C:/apps/Electric Cloud/ElectricCommander/logs/agent/agent.log
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | logMaxSize: 26214400 bytes
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | logMaxFiles: 40
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | unixShellPattern: (.*[/\])?(sh|bash)(\.exe)?
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | keyFile: C:/apps/Electric Cloud/ElectricCommander/conf/agent.key
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | certFile: C:/apps/Electric Cloud/ElectricCommander/conf/agent.crt
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | verifyPeer: 0
 2017-11-20T12:54:36.145 | WARN  | 0xc91ee0   | Error on line 114 of config file: caFile must have a value.
 2017-11-20T12:54:36.145 | WARN  | 0xc91ee0   | Error on line 115 of config file: caPath must have a value.
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | --- End processing config file ---
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | --- Begin processing command line options ---
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | configuration file: "C:/apps/Electric Cloud/ElectricCommander/conf/agent.conf"
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | embedded mode, talk-back port 6800
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | stop file: "C:/apps/Electric Cloud/ElectricCommander/logs/agent.stop"
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | Resetting listener port to ephemeral port since we're in embedded mode.
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | Forcing daemonize=0 since we're in embedded mode.
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | Forcing proto=http since we're in embedded mode.
 2017-11-20T12:54:36.145 | INFO  | 0xc91ee0   | --- End processing command line options ---
 2017-11-20T12:54:36.239 | INFO  | 0xc91ee0   | Agent (32-bit) 6.0.5.108377, build build_6.0_108377_OPT_2016.07.13_12:10:17 started with the following settings:
    protocol:      http
    listener port: 0
    daemonize:     0
    stopFile:      'C:/apps/Electric Cloud/ElectricCommander/logs/agent.stop'







I am trying to gather as much information about the communication (protocals, ports, etc...) between the two to provide to our networking team.

avatar image By prgerth 57 asked Nov 21, 2017 at 05:16 PM
more ▼
(comments are locked)
10|750 characters needed characters left

2 answers: sort voted first

Hi prgerth,

I have noticed a similar behavior (sporadic communication failures between the EF server and EF agents, AGENT_IO_ERROR, Unspecified network error reaching agent machine: Unspecified network error reaching agent machine).

You may try to set the 'Agent Host Name' as either the IP or the Fully Qualified Name (FQN) of this agent.

Good luck

avatar image By waldo.ramirez 0 answered Feb 13 at 09:35 AM
more ▼
(comments are locked)
10|750 characters needed characters left

Hello prgerth,

Another possibility: as the netstat -a shows that the port 7800 is listening in the agent, you may check if the EF server already has 'ESTABLISHED' connections with this agent in this port. Probably there are already connections that were not closed and create conflict to establish new connections.

Best regards, Waldo

avatar image By waldo.ramirez 0 answered Jun 01 at 12:12 PM
more ▼
(comments are locked)
10|750 characters needed characters left
Your answer
toggle preview:

Up to 8 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.