x
login Signup

ElectricAccelerator ERROR EC1050: wrong Electric Make protocol version

Some users are seeing this error:

ERROR EC1050: agentname:

The protocol version of Electric Make (X) is incompatible with the software installed on the Electric Cloud cluster 192.168.6.8 (Y). You need to upgrade your copy of Electric Make; aborting build. What does this mean and how do I resolve this?
avatar image By prefontaine 456 asked Jul 13, 2012 at 04:39 PM
more ▼
(comments are locked)
10|750 characters needed characters left

1 answer: sort voted first

This error message indicates that the build was submitted using a different version of Electric Make than is installed on the cluster nodes. In order to ensure correct operation, ElectricAccelerator requires that the version of emake used to submit the build is available on the cluster nodes used by the build.

Typically this error appears when you add new nodes to your cluster and install the latest version of ElectricAccelerator on those nodes -- in that case, only the latest version of Electric Make is available on the cluster. In comparison, when you upgrade a cluster node, the old version of Electric Make is preserved, so that users using the old version can still use that node. In order to resolve this, you can either install the old version of ElectricAccelerator first, then upgrade to the new version; or you can install the Electric Make backwards compatibility package on the new nodes. This bundle contains just those bits necessary to ensure compatibility with users using old versions of Electric Make. You may install as many backwards compatibility packages as necessary to accommodate your users.

Backwards compatibility packages are available for every legacy release of ElectricAccelerator from the Electric Cloud FTP site (ftp.electric-cloud.com).

Installation on a single agent machine

  1. Open a terminal window.

  2. Change to the Electric Cloud installation directory (for example c:/ECloud or /opt/ecloud).

  3. Download the appropriate set of archive files (for example, i686_win32_bcp.zip [all previous eMake versions] or i686_win32_5.2.5_bcp.zip [a single eMake version]) from the Electric Cloud FTP site: emake_archive/.

  4. Unpack the archive in the current directory (). For Windows, make sure the extraction destination is without any sub-directories, such as c:/ECloud.

  5. Repeat the process for each new agent machine.

Installation on multiple agent machines

  1. Open a terminal window.

  2. Change to a temporary directory (such as /var/tmp, or c:/Windows/Temp).

  3. Download the appropriate set of archive files (for example, i686_win32_bcp.zip [all previous eMake versions] or i686_win32_5.2.5_bcp.zip [a single eMake version]) from the Electric Cloud FTP site: emake_archive/.

  4. Unpack the archive in the current directory. For Windows, make sure the extraction destination is the temporary directory (or the directory from step 2) without any sub-directories, such as c:/Windows/Temp.

  5. Run (as an example): clusterupload --cm <cmname> i686_win32 c:/ECloud.

Note: For additional information about how to indicate a range/group of hostnames/IPs for the clusterexec command, see the online help system in the Cluster Manager GUI.

Protocol changes

Occasionally, ElectricAccelerator may contain protocol changes that make it necessary to update the eMake version on the build machines. Starting with ElectricAccelerator 6.0 an eMake-only installer is available for this type of update.

Customizing the version mismatch warning

On the Cluster Manager, modify file //conf/version_mismatch.txt. It may be necessary to bounce the Cluster Manager after changing the warning message.

avatar image By aaron scheiber 3.7k answered Jul 13, 2012 at 05:04 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.