ansible · ansible/1
1
General error
An error occurred that prevented the playbook from running, such as an unhandled exception, a missing module, or an internal Ansible failure. Check stderr for details.
Also defined in
- bazel Build Failed The build failed. One or more build actions did not complete successfully. Check the build output for the failing target and action.
- cmake Error CMake encountered a fatal error. This is the general non-zero exit code returned when configuration, generation, or a build step fails. Check the output for 'CMake Error' lines to identify the specific failure.
- composer General Error A general error occurred. Causes include network failures while downloading packages, file system permission errors, a malformed composer.json, or an authentication failure against a private repository.
- curl Unsupported protocol The URL scheme is not supported by this build of curl.
- docker Application error The container process exited with a generic application error. The specific cause is logged to the container's stdout/stderr.
- eslint Linting Errors Found Linting succeeded, but at least one rule reported an error; or the number of warnings exceeded the `--max-warnings` threshold. Fix the reported violations or adjust the ESLint configuration.
- git General error The command failed for a non-fatal reason, such as no changes to commit, a merge conflict left unresolved, or a pattern that matched nothing. The exact meaning is subcommand-specific.
- gradle Build Failed The Gradle build failed. One or more tasks did not complete successfully. Check the build output for the specific task failure and its associated exception or error message.
- homebrew Homebrew Error The Homebrew command failed. This is the generic failure exit code for Homebrew; the actual exception class and message appear above it in the output. Common causes include formula not found, build failure, or a network error fetching the bottle.
- jest Tests Failed One or more tests failed, a test suite failed to run (e.g. due to a syntax error or missing import), or Jest itself encountered an unhandled error. Check the test output for the specific failure messages.
- ldap operationsError The server encountered an internal error that prevented it from completing the operation. This is a general-purpose server-side error not covered by a more specific code.
- make Build Error One or more recipes (shell commands in a rule) exited with a non-zero status. Make stops at the first failure unless the `-k` / `--keep-going` flag is used, in which case it continues other independent targets and exits with 1 when all work is done.
- maven BUILD FAILURE One or more goals or lifecycle phases failed. The failure message is printed above the BUILD FAILURE banner. Common causes include compilation errors, test failures, unresolvable dependencies, or plugin execution errors. Scroll up to find the first ERROR line in the output.
- modbus ILLEGAL_FUNCTION The function code in the request is not recognised or is not allowed by the server. This may indicate the server has not implemented the requested function, or is not in a state that allows it.
- mongodb InternalError An unexpected internal error occurred in the server. This is a MongoDB bug; report it with the full log output.
- pytest Tests Failed Tests were collected and run, but one or more tests failed or raised an unexpected error. Review the test output for FAILED and ERROR entries, then fix the failing tests or assertions.
- rsync Syntax or usage error rsync was invoked with an invalid option or argument combination.
- shell General error A general or unspecified error occurred. Many programs use this as a catch-all failure code.
- systemd Failure The service process exited with a generic failure code.
- vue Error in render function An unhandled exception was thrown while executing a component's render function. This includes errors in template expressions and in the body of a functional component.