Ubuntu 14环境下Graphite 0.9.12升级至0.9.14操作咨询

Hey there! I’ve walked through this exact upgrade on Ubuntu 14 before, so let me break down everything you need to know—no guesswork required.

Key Pre-Upgrade Basics #

First off, you don’t need to fully remove your old Graphite packages—this is an in-place upgrade, but backups are non-negotiable to avoid losing your metrics or configs.

1. Stop Running Services #

Before making any changes, shut down Carbon and your web server (almost always Apache for Graphite setups) to prevent conflicts:

sudo service carbon-cache stop
sudo service apache2 stop

2. Backup Critical Files #

These are the files you must preserve—never delete them unless you have a solid backup:

• Configuration files:
  • /opt/graphite/conf/carbon.conf
  • /opt/graphite/conf/storage-schemas.conf
  • /opt/graphite/conf/storage-aggregation.conf
  • /opt/graphite/webapp/graphite/local_settings.py
• Metrics data:
  • The entire /opt/graphite/storage/ directory holds all your historical metrics. Back it up with a timestamped archive:

    tar -czf graphite-storage-backup-$(date +%Y%m%d).tar.gz /opt/graphite/storage/
    

Performing the Upgrade #

Most Graphite installs on Ubuntu 14 use pip, so this is the most reliable method to get 0.9.14:

pip install --upgrade graphite-web==0.9.14 carbon==0.9.14 whisper==0.9.14

This command will automatically replace old package files with the 0.9.14 versions—your custom configs and metrics data will stay completely untouched.

If you originally installed via apt, note that Ubuntu 14’s official repos don’t include Graphite 0.9.14, so switching to pip is the way to go here.

Post-Upgrade Steps #

1. Run Database Migrations #

0.9.14 includes small database schema updates, so execute this to sync the Graphite database:

cd /opt/graphite/webapp/graphite
python manage.py migrate

2. Restart Services #

Bring everything back online:

sudo service carbon-cache start
sudo service apache2 start

3. Verify the Upgrade #

• Visit your Graphite web interface—check the bottom-left corner for the version number (it should show 0.9.14).
• Test a few metrics to ensure they’re still being collected and displayed correctly.

What to Avoid #

• Don’t manually delete old package files—pip’s upgrade process handles this cleanly, and manual deletion can break dependencies.
• Don’t skip backups—even if the upgrade goes smoothly, having a fallback is always smart.

If you run into issues after upgrading, check the log files at /opt/graphite/storage/log/webapp/ and /opt/graphite/storage/log/carbon/ for error messages—they’ll usually point you straight to the fix.

内容的提问来源于stack exchange，提问作者Zoette