L2J Server

Hi, we have closed beta test server with 50-60 characters - beta testers.
We want to update everyday the server with last nightly version of Server and Data pack while
keeping old accounts.
What is the fastest and safe way to do it ?

(in l2jserver readme.txt i can not understand it: "- edit and run update in the tools folder" in tools folder no file or something like "update")

1. Using Eclipse or any other Java compiler, manually enter the changes listed in the code page for each new changeset and compile.

or

2. Using Eclipse or Tortoise SVN or any other SVN software, download the latest SVN and compile. If you had custom mods/addons, you'll need to re-run those patches before compiling.

Run the database installer and choose the upgrade option and automatically apply the updates when prompt to do so.

Note: You may want to dump your SQL databases nightly or twice a day if you have activities on the accounts daily. I do it twice a day.

its okay but how to do it using nightlies not SVN http://www.l2jserver.com/nightly/

or it's impossible ?

*we want test only clean L2J Nightly Builds - no mods/addons or customization

Same process, the only difference with nightly builds is that it's ALREADY compiled. An option would be:

1. Overwrite the existing server files while server is down. Run the database installer to upgrade, when prompted to automatically apply updates, choose Yes.

I would still recommend dumping your SQL databases in case you screw up.

After update - what is the best way to solve errors like:

Can't DROP 'acc'; check that column/key exists
Unknown column 'access_level' in 'accounts'
Table 'l2jdb.augmentations' doesn't exist

Upgrade option in database installer not work accurate, any solution ?

If you are ugrading from an existing official L2J core/dp, you should not have any errors with the update. Sounds to me like you are running server files that are not official L2J core/dp files. Where did you get your original server files? You are missing tables which leads me to believe that you are using someone else's files instead of files from this site.

However, in case you are using files from this site, try this:

Create a new folder and unzip core and dp into it. Configure gameserver and loginserver as normal, then create a different database (clean), next import your existing database into the new database you just created. If all this sounds weird to you then I can only suggest that you learn more about basic MySQL usage. A basic understanding of MySQL goes a long way in running your own server.

it's all just for test, we want test everyday nightly versions

1. Day 1 - I download form here: http://www.l2jserver.com/nightly/
Server Version= 3395
Datapack Version= 6497
2. Install server - All work fine
3. Day 2 download new versions again from here: http://www.l2jserver.com/nightly/
Server Version= 3396
Datapack Version= 6498
4. Unzip and copy them over the server files from Day 1
5. Run the database installer and automatically upgrade
6. Receive errors.
I think auto-upgrade option in database installer not work 100% accurate.
****************************
But, It's okay for now because second way work 100% with NO ERRORS.

Just question is: When i backup base what is better: "Backup" or "Dump SQL file". And when import what is better "Execute Batch file" (SQL dump of old base) or "Restore backup" function.

May be Execute "fill in" new base with old values, but Restore overwrite all tables. Is it correct ?

Thanks allot for help and answers.

But, It's okay for now because second way work 100% with NO ERRORS.

Just question is: When i backup base what is better: "Backup" or "Dump SQL file". And when import what is better "Execute Batch file" (SQL dump of old base) or "Restore backup" function.

Personally, I don't think there is a best or preferred way of doing a backup. As long as you have a backup of the database you can restore or import from when disaster strike is the most important...imo. However, I do daily SQL dumps using a small batch file I wrote up and then use Task Scheduler to schedule back up date(s)/Time. Also, every two weeks or so I will also back up the actual database files under MySQL\DATA.

May be Execute "fill in" new base with old values, but Restore overwrite all tables. Is it correct ?
Thanks allot for help and answers.

That depends I guess on what you're trying to accomplish. If your database crash, you would want to restore and overwrite all tables. If your database is fine and there are new table values and such then I would suggest doing updates "fill in" for those particular tables only. I am not entirely sure I understand the question correctly but I think that is what you meant.

I am glad you finally got your database up and running without errors. Good luck.

ksmxbg wrote:it's all just for test, we want test everyday nightly versions

1. Day 1 - I download form here: http://www.l2jserver.com/nightly/
Server Version= 3395
Datapack Version= 6497
2. Install server - All work fine
3. Day 2 download new versions again from here: http://www.l2jserver.com/nightly/
Server Version= 3396
Datapack Version= 6498
4. Unzip and copy them over the server files from Day 1
5. Run the database installer and automatically upgrade
6. Receive errors.
I think auto-upgrade option in database installer not work 100% accurate.
****************************
But, It's okay for now because second way work 100% with NO ERRORS.

Just question is: When i backup base what is better: "Backup" or "Dump SQL file". And when import what is better "Execute Batch file" (SQL dump of old base) or "Restore backup" function.

May be Execute "fill in" new base with old values, but Restore overwrite all tables. Is it correct ?

Thanks allot for help and answers.

4. Unzip and copy them over the server files from Day 1 <----here is the trouble...

Day 1 files should be deleted completly.

------------------------------------------------------------------------------------------------------------------------------------

now about... 6

6. Receive errors.
I think auto-upgrade option in database installer not work 100% accurate. <--- this is not a issue, auto-upgrade works 100%, you always will receive errors, is normal

More than likely the Upgrade is executing a sql script that is older than your current db. In your error, "access_level" used to be the name of a column in the accounts table. At some point that column name was changed to accessLevel. The update script is trying to do this again.

Just take a look at the .sql files.

Why to update daily?

The trunk nightly is a nuclear test sandbox, one single buggy commit could broke your server and piss off all your users more that you can imagine.

Montly Updates are the best in my opinion, unless something really good appeared on the trunk to update on less than a month.

Imho ideal combination is:

T = 2 + K * (1 / N )

In which:

• N is the number of times that the administrator visit l2j trunk and forum per day
• K is an adimensional constant
• T is time in days between every update

Basically, what you can afford depending on your administrator/java experience but never more frequently than once every 2 days

ThePhoenixBird wrote:Why to update daily?

The trunk nightly is a nuclear test sandbox, one single buggy commit could broke your server and piss off all your users more that you can imagine.

Montly Updates are the best in my opinion, unless something really good appeared on the trunk to update on less than a month.

totally agree =)

ThePhoenixBird wrote:Why to update daily?

1-st post - L2J server for testing purposes only