Troubleshooting

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

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.

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.

Corrupted Database Dump

If you think your database dump has been corrupted, you can check by using this command with the hostname of the source system:

ssh root@source_hostname "su -s /bin/bash - postgres -c exit"

The command will only produce output if the database has become corrupted.

If the database is corrupted, check the .bashrc environment file on the source system. Ensure there is no extra text in the file at the point that the script starts the shell.

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.