Return to Jive Software

Up to Discussions in Support

This Question is Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
3,081 Views 3 Replies Last post: Jun 29, 2009 4:19 PM by Brad Heller RSS
kpierce Novice
kpierce
15 posts since
Apr 14, 2009
Currently Being Moderated

Jun 26, 2009 10:26 AM

Migration from 2.5/mysql to 3.0/psql fails

Performing a migration from 2.5 using MySQL to 3.0 using the default Postgres.  Running the migration script generates the following error.  The migration log (/usr/local/jive/var/logs/migration.log) is blank, most likely due to the condition noted in the first two lines of the error message.

 

clearspace:/usr/local/jive/bin/migration/bin # ./migration migration.properties
log4j:WARN No appenders could be found for logger (com.jivesoftware.migration.schema.DbUtil).
log4j:WARN Please initialize the log4j system properly.
com.mysql.jdbc.CommunicationsException: Communications link failure

Last packet sent to the server was 0 ms ago.
        at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1070)
        at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2104)
        at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:729)
        at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:298)
        at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:283)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:185)
        at com.jivesoftware.migration.schema.DbUtil.getConnection(DbUtil.java:140)
        at com.jivesoftware.migration.etl.DbConfig.getInputConnection(DbConfig.java:192)
        at com.jivesoftware.migration.etl.DbConfig.getVersion(DbConfig.java:297)
        at com.jivesoftware.cli.Main.exportBlobs(Main.java:200)
        at com.jivesoftware.cli.Main.run(Main.java:102)
        at com.jivesoftware.cli.Main.main(Main.java:68)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:366)
        at java.net.Socket.<init>(Socket.java:209)
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:257)
        at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:277)
        at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2030)
        ... 11 more
Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException
        at com.jivesoftware.cli.Main.main(Main.java:70)
Caused by: java.lang.NullPointerException
        at com.jivesoftware.migration.etl.DbConfig.getVersion(DbConfig.java:307)
        at com.jivesoftware.cli.Main.exportBlobs(Main.java:200)
        at com.jivesoftware.cli.Main.run(Main.java:102)
        at com.jivesoftware.cli.Main.main(Main.java:68)

 

The migration.properties file is captured below.  I am able to get a MySQL command prompt by running mysql -u root -p on the source box.

 

inputUrl=jdbc:mysql://editedipaddress:3306/clearspace
inputDriver=com.mysql.jdbc.Driver
inputUser=root
inputPassword=editedpassword
outputUrl=jdbc:postgresql://127.0.0.1:5432/sbs
outputDriver=org.postgresql.Driver
outputUser=sbs
outputPassword=editedpassword
workDir=/usr/local/jive/var/work/migrate
steps=exportBlobs, exportSql, writeEtls, createTargetSchema, runEtls, validate

Expert
Brad Heller
3,518 posts since
Jun 18, 2009
Currently Being Moderated
Jun 26, 2009 11:55 AM in response to: kpierce
Re: Migration from 2.5/mysql to 3.0/psql fails

Hey there,

 

Did any data/tables/etc. make it in to the Postgres server? This link error could be that the migration script is not establishing a connection from the get go or there is a connection fault while the script is running. Does this DB live on the same server as your existing Clearspace deployment? Does it live on the same server as the Postegres server? Please ensure that extenal TCP/IP connections are allowed in to the MySQL daemon.

 

Let me know how that goes -- if that doesn't resolve the issue let's dig deeper.

 

Cheers,

Brad

kpierce Novice
kpierce
15 posts since
Apr 14, 2009
Currently Being Moderated
Jun 29, 2009 2:46 PM in response to: Brad Heller
Re: Migration from 2.5/mysql to 3.0/psql fails

The migration is from one server to a different server.  I needed to setup the user@remotehost MySQL account on the source server and afterward the migration worked flawlessly.  Thanks for the help!


 

 

o   mysql> grant all privileges on *.* to user@'remotehost' identified by 'password';

Expert
Brad Heller
3,518 posts since
Jun 18, 2009
Currently Being Moderated
Jun 29, 2009 4:19 PM in response to: kpierce
Re: Migration from 2.5/mysql to 3.0/psql fails

Great! Let me know if you have additional questions or comments!

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.