EQEmu on Fedora 22 Server Minimal Guide

[Akkadius]

You need to make sure that you are running world in context of your server directory

Also, make sure the user you are using to run world can also make folders and files. Beyond that make sure the db_update folder can be written by anything if that doesn't fix it. The db_update.pl script that gets ran by world needs to be able to save files and use them to work with them.

[camryfu]

Originally Posted by Akkadius

You need to make sure that you are running world in context of your server directory

Also, make sure the user you are using to run world can also make folders and files. Beyond that make sure the db_update folder can be written by anything if that doesn't fix it. The db_update.pl script that gets ran by world needs to be able to save files and use them to work with them.

Yes, I run loginserver, world, zone all in server directory:







and the folder own is same user (eqadmin):



it should be written in that folder.

[camryfu]

Because of no more update need after world startup, I try to re-run client to seek for luck, but crash again.

[Akkadius]

Are you sure that the updates ran? If they aren't able to pull down the manifest and the update files during the update, you may have not actually had anything updated at all.

When the manifest gets pulled down (First option 3 run) you should also see all of the updates you are missing in the same run.

Second run will then apply those updates.

I would set your db_version 'version' column to 0 and run it again manually. If you're missing database schema updates that can cause a client crash inevitably.

If you're completely updated for sure and your client is still crashing, you could have a corrupt character and I would try to make another after you are fully updated.

[camryfu]

Originally Posted by Akkadius

Are you sure that the updates ran? If they aren't able to pull down the manifest and the update files during the update, you may have not actually had anything updated at all.

When the manifest gets pulled down (First option 3 run) you should also see all of the updates you are missing in the same run.

Second run will then apply those updates.

I would set your db_version 'version' column to 0 and run it again manually. If you're missing database schema updates that can cause a client crash inevitably.

If you're completely updated for sure and your client is still crashing, you could have a corrupt character and I would try to make another after you are fully updated.

I set version to '0' and re-update:





then re-run client, it still crashed.

[camryfu]

re-run world, it seems up to date: