|
Answer: That message means that either another ECS ("Enabling Communications System") session is active or it means that a previous ECS session ended abnormally, leaving an orphan lock file.
If you verify that another ECS session is truly active, wait until that session ends then try launching a new ECS session.
If you verify that another ECS session is truly not active, delete the file "ecsActive" from the "/ecs/" directory. After deleting "ecsActive", run your ECS session again. (Note: Unix filenames are case-sensitive ... the letter "A" in "ecsActive" is uppercase.)
Background: To prevent more than one ECS session from starting accidentally, a "lock file" ("ecsActive") is used. Near the beginning of an ECS session, the "/ecs/" directory is checked for the presence of "ecsActive". If it is not found, "ecsActive" is created and the communications session continues. At the end of the session, "ecsActive" is deleted.
If, on the other hand, an "ecsActive" file is found in the "/ecs/" directory when the communications session is launched, you get the error message in question and the session ends.
If you find the "ecsActive" file in the "/ecs/" directory even though there is no communication session in progress, this means that a previous session failed to reach the point where it does its "housekeeping" so that the "ecsActive" file is not deleted. This can happen if the system crashes during a session or if a user aborts a session (using "CONTROL-C" or the "kill" command for instance).
|