Troubleshoot upgrade issues
In the event something goes wrong during your upgrade, check the following sections for help.
Restoring the PostgreSQL 9.4 database in the event the upgrade fails
If you experience problems upgrading your PostgreSQL database, you can restore your database from backup and proceed with the the upgrade after solving any other issues.
Example problems:
- System overflows available disk space.
- Disk mount becomes unavailable due to network or other issue.
- System crashes for issues unrelated to the database during upgrade.
You will need to to recreate the local PostgreSQL database, then restore your data from a backup.
Actions to take to restore the PostgreSQL database:
- Log in to the Splunk Phantom instance's operating system as either the root user or a user with sudo privileges.
- Run the recreate_local_db.py script to reinitialize the local PostgreSQL database.
/opt/phantom/bin/recreate_local_db.py
Running this script will destroy any existing data in the local database.
- Restore the PostgreSQL database from your backup. sudo phenv python ibackup.pyc --restore <path/to/<number>_phantom_backup.tar>See Backup or restore your Splunk Phantom instance in Administer Splunk Phantom.
- Verify that your Splunk Phantom data has been restored.
- Redo the upgrade.
Upgrade an unprivileged Splunk Phantom Cluster | Migrate a Splunk Phantom install from REHL 6 or CentOS 6 to RHEL 7 or CentOS 7 |
This documentation applies to the following versions of Splunk® Phantom (Legacy): 4.9
Feedback submitted, thanks!