====Upgrading ARDI - Linux====

On Debian-based systems, the user will need to login via a terminal/SSH in order to begin the upgrade process.

The following command begins an upgrade not only of ARDI but of all of the various packages installed on the server...

<code>
sudo apt-get update
sudo apt-get upgrade
</code>

During the update, your drivers will be stopped and live data will stop flowing. Clients may have issues connecting. While the //entire// update process can take several minutes (depending on how many applications and services need to be downloaded and how fast your internet connection is), the actual **ARDI** down-time seldom lasts for more than one minute.

**Watch For Kept-Back Updates**

<WRAP info>
It's important to check for any updates not being applied.
</WRAP>

In some rare cases, you may see the following (the package name might be different, but will start with 'ardi-')

<code>
The following packages have been kept back:
  ardi-drivers
</code>

This occurs when there is a very large update to an ARDI component that needs you to download additional packages. As a security precaution, your system doesn't download these additional package automatically, so it doesn't apply the update.

To let your system know that it's OK to install the kept-back packages, type...

<code>
apt-get install //<package name>//
</code>

Where //<package name>// is the name of the package that was kept back. For example, **apt-get install ardi-drivers** would solve the problem shown in the example.

===Checking the Results===

After the automated upgrade is complete, you should visit **every** [[ARDI database|ARDI database]]  to ensure that any updates are applied and all are still working as expected.

New features sometimes require changes to the database or cache structure. These changes are applied the first time someone visits the web-interface for each database. This means that verifying that each database is working is actually a //vital// part of the update process.