When I run worldserver, it exits immediately with no messages at all. I've been searching around the forums and seen similar problems reported a few times, but they're always accompanied by error messages. I don't have any. No error messages and no log files. No output at all.
Does anyone have any idea what might cause this kind of problem or what I might do to help me figure it out?
Ubuntu Linux (12.10)
branch 4.3.4, commit 904fa5b47b
TDB 434.05, commit e07faffe7a
I followed through the How-to_Linux step-by-step adjusting when necessary for the 4.3.4 branch. Everything went smoothly.
I followed through the TDB 4.3.4 + DB Updates How-to also and everything went smoothly except for a minor problem with the auth DB updates.
I've dropped and reloaded the databases a couple of times without success.
I added the SQLDriverLogFile entries to my worldserver.conf. There wasn't any reference to these entries in the worldserver.conf(.dist) that I got from the repo, but I added them based on the example worldserver.conf provided in the wiki. I set all the logging levels to trace. This also had no effect.
I ran worldserver with a bogus -c argument and I did get the "Invalid or missing configuration file" message, so I think that confirms that it's reading the proper conf file. This file is read from TrinityCore/conf, not in TrinityCore/server/etc as suggested somewhere in one of the wiki entries.
Using netstat, I confirmed that there's not already a service listening on port 8085. Just in case, I tried changing the WorldServerPort anyway. No joy.
I ran worldserver with strace and I can confirm from that output that it's reading the configuration file and running several SQL commands.
I looked at Main.cpp for worldserver and a few other files. I can see that it should be logging with the TC_LOG_* functions, but I don't understand what I'm reading well enough yet to figure out why it's not working. I'm certain it doesn't fail until it executes sMaster->Run(), but again I can't figure that out yet.
The exit status of worldserver is 1 which is indicated in the code as "shutdown at error". That's useless at this point unless there's some logging.
Thank you.