Troubleshooting

This section contains some common problems you might encounter with SUSE Manager upgrades, and solutions to resolving them.

To get more information about an upgrade problem, check the migration log file. The log file is located at /var/log/rhn/migration.log on the system you are upgrading.

1. Not Enough Disk Space

Check the available disk space before you begin migration. We recommend locating /var/spacewalk and /var/lib/pgsql on separate XFS file systems.

When you are setting up a separate file system, edit /etc/fstab and remove the /var/lib/pqsql subvolume. Reboot the server to pick up the changes.

2. Retrying to Set up the Target System

If you need to retry setting up the target system, follow these steps:

  1. Delete /root/.MANAGER_SETUP_COMPLETE.

  2. Stop PostgreSQL and remove /var/lib/pgsql/data.

  3. Set the target system hostname to match the source system hostname.

  4. Check the /etc/hosts file, and correct it if necessary.

  5. Check /etc/setup_env.sh on the target system, and ensure the database name is set:

    MANAGER_DB_NAME='susemanager'
  6. Reboot the target system.

  7. Run mgr-setup again.

3. Schema Upgrade Fails

If the schema upgrade fails, the database version check and all the other spacewalk services do not start. Run spacewalk-service start for more information and hints how to proceed.

You can also run the version check directly:

systemctl status uyuni-check-database.service

or

journalctl -u uyuni-check-database.service

These commands print debug information if you do not want to run the more general spacewalk-service command.

4. The Web UI Fails to Load

Sometimes, the Web UI will not load after migration. This is usually caused by browser caching, if the new system has the same hostname and IP address as the old system. This duplication can confuse some browsers.

This issue is resolved by clearing the cache and reloading the page. In most browsers, you can do this quickly by pressing Ctrl+F5.