By: Thomas Maerz user 14 Dec 2017 at 2:11 a.m. CST

4 Responses
Thomas Maerz gravatar
Hello, I am attempting to migrate our instance form 2.4.3 to 3.1.1. I am not having much success. I am following the documentation as specified. When the 2.4.3 --> 3.1.1 upgrade did not work, I also tried to get from 2.4.3 --> 2.4.4 in an attempt to see if a 2.4.4 --> 3.1.1 migration might work, but the 2.4.3 --> 2.4.4 migration also does not work for other reasons. For the 2.4.3 --> 2.4.4 upgrade, I was able to successfully export. I then uninstalled 2.4.3, installed 2.4.4 per instructions, installed pip and jsonmerge. When I try to run import244.py backup_24, I get the error: > GLUU.root@gluu:~# ./import244.py backup_24 > Traceback (most recent call last): > File "./import244.py", line 552, in <module> > main(sys.argv[1]) > File "./import244.py", line 493, in main > backup_version = int(getBackupProperty('version').replace('.', '').strip()[:3]) > ValueError: invalid literal for int() with base 10: 'v3' import_244.log is empty. The existing gluu-server-2.4.4 instance works just fine. In regards to the 2.4.3 --> 3.1.1 migration: When I try to run the import_2431.py script, I get the following output: > ------------------------------------------------------------ > Gluu Server Community Edition Migration Tool > ============================================================ > > Migrate LDAP server's configuration used for authentication at the source instance?- 1.yes, 2.no [2]: 1 > INFO Stopping Webapps oxAuth and Identity. > INFO Stopping OpenLDAP Server. > INFO Copying the Certificates. > INFO Updating the CA Certs Keystore. > INFO Copying the custom pages and assets of webapps. > INFO Copying Shibboleth IDP files... > INFO Converting Schema files of custom attributes. > $ webexID $ updatetimestamp $ whenChanged $ firstname $ lastname $ webexLastName $ webexEmail $ email $ webexFirstName $ postalCode $ wrikeID $ googleID $ oraclefusionID $ oracleCloudID $ novatusID $ paycomID $ gotoassistID $ auroranameID > INFO Exporting LDAP data. > ERROR 5a31fd99 /opt/gluu/schema/openldap/custom.schema: line 16 attributetype: Inconsistent duplicate attributeType: "email" > slapcat: bad configuration file! > > INFO Processing the LDIF data. > INFO Importing Processed LDAP data. > ERROR 5a31fdda /opt/gluu/schema/openldap/custom.schema: line 16 attributetype: Inconsistent duplicate attributeType: "email" > slapadd: bad configuration file! > > ERROR 5a31fdda /opt/gluu/schema/openldap/custom.schema: line 16 attributetype: Inconsistent duplicate attributeType: "email" > slapadd: bad configuration file! > > INFO Fixing permissions for files. > ERROR chown: cannot access '/opt/gluu/data/main_db/data.mdb': No such file or directory > > ERROR chown: cannot access '/opt/gluu/data/site_db/data.mdb': No such file or directory > > INFO Starting OpenLDAP Server. > ERROR Couldn't start the OpenLDAP server. > ERROR Symas OpenLDAP LDAP services slapd starting... failed. > > GLUU.root@localhost:~# service gluu-server-3.1.1 status > gluu-server-3.1.1: unrecognized service > GLUU.root@localhost:~# service idp status > Jetty running pid=4263 > > START_INI = /opt/gluu/jetty/idp/start.ini > START_D = /opt/gluu/jetty/idp/start.d > JETTY_HOME = /opt/jetty > JETTY_BASE = /opt/gluu/jetty/idp > JETTY_CONF = /opt/jetty/etc/jetty.conf > JETTY_PID = /var/run/idp.pid > JETTY_START = /opt/jetty/start.jar > JETTY_LOGS = /opt/gluu/jetty/idp/logs > JETTY_STATE = /opt/gluu/jetty/idp/idp.state > CLASSPATH = > JAVA = /opt/jre/bin/java > JAVA_OPTIONS = -server -Xms256m -Xmx572m -XX:MaxMetaspaceSize=246m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/idp -Djetty.logging.dir=/opt/gluu/jetty/idp/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/idp -Djava.io.tmpdir=/opt/jetty-9.3/temp > JETTY_ARGS = jetty.http.host=localhost jetty.http.port=8086 jetty.state=/opt/gluu/jetty/idp/idp.state jetty-logging.xml jetty-started.xml > RUN_CMD = /opt/jre/bin/java -server -Xms256m -Xmx572m -XX:MaxMetaspaceSize=246m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/idp -Djetty.logging.dir=/opt/gluu/jetty/idp/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/idp -Djava.io.tmpdir=/opt/jetty-9.3/temp -jar /opt/jetty/start.jar jetty.http.host=localhost jetty.http.port=8086 jetty.state=/opt/gluu/jetty/idp/idp.state jetty-logging.xml jetty-started.xml After this process, the gluu-server-3.1.1 won't start and the browser gets 403 errors just like [this](https://support.gluu.org/installation/4210/shibboleth-503-after-fresh-install/) The process described by that gentleman does not fix the issue. Any suggestions?

By Arvind Tomar staff 14 Dec 2017 at 3:09 a.m. CST

Arvind Tomar gravatar
hi Thomas Maerz please try import script on the fresh server you have run multiple time import script on the same server ... thanks arvind tomar

By Thomas Maerz user 14 Dec 2017 at 3:13 a.m. CST

Thomas Maerz gravatar
Hello and thank you for the quick response! I am already using a fresh installed Ubuntu Server 14.04 each time I do this as well as using vm snapshots before and after each step. Any other suggestions?

By Arvind Tomar staff 14 Dec 2017 at 3:37 a.m. CST

Arvind Tomar gravatar
can you share you exported dir with me ? so i can check it my side my gluu email is arvind@gluu.org but I was talking about fresh gluu instance you need to import on fresh gluu 3.1.1

By Arvind Tomar staff 20 Dec 2017 at 1:15 a.m. CST

Arvind Tomar gravatar
There is no response in while so assuming issue is resolved. closing the issue.