Agent incompatible due to no UNC/SSH access (v 2212)

Continua CI Discussion
1

I have an agent on a separate machine which is showing as incompatible with the message:

The agent does not have access to the server via UNC or SSH.

The computer on which the agent is deployed can see the Continua server share and the effective permissions for the agent service account are showing full control.  That is the case using the path shown in Data Share in Administration | Continua Server | Properties.  I'm using version 2212 (agent and server).

Any ideas what to try next?

Thanks

Sean



2

Any update on this guys?

3

Hi, sorry about that. For some reason this question managed to fall through the cracks.

This looks like it may be a problem with ports and your firewall. Basically, the only time an agent talks to the server is to register with the Server every minute or so to tell that server that it is still online. All other communication originates from the server and the server tells the agent to do things.

Within this context, it looks like the agent successfully registered with the server but the server cannot talk back to the agent.

Check that your firewall is configured correctly so that all incoming and outgoing ports are allowed. Have at a look at this page in our wiki for a list of default ports:

http://wiki.finalbuilder.com/displa…d+Security

Note that you will have to configure both the incoming and outgoing ports for both the server and agent. Using the default ports, you will need to grant access to the following ports

Server: Incoming: 9000 Outgoing: 9002

Agent: Incoming: 9002 Outgoing: 9000 

4

Hi Dave

Thanks for getting back with all the info. I’ve gone through that and it’s still not working for me I’m afraid. I didn’t have all the ports open on the servers before, and the server config had 9000 instead of 9002 for the agent’s port. I have updated the config and firewalls now to the specs you mention, and checked it all against the documentation.

I’ve also tested that each server can see the other one using a TcpClient (code below) and the server can connect to the incoming port of the other server. The account used by the agent can still see the UNC share from the agent and has full rights in the effective permissions.

Is there anything else I can try?

Thanks

Sean

bool PortOpen(string host, int port)
{
var client = new TcpClient();
client.SendTimeout = 1;
client.ReceiveTimeout = 1;
client.Connect(host, port);
return client.Connected;
}

5

Hi Sean

If you look at the Agent Properties for that agent (click on the number of properties for that agent in the agents view) do you see the following properties :

serverfiletransport.sshavailable
serverfiletransport.uncavailable

Are there any properties for that agent?

The fact that the Agent is seen by the server suggests the firewall settings for Agent to Server communication is ok, however the agent properties are collected by the server requesting them, so if there are zero properties then that would suggest and issue with the server connecting to the agent.

6

Hi Vincent

It does look like the firewall is okay from the tests I did here. There are 55 properties showing for the agent. The serverfiletransport* properties that I can see are:

serverfiletransport.forcessh False
serverfiletransport.sshavailableFalse
serverfiletransport.uncavailableTrue

I’m not sure if this is relevant, but I have to keep refreshing the properties when I open them. After I switch back to the Agents in the left nav, then go back into the agent the properties is showing as 0 until I refresh.

Thanks

Sean

7

Any update on this one guys?

8

Hi Sean, the errors you are seeing are really strange and we are not sure what could be causing them.

Firstly, can you turn debugging on and see if there are any hidden errors being thrown? Instructions for enabling debugging can be found:

http://wiki.finalbuilder.com/displa...leshooting

Once the agent has attempted to connect a couple of times (agents attempt to connect to the server every 30 seconds), stop the service, grab the log and can you then send it through to us at support@finalbuilder.com?

If there is no glaring issues in the log, we may have to use goto meeting (or similar product) to have a look at your system and figure out why the agent cannot communicate with the server

9

Log file sent - thanks again!