Use of /warp import pre3-mysql is not working.

[veteranmina]

When attempting to import the old mysql database, which the schema was renamed to mywarpold, it states it cannot connect to the database. At first I thought I had a typo and re-checked it a few times, all good. So tried again and it still fails.

Looking at logs, this is all it gives me to deal with:

CONSOLE: [INFO] Import started. This may take some time...
7:47:36 PM CONSOLE: [INFO] Could not establish database connection in order to import warps: Failed to connect to the database.

This is the exact command that I am typing (minus user/pass)

/warp import pre3-mysql jdbc:mysql://localhost/mywarpold user pass warpTable

I have tried multiple times to get this to work, but it does not want to import itself to the new database.

[TheE]

Are you sure that the DSN is correct? Perhaps your MySQL server listens to a non standard port that needs to be given too?

Perhaps I should add some more debug output, the current error is not really specific.

[veteranmina]

It is the correct DSN, as it connects to the new database using the exact same DSN in the configuration. The port is also using the standard 3306 port. This is why I was stumped when it kept giving me this error.

[TheE]

I just tested it with my setup and it works as expected. Are you using an older devBuild? There was a similar bug, but that has been fixed.

[veteranmina]

I was using build #33 to upgrade. I can attempt to use a newer version to see if that works. The reason I had used that version was due to build#34 had the potential break.
(disregard the link to #33 it auto-linked that)

[TheE]

No, it should work fine with build#33, I just tested it. (Updating is still encouraged.)

Another guess: You mentioned that you renamed the scheme. Have you checked if the user, you are using to connect with the database, has the rights to access that scheme and use SELECT?

[veteranmina]

I had used root to create and then access the database, I can double check once I get off work to see.

I do have a second account that i use afterwards to keep root private, i'll check that account as well.

Could possibly dropping the db and restoring under a different name have anything to do with it?

[TheE]

I doubt it because even if, it should not matter for root.

I just pushed a new devBuild that should actually show the SQL error that happened. If you test it, please post the exact output of using the command you posted above, it might give us an idea about the cause.

[TheE]

I just got a mail with the comment you removed (the MySQL Workbench image). I noticed that there is no schema named mywarpold, there is only warp and mywarp and I assume that the later on is the new one.

Is this intentional, have you tested /warp import pre3-mysql jdbc:mysql://localhost/warp user pass warpTable?

[veteranmina]

Sorry about that, I removed it after i noticed you had just posted the new devBuild. The one called warp is the old one, i had changed the name and had also tried with it as well. I am currently getting the new dev build on the server.

[veteranmina]

Quite interesting, i uploaded the new build40 and ran this command:

/warp import pre3-mysql jdbc:mysql://localhost/warp user pass warpTable

It worked perfectly importing all warps.

Now my question about skipped warps, if i run it again when the user has logged in at least once, will it import it then?

[TheE]

Strange, maybe you were (without knowing) running a build older than 52cc629 (build17).

Anyway, I am glad that it is working now.

[veteranmina]

Could have thought i had the right one, but in the end thank you very much for the support!

[TheE]

And, to answer the last question: Warps are skipped for four reasons:

1. Important data is missing, for example location or name. There is absolutely nothing that can be done in that case.
2. The warp cannot be connected with a loaded world, which means there is no world with a name as stored in the old database. This can be fixed by renaming an existing or creating a new world with such a name.
3. No unique ID can be found for the player who created the warp. The names are resolved directly from Mojang's servers when importing. If these do not know a player, he might either have changed his name (?) or has no paid account. In both cases, there is nothing that could be done.
4. The warp is exported successfully, but a warp with that name already exists which is why it cannot be imported. Simply remove or rename the existing warp and it should work fine.

In every case, you should see precise information about what is going on logged to the console.

[veteranmina]

Alright makes sense, again thank you very mush for the support. It's nice to see developers like yourself this helpful!