Hypopathetically speaking, what's the age limit on a database this will upgrade? I see your in your example pic it starts with updates from 2013, anyone run Zeb/Squeeker/older stuff through it for giggles?

Thanks for reminding me, I have the manifest built through all of Github updates. I need to configure the manifest to understand all of the upgrades through SVN.

So technically when I have that done, it should take a super old database all the way up to recent with ease.

Akka's Funhouse for example was just old enough to be a few months ahead of when we started with Git, so I took a 2 year old database and brought it to recent within seconds. Very very nice thing to have.

Just compiled and updated. This worked flawlessly, thank you for adding this feature!

I just wanted to mention that this works GREAT!

For around 20 total hours I tried every guide I could find, every list of steps, to update halls havoc database correctly. Everything I tried would have errors in various sql scripts. Then when it apparently worked, there were things obviously wrong. Things like inventory disappeared completely and all items seemed to be unavailable, yet the items table was full of items. I ended up resurrecting a an old database save from before I started trying to update, and then sourced the data then ran the server.

The automatic updater worked perfectly!


I think there is so much obsolete information out there now, that it is difficult to figure out exactly what to do. This auto-updater is a GREAT feature!

Excellent work, all!

Rick HallsHavoc

This only works if the database runs on the same host as the world server. Your script grabs host from the config file, but never actually uses the $host variable in your mysql commands.

Since it also auto-downloads db_update.pl I can't even fix the script as my changes get overwritten.

Run your updates on the world server?

The world server and the database server are not the same host. You should simply modify the script to add --host="$host" to the various mysql command lines and that would solve the issue.

As a work-around, I've simply set the MYSQL_HOST environment variable prior to running ./world

Even then, the script still doesn't fully update the database (coming from peqbeta_2014-10-11-02:01.sql) as apparently that database is missing some core tables like character_buffs so there are 8 required updates which fail to apply. Not really a problem with the script, per-se, although I'm surprised there isn't a simple empty schema included with the source that one could apply to build an empty, clean and current database so that this whole patch process wouldn't be necessary for a brand new installation. Relying on PEQ to provide the base schema seems silly.

But there are warnings all over the place not to use the October 2014 version of the database. You need to use the September version...

I have yet to see any of those warnings. Other than the one I posted after I figured it out the hard way.

Regardless, that has nothing to do with the fact that the update_db.pl script parses the configuration file for <host> and then ignores it, only working on localhost unless you set the MYSQL_HOST environment variable.

This is a bug in the script, regardless of which peq db one uses (or even if one doesn't use peq at all!)

Wouldn't necessarily call it a bug.

It pulls it down automatically because I've set it that way for a while because at one point the script wasn't capable of checking itself for updates by being passed parameters by the source, could probably change that soon.

Also, why are you using multiple hosts? It's far unecessary unless you actually have load to match the necessity.

98% of the folks who run the script aren't going to need a host option and would simply run it on their database server.

Updated, you're welcome.

https://github.com/EQEmu/Server/comm...a6e1e00cc91214

And

This has to do with PEQ dumps, the schema update does exactly what it needs to do and PEQ missing tables is another issue in itself. I will notify those who oversee those dumps.

I run on multiple hosts because I have multiple hosts already setup in a variety of roles. My DMZ host (where I run eqemu) doesn't run mysql. I already have it running on an internal host and adding the eqemu database to that makes the most sense for my environment.

This is not working for me and I cant seem to find out what is wrong. It downloads all the database updates but doesn't seem to apply them.

Did you select option 3 at this point?

Yes, I select option 3 and it downloads the updates even if I already have them in the db_update folder. I select option 3 again and I get several "The system cannot find the path specified." errors.

Little bit more detail please.

What OS?

Have you ran these updates before?

etc.