|
(→Error Examples)
|
(→Duplicate Agents)
|
| Line 130: | |||
| <pre>result.ser (No such file or directory)</pre> | <pre>result.ser (No such file or directory)</pre> | ||
| <pre>result.ser (The system cannot find the path specified)</pre> | <pre>result.ser (The system cannot find the path specified)</pre> | ||
| + | == Background == | ||
| + | Each agent is assigned a unique endpoint ID value. When the agents connect to the server, the server reads these endpoints and stores it in the database. Each agent is then referenced by its endpoint, and when work is to be dispatched to an agent, it is identified by the endpoint. This explains why you can have two agents with the same name, but different agents altogether because their endpoints are different. If somehow two agents connect to the server with the same endpoint, chaos ensues when trying to run any builds. Examples of how two agents might connect with the same endpoint on the same server include: | ||
| + | * '''PRE-3.8''': The same agent was started twice with ah3agent run/start | ||
| + | * '''PRE-3.8''': The same agent was started twice under different user accounts | ||
| + | * '''PRE-3.8''': The same agent was started as a ''Windows Service'' and from the ''command prompt'' | ||
| + | * A (virtual) machine has been cloned across the network and the agent on that machine contains the same '''endpoint ID''' as another VM's agent. Both agents are started and connected to server. | ||
| + | * Two different agents connected to the server have manually had their installed.properties file edited to have an identical '''endpoint ID'''. | ||
| + | * On a ''very rare case'', the agent-installer could randomly generate an '''endpoint ID''' that matches another agent. | ||
