Check if there are network related issues which results in the host resolution failing. You may notice some exceptions in the SystemNode, however, in such cases the CLI scripts will not be notified about those exceptions generated by the SystemNode during deployment. In such cases, ‘deploy.app’ ANT Task (from CLI) will not terminate on its own, therefore the user will have to terminate the build manually.

Once the CLI build is triggered and if the host became unreachable, then it is expected behavior that CLI script will continue to execute as long as there is no timeout specified.

You can avoid indefinite waiting times for the AdminTask by setting the timeout for each AdminTask [timeout="timeout value"/>] in the CLI build file. If a timeout occurs and the "failOnError" attribute of AdminTask is true, then the Ant task will fail. If the timeout is not specified then the default value is 0, which means the task will never timeout.