Automatic Database Upgrade and Versioning

[pfyon]

Just FYI, my old start script redirects the output of all the binaries (world, zone, etc) to a logfile. Turns out when this starts, it prompts for user input if there are updates.... and continues to prompt. 16GB logfile later I discovered this and killed it.

So anyone who redirects output to a logfile, beware.

[Akkadius]

Originally Posted by pfyon

Just FYI, my old start script redirects the output of all the binaries (world, zone, etc) to a logfile. Turns out when this starts, it prompts for user input if there are updates.... and continues to prompt. 16GB logfile later I discovered this and killed it.

So anyone who redirects output to a logfile, beware.

These are the sorts of things that I need to fix and be brought to attention.

I'm assuming this is Linux.

If your database is up to date you won't have that issue since it will not wait for a prompt.

Can you reproduce to me what the contents of the log is? I'm going to guess its reprinting the menu because the start script is sending characters.

[trevius]

Originally Posted by pfyon

Just FYI, my old start script redirects the output of all the binaries (world, zone, etc) to a logfile. Turns out when this starts, it prompts for user input if there are updates.... and continues to prompt. 16GB logfile later I discovered this and killed it.

So anyone who redirects output to a logfile, beware.

Had this same issue, so Akkadius was already aware and it will be resolved. Until it is fixed, you can get around this by starting world manually the first time after you update by doing the following:

./world

Then you can respond to the prompts, update your db and CTRL+C to end the process. Finally, use your startup script again as normal and you will be running without issues (at least until the next update).

[pfyon]

Originally Posted by trevius

Had this same issue, so Akkadius was already aware and it will be resolved. Until it is fixed, you can get around this by starting world manually the first time after you update by doing the following:

./world

Then you can respond to the prompts, update your db and CTRL+C to end the process. Finally, use your startup script again as normal and you will be running without issues (at least until the next update).

Yeah, I realized the issue after waiting about half an hour and doing a df -h. And yes, linux.

Ultimately, I was bringing my source up to date and my database is all screwed up because I guess bots are screwed up right now? So it was never able to run all the updates properly.

[Akkadius]

Originally Posted by pfyon

Yeah, I realized the issue after waiting about half an hour and doing a df -h. And yes, linux.

Ultimately, I was bringing my source up to date and my database is all screwed up because I guess bots are screwed up right now? So it was never able to run all the updates properly.

Are you running bots currently?

[pfyon]

Originally Posted by Akkadius

Are you running bots currently?

I was, but that was around 6 months ago. I had to rebuild my vps and am just getting around to getting eqemu back up now.

[Akkadius]

Here is a fix for linux users. Replace your start script as such:

http://wiki.eqemulator.org/i?Module=...Paste=xRJzfmq2

It will run the update routine before ever triggering world, which will all the user take care of updates, exit the program and then everything will continue to flow and start the server up every single time until you decide to upgrade.