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
Error in import30.py script #279
Comments
Error on Ubuntu 14.04 when tried to upgrade 2.4.4 to 3.0.1 |
Commit 9fe6c81 has fix. |
When I try to start openldap
When Gluu Server is restarted
|
I figured out the issue. The ox-INUM object classes were deprecated during the 3.0 development and are no longer used. But the old data depends on the objectclass. I updated the script to concat the 99-user.ldif schema to the custom.schema of OpenLDAP in the commit 193e21d. This should fix the issue. |
@tecoholic this is from CentOS 6.8. The import does not throw any errors now, but oxTrust fails to start. When I restarted oxTrust and tailed log, I found the following error in the log. |
@zamilskhan PKIX path failure is usually due to the change in certificates. A restart of the gluu-server should reload the certificates and remove the error. |
The last line in the upgrade docs https://gluu.org/docs/ce/3.0.1/upgrade/ says
It feels as if it is hidden in the docs. @jschristie Can you update the sentence to read "After completion of import, stop/start gluu-server container one time." as a |
@tecoholic I just updated the docs accordingly. Thanks for the suggestion. |
Closing the issue as concerns were dealt with. |
Error from terminal from a CentOS 6.8 VM upgrade test from 2.4.4.2 to 3.0.1
Restarted Gluu |
Can you share the |
This issue was investigated again. Found no errors. It looks like the above issues have been sorted out after Shekar fixed the time parsing to the import script. Here is the output of testing.
However there is an important issue in CentOS 6.x: The 1. Installing Python 2.7
2. Installing Pip
3. Installing JsonMerge
4. Running the import script
|
OS: CentOS 6.8
Upgrade: 2.4.4 to 3.0.1
See ticket regarding the issue.
The following error is seen when the import command is used
The text was updated successfully, but these errors were encountered: