> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-adaptive-execution-layer-ael/troubleshooting-ael-cp/driver-timeout-and-deployment-errors-with-ael-on-secured-clusters-ael-troubleshooting.md).

# Driver timeout and deployment errors with AEL on secured clusters

You may receive driver timeout and web socket deployment error messages when running Spark with AEL on a secured cluster.

Before trying to address any issues while running Spark with AEL on a secured cluster, verify the following:

* The cluster has been secured by your cluster administrator.
* The user associated with the AEL daemon has a valid Kerberos certificate.

If the expiration date and time returned by the `klist` command is less than the date and time returned by the `date` command, you must obtain a new ticket by using the `kinit` command. Contact your cluster administrator to determine what `kinit` approach was set up on your system.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-adaptive-execution-layer-ael/troubleshooting-ael-cp/driver-timeout-and-deployment-errors-with-ael-on-secured-clusters-ael-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
