> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.19.01, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

*Edge for Private Cloud v4.19.01*

An on-premises installation of Edge Private Cloud does not restart automatically during a
reboot. You can use the following commands to enable/disable autostart on any node.

To *enable* all components on the node:

```
/opt/apigee/apigee-service/bin/apigee-all enable_autostart
```

To *disable* all components on the node:

```
/opt/apigee/apigee-service/bin/apigee-all disable_autostart
```

To enable or disable autostart for a specific component on the node:

    /opt/apigee/apigee-service/bin/apigee-service component_name enable_autostart
    /opt/apigee/apigee-service/bin/apigee-service component_name disable_autostart

Where <var translate="no">component_name</var> identifies the component. Possible values include:

- `apigee-cassandra` (Cassandra)
- `apigee-openldap` (OpenLDAP)
- `apigee-postgresql` (PostgreSQL database)
- `apigee-qpidd` (Qpidd)
- `apigee-sso` (Edge SSO)
- `apigee-zookeeper` (ZooKeeper)
- `edge-management-server` (Management Server)
- `edge-management-ui` (new Edge UI)
- `edge-message-processor` (Message Processor)
- `edge-postgres-server` (Postgres Server)
- `edge-qpid-server` (Qpid Server)
- `edge-router` (Edge Router)
- `edge-ui` (Classic UI)

The script only affects the node on which you run it. If you want to configure all nodes for
autostart, run the script on all nodes.

> [!NOTE]
> **Note:** If you run into issues where the OpenLDAP server does not start automatically on reboot, try disabling SELinux or setting it to permissive mode.

Note that the order of starting the components is very important:

1. First start ZooKeeper, Cassandra, LDAP (OpenLDAP) If ZooKeeper and Cassandra are installed as cluster, the complete cluster must be up and
   running before starting any other Apigee component.

2. Then, any Apigee component (Management Server, Router, UI, etc.). For Postgres Server first start postgresql and for Qpid Server first start qpidd.

**Implications:**

- For a complete restart of an Apigee Edge environment, the nodes with ZooKeeper and Cassandra need to be booted completely prior to any other node.
- If any other Apigee component is running on one or more ZooKeeper and Cassandra nodes, it is not recommended to use autostart. Instead, start the components in the order described in [Starting, stopping, restarting, and
  checking the status of Apigee Edge](https://docs.apigee.com/private-cloud/v4.19.01/starting-stopping-and-restarting-apigee-edge).

## Troubleshooting autostart

If you configure autostart, and Edge encounters issues with starting the OpenLDAP server, you
can try disabling SELinux or setting it to permissive mode on all nodes. To configure
SELinux:

1. Edit the `/etc/sysconfig/selinux` file:

   ```
   sudo vi /etc/sysconfig/selinux
   ```
2. Set `SELINUX=disabled` or `SELINUX=permissive`.
3. Save your edits.
4. Restart the machine and then restart Edge:

   ```
   /opt/apigee/apigee-service/bin/apigee-all restart
   ```