Quote:
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.