Changing the default database port?
In the interest of running another unrelated database server that wants to use port 3306 on the same box as my EQEMU server, I tried changing eqemu's database to port 3304 so they wouldn't fight for a binding. The world.exe component did not like it. Given the database port is definable in the config files, I assume this is unintended and should be possible.
I started with a healthy install, current build. I had been using it to play for a couple weeks, so it was validated to be fully operational.
I shut the server down via the batch script.
I edited the database port via the my.ini (port=3306 >> port=3304) on both lines.
I edited the database port where defined in eqemu_config.json and login.json.
I rebooted the host, and after reboot I launched the start_server script.
The new port is listed on all the server component windows where it's output. Most of these windows seem to have been fine with the change, with the exception of eqemu\bin\world.exe which breaks, then erroneously starts downloading every database table update (that had already been applied) and then outputs error after error as it slowly fails at installing every single one of them.
The latter issue seems simply an improper error handling, which I wouldn't be hitting if it was successfully querying the db_version in the first place.
The impression I have is that something is hard-coded to port 3306. What makes it weirder is that you even see the new port referenced in the init info for the world.exe window.
[World] [Info] Loading server configuration
[World] [Info] CURRENT_VERSION: [2.0]
[World] [Info] Added loginserver [redacted_ip]:[5998]
[World] [Info] Connecting to MySQL [root]@[127.0.0.1]:[3304]
[World] [Info] [MySQL] Connection [default] database [peq] at [127.0.0.1]:[3304]
[World] [Info] Loaded [77] log categories
[World] [Info] Starting File Log [logs/world_2936.log]
[World] [Info] Checking Database Conversions
[Update] No script update necessary
[Info] For EQEmu Server management utilities - run eqemu_server.pl
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (10061 "Unknown error")
[Database] Table 'db_version' does not exist.... Creating...
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (10061 "Unknown error")
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (10061 "Unknown error")
...etc
Note: I can connect to the database on the new port using the HeidiSQL session manager, as a primitive sanity-check that the database is accessible.
|