-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL issues with Install Script #894
Comments
I am encountering the same issue. The installation process gets stuck at "Setting up IXP Manager database...". I have found the following error message in the ixp-manager-install.log In Connection.php line 760: It looks like the problem was related to a code change in PR #887. After I reversed that change, the installation worked fine. |
Thanks @tallwireless and @ShengHungWu - that has been fixed now. The install script should work fine now as it pulls from release-v6 and the fix is in there. |
ISSUE TYPE
Bug Report
OS
charlesr@portal:/srv/ixpmanager$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
VERSION
ENVIRONMENT
CONFIGURATION
SUMMARY
Installer fails to complete. Appears to be an issue with the a difference between the database schema in the repo and the install script.
STEPS TO REPRODUCE
During the installation, the installer quits after attempting to add entries to the database:
Making some modifications to the script to get the MySQL commands, I was able to determine that there is a difference between the schema in the database, and the commands used by the installer:
As I'm currently working on bringing up a new IX, I have installed the portal software several times in the last month for testing and development, and haven't run into any issues. I think this might be related to the new release of the software.
EXPECTED RESULTS
A successful installation of the portal software.
ACTUAL RESULTS
A non-successful installation of the portal software.
IMPORTANCE
This is of importance to us as we are currently setting up our production environment to go live in the next week or so.
RELEVANT LOGS
N/A
The text was updated successfully, but these errors were encountered: