KBEA-00072 - Fixing a cygwin mounts table in improper format condition

Article ID:360033190451
1 minute readKnowledge base
On this page


During a build, one agent reports the following:

> WARNING EC2094: Problem resolving cygwin mounts: couldn’t read cygwinMounts table:
> improper format

There have been no Cygwin changes to this node (in question), why does one agent report this and not others?

Cygwin "mount" command shows (on all nodes, including the one reporting the error):

c:\tools\win32\usr\include on /usr/include type system (binmode)
c:\tools\win32\bin on /bin type system (binmode)
c:\tools\win32\bin on /usr/bin type system (binmode)
c:\tools\win32\lib on /usr/lib type system (binmode)
c:\tools\win32 on / type system (binmode)
c:\tmp on /tmp type system (binmode)
c: on /cygdrive/c type system (textmode,noumount)
p: on /cygdrive/p type system (textmode,noumount)
y: on /cygdrive/y type system (textmode,noumount)
z: on /cygdrive/z type system (textmode,noumount)


Be sure the Cygwin mounts from all of the agents show the same text mode, and are accessible to the build and agent user accounts. If so, it is possible that the ecagent state file has been corrupted. To work around this:

  1. Stop the agent processes on the node.

  2. Remove the c:\Ecloud\ecagent.state file.

  3. Restart the agents and run a build.

The ecagent.state file will rebuild itself with the proper format.

Applies to

  • Product versions: all

  • OS versions: Windows