Howdy. That Debian 7 instruction was (mostly?) written by me, so hopefully I can help you out.
That symptom sounds like a zone server concern. Getting to world select takes a certain port, and to select a character and enter in game is a hand off to your zone server. If it locks up, never shows a load screen, and eventually boots you to login (or crashes) it may be zone server related. I'd watch the console to see if your zone server instances say anything as the player joins up, a zone server should pick up the hand off from world server the moment you join in game.
First guess: Port related, by default zone servers use a range (7000+) of TCP/UDP connections for communicating, they may not be forwarded properly.
As for logging, in game there's some handy ways to control logging. Since you can't join, it isn't too useful. I'm leaning towards port still, though, unless your zone server is doing a "segmentation fault" or other type of crash.
The process of starting up a server has changed quite a bit since I wrote that debian 7 instruction (I should update it), the eqtime.cfg issue may be permissions, it may be the file doesn't exist, at some point eqtime was moved to DB as well, and if you follow my steps, you get latest copy of eqemu/server, yet if you get the latest peq, it's an august snapshot, so may need to run the world's DB updater to possibly fix the eqtime issue. But, the inability to get in game is not correlated to this error. Keep an eye out for any red text on the world or zone server bootup.
Also, run shared_memory once if you haven't.
|