Before deleting any files, you must stop the background processes and automated tasks that keep Observium running. Leaving these active can cause system errors and log bloating during the deletion process. 1. Remove the Cron Jobs
Run the following command to drop the Observium database (replace observium with your actual database name if you customized it during installation): DROP DATABASE observium; Use code with caution.
This guide assumes the standard installation path ( /opt/observium ). If you installed it in a custom directory, adjust the commands accordingly. Step 1: Disable and Remove Observium Cron Jobs
Uninstalling Observium from an Ubuntu system is a deliberate process because it is a self-contained application typically installed into a specific directory, rather than a standard system package. Unlike applications managed by uninstall observium ubuntu
He took a deep breath. Then, he began.
Observium uses a Virtual Host configuration to serve its web interface. You must delete this configuration file so your web server does not throw errors on its next reload. For Apache Users: Disable the Observium site configuration: sudo a2dissite observium.conf Use code with caution. Delete the virtual host configuration file: sudo rm /etc/apache2/sites-available/observium.conf Use code with caution. Restart Apache to apply changes: sudo systemctl restart apache2 Use code with caution. For Nginx Users: Delete the server block configuration file:
Delete the dedicated Observium database user. Check your original config.php if you forgot the exact username: DROP USER 'observium'@'localhost'; Use code with caution. Flush the privileges to apply changes and exit: FLUSH PRIVILEGES; EXIT; Use code with caution. Step 3: Remove the Observium Installation Files Before deleting any files, you must stop the
During a standard installation, a dedicated system user named observium is often created to run the poller scripts safely without root permissions.
Observium is a powerful, auto-discovering network monitoring platform. However, there may come a time when you need to migrate to a different solution (like LibreNMS, Zabbix, or PRTG), free up system resources, or perform a clean reinstallation. Simply deleting the Observium directory is not enough. A proper uninstall involves removing the web files, databases, cron jobs, web server configuration, and the associated system user.
Leo, the sole systems administrator for a modest but growing cloud startup, fumbled for his phone. The glow of the screen illuminated his tired face. Observium, the network monitoring tool he’d lovingly installed on an Ubuntu server three years ago, was screaming that a core switch was down. Remove the Cron Jobs Run the following command
Note: If your database or username differs, check config.php under $config['db_name'] and $config['db_user'] .
Note: If you use Nginx instead of Apache, replace apache2 with nginx . Step 2: Remove Cron Jobs and Systemd Timers
Observium uses a MySQL or MariaDB database. You should drop the database to free up space and remove old credentials.
Remove the dedicated database user created for Observium (usually named observium ): DROP USER 'observium'@'localhost'; Use code with caution. Flush the privileges to apply the changes and exit: FLUSH PRIVILEGES; EXIT; Use code with caution. Step 5: Remove Web Server Configurations
Observium is a powerful network monitoring platform, but there may come a time when you need to remove it entirely — perhaps migrating to LibreNMS, Prometheus, or simply reclaiming resources. Because Observium isn’t installed from standard Ubuntu repositories, a simple apt remove won’t suffice. This guide walks through a , including the web interface, database, RRD files, and cron jobs.