sudo rm -rf /opt/observium
If you installed elsewhere (e.g., /var/www/html/observium):
sudo rm -rf /var/www/html/observium
sudo rm -rf /var/log/observium
sudo mysql -u root -p -e "SHOW DATABASES;" | grep observium
First, stop all running Observium-related services:
sudo systemctl stop apache2
sudo systemctl stop mysql
sudo systemctl stop snmpd
sudo systemctl stop fpm
If you have Observium's poller service running:
sudo systemctl stop observium
Observium often runs under www-data, but some setups create a dedicated observium user. If present:
sudo userdel observium
sudo groupdel observium
You have now successfully removed Observium, its database, and its configuration files from your Ubuntu server. If you are migrating, you can now proceed with installing your new monitoring tool.
Uninstalling Observium from Ubuntu requires a manual cleanup because it is typically installed from source or a tarball into the /opt directory rather than through a standard package manager. Step 1: Stop Services and Cron Jobs
Before deleting files, stop the background processes to prevent errors.
Cron Jobs: Remove or comment out the Observium cron file to stop automated polling. sudo rm /etc/cron.d/observium Use code with caution. Copied to clipboard
Web Server: Disable the Observium site configuration in Apache or Nginx.
Apache: sudo a2dissite observium.conf followed by sudo systemctl reload apache2
Nginx: Remove the symlink in /etc/nginx/sites-enabled/ and reload. Step 2: Remove the Installation Directory
Delete the main application files located in the directory where you originally extracted the Observium tarball. sudo rm -rf /opt/observium Use code with caution. Copied to clipboard Step 3: Drop the Database uninstall observium ubuntu
Remove the dedicated database and user created for Observium in MySQL or MariaDB. Log in to your database: sudo mysql -u root -p Run the following commands:
DROP DATABASE observium; DROP USER 'observium'@'localhost'; FLUSH PRIVILEGES; EXIT; Use code with caution. Copied to clipboard Step 4: Cleanup Dependencies (Optional)
If you installed specific packages solely for Observium (like fping, net-snmp, or specific PHP modules) and no longer need them, you can remove them using apt. sudo apt purge fping snmp snmpd sudo apt autoremove --purge Use code with caution. Copied to clipboard
Note: Be careful not to remove packages required by other applications on your system. Step 5: Remove Logs and Temp Files
Check for any remaining logs or temporary data that might be outside the /opt folder. Check /var/log/ for any Observium-specific log files.
Ensure any custom SNMP configurations in /etc/snmp/snmp.conf related to Observium MIBs are cleared. AI responses may include mistakes. Learn more benjaminrobertson/observium - Puppet Forge
The Uninstall
It started, as these things often do, with a single red alert at 3:14 AM.
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.
He stumbled to his home office, logged in, and realized the truth: the switch was fine. Observium was lying.
That was the first crack. Over the next week, more cracks appeared. The graphs for memory usage flatlined. The auto-discovery feature, once a marvel, now identified servers as "unknown device (generic)." The web interface took forty-five seconds to load. Upgrading it—a task involving a labyrinth of ./discovery.php and ./poller.php commands—failed with a PHP dependency error so cryptic it felt like a personal insult.
The final straw came when Leo’s boss, Jenna, asked for a simple bandwidth report for a client. Leo spent two hours trying to extract a clean CSV from Observium’s MySQL database, only to get data that showed negative packets transmitted. sudo rm -rf /opt/observium
"We need a new solution," Jenna said, not unkindly. "Can you remove the old one?"
"Remove," Leo repeated. The word felt heavier than "uninstall." It meant admitting failure. It meant confronting the ghost of his past self—the eager junior admin who had followed a quickstart guide with religious fervor, pasting commands without truly understanding them.
"By Friday," Jenna added, and walked away.
Friday arrived like a storm front. Leo sat before the terminal, the cursor blinking on a cold, gray afternoon. The server, affectionately named monitor.internal, hummed quietly in the rack.
He took a deep breath. Then, he began.
His first instinct was the nuclear option. sudo apt remove observium. He typed it, heart pounding. The terminal whirred, thought for a moment, and replied:
Package 'observium' is not installed, so not removed.
Of course. He hadn't used apt. He’d compiled it from source, following a blog post titled "The Ultimate Network Monitoring Guide (2019)." The guide had made him feel like a wizard. Now, it made him feel like an archaeologist.
He opened his old notes. The installation path was /opt/observium. The web root had a symlink: /var/www/html/observium. The database was called observium_db. The cron job ran poller.php every five minutes. It was a mess of his own making.
Step one was to stop the bleeding. He disabled the cron job:
sudo crontab -u www-data -l > old_cron.txt
sudo crontab -u www-data -r
The poller fell silent. A small victory.
Step two was to unplug the web interface. He removed the symlink: If you installed elsewhere (e
sudo rm /var/www/html/observium
He reloaded Apache. The old dashboard, with its dead graphs and red alerts, was gone. A generic "404 Not Found" page stared back at him. It was peaceful.
Step three was the database. He logged into MySQL with trembling fingers.
DROP DATABASE observium_db;
DROP USER 'observium'@'localhost';
FLUSH PRIVILEGES;
The database vanished in a whisper. Thousands of data points, three years of history—gone. He felt a strange pang, like deleting a save file for a game he no longer played.
Step four was the purge. The actual files.
sudo rm -rf /opt/observium
He watched the directories scroll by: rrd/, logs/, includes/, html/. All those custom alerts he’d written. All those graphs he’d tweaked. All gone.
He checked for leftovers. Configuration files? sudo find / -name "*observium*" -type f 2>/dev/null. A few old logrotate snippets in /etc/logrotate.d/. He deleted those too. He checked PHP modules he’d installed specifically for Observium—php7.4-mysqlnd, php7.4-snmp. He left them for now. No need to break other things.
Finally, he ran sudo apt autoremove to clean up orphaned packages. A library called libsnmp-dev was removed. He didn't even know what that was for.
He rebooted the Ubuntu server.
When it came back up, the terminal was clean. htop showed CPU usage at 2%. Memory was mostly free. The server was quiet. It was just an Ubuntu box again, waiting for its next purpose.
Leo leaned back in his chair. He felt lighter. The frantic red alerts, the sluggish interface, the nagging dread of an unsupported, decaying system—all of it was gone. He had not just uninstalled a program. He had exorcised a ghost.
He opened a fresh terminal window and typed:
sudo apt update
sudo apt install prometheus node-exporter grafana
The new future began to install.
And for the first time in months, Leo smiled.