> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/installation-and-settings/deployment-types/saas-deployment/bridge-client-setup/autonar/linux.md).

# Linux

Update Existing AutoNAR Cron Job with the New NiFi Installation Path on Linux

This article outlines the procedure for updating an existing AutoNAR cron job when the Apache NiFi installation path changes on a Linux server. This procedure replaces references to the old NiFi installation path with the new NiFi path. It also includes steps to verify the cron configuration, script permissions, AutoNAR operation, and cron logs.

## Prerequisites

Ensure the following prerequisites are met before starting the procedure:

* Access to the Linux server hosting the Apache NiFi installation.
* Sudo privileges to view the NiFi service configuration and edit the root crontab.
* Access to the new Apache NiFi installation directory.
* Access to the OvalEdge application with permission to manage the Bridge Client.
* The NAR file S3 link required to test the NAR update.

### Steps Involved

#### **Identify the Existing NiFi Path**

1. Check the current Apache NiFi service configuration.

   ```
   sudo systemctl status nifi.service
   ```
2. Check the service configuration to identify the current Apache NiFi installation path.

   ```
   sudo systemctl cat nifi.service
   ```
3. Identify the new Apache NiFi installation path.
   \
   For example:\
   \
   **Old Path:**

   ```
   /home/ovaledge/nifi/nifiinstall/nifi-1.16.3
   ```

   \
   \
   **New Path:**

   ```
   /home/ovaledge/nifi_client/nifi-1.25.0
   ```

#### Update the Existing Cron Job

1. Open the root crontab.

   ```
   sudo crontab -e
   ```
2. Locate the existing AutoNAR cron entry and replace the old Apache NiFi path with the new path.\
   \
   **Old cron entry:**

   ```
   */5 * * * * /home/ovaledge/nifi/nifiinstall/nifi-1.16.3/bin/oe-cleanup-restart.sh /home/ovaledge/nifi/nifiinstall/nifi-1.16.3 >> /home/ovaledge/nifi/nifiinstall/nifi-1.16.3/logs/cronLogfile.log 2>&1
   ```

   \
   \
   **Updated cron entry:**

   ```
   */5 * * * * /home/ovaledge/nifi_client/nifi-1.25.0/bin/oe-cleanup-restart.sh /home/ovaledge/nifi_client/nifi-1.25.0 >> /home/ovaledge/nifi_client/nifi-1.25.0/logs/cronLogfile.log 2>&1
   ```

{% hint style="info" %}
Update all references to the old Apache NiFi path in the cron entry, including the script path, NiFi installation path, and log file path.
{% endhint %}

#### **Verify the Cron Job**

1. After saving the crontab, verify that the updated AutoNAR cron entry is present.

   ```
   sudo crontab -l
   ```
2. Confirm that the cron entry points to the new Apache NiFi installation directory.

#### Verify Script Permissions

1. Verify that the AutoNAR script is executable.

   ```
   sudo chmod +x /home/ovaledge/nifi_client/nifi-1.25.0/bin/oe-cleanup-restart.sh
   ```
2. Verify that the script exists.

   ```
   ls -l /home/ovaledge/nifi_client/nifi-1.25.0/bin/oe-cleanup-restart.sh
   ```

#### **Test the AutoNAR Setup** 

Test the restart and NAR update functionality from the OvalEdge application.

**Restart the Bridge Client**

1. Log in to the OvalEdge application.
2. Navigate to **Administrator > Connectors > Manage Bridge**.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2F1D409kJBKLfLf5tz58Kz%2Fimage.png?alt=media&amp;token=914f07c4-d1d1-4723-86ad-a595c49ca6ec" alt=""><figcaption></figcaption></figure>
3. Click **Restart Bridge**.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FtUzfIUEhqeKE3FSKvreU%2Fimage.png?alt=media&amp;token=be17e42d-2900-464d-bcb5-59bd7343f36a" alt=""><figcaption></figcaption></figure>
4. In the confirmation prompt, click **Yes**.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FRt3ElH8NqKajHaFAEMEG%2Fimage.png?alt=media&amp;token=8c2fa235-117e-491b-9110-1026074c4af9" alt=""><figcaption></figcaption></figure>
5. Wait approximately 5 minutes for the restart process to complete.

**Update the NAR File**

1. Click **Update Bridge**.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FHDZJvhfnVojsvdUZj0Q1%2Fimage.png?alt=media&amp;token=a2cc5526-1c3c-4691-9d6c-4663cadfa0f9" alt=""><figcaption></figcaption></figure>
2. Enter the S3 link for the NAR file.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FybRnWR62iixXnS0Wl16D%2Fimage.png?alt=media&amp;token=071aaac9-827e-46e4-b53b-8b6966e5530e" alt=""><figcaption></figcaption></figure>
3. Click **Update**.
4. Wait approximately 5 minutes for the NAR file update and Apache NiFi client restart to complete.

   <figure><img src="https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FAZkS1NtQB4sG44tgOR7c%2Fimage.png?alt=media&amp;token=80c091a9-5625-4c0d-9834-9079a87130a9" alt=""><figcaption></figcaption></figure>

**Expected Result**

The Bridge Client restarts successfully, and the NAR file update completes without errors.

#### **Verify the Cron Log**

1. After the next scheduled cron execution, check the AutoNAR cron log.

   ```
   tail -f /home/ovaledge/nifi_client/nifi-1.25.0/logs/cronLogfile.log
   ```
2. Confirm that the AutoNAR script executes successfully without errors.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/installation-and-settings/deployment-types/saas-deployment/bridge-client-setup/autonar/linux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.