View Single Post
  #1  
Old 07-23-2015, 12:41 AM
ahamilton634's Avatar
ahamilton634
Sarnak
 
Join Date: Jul 2015
Location: Sunny California
Posts: 30
Default MySQL path not found, please add the path for automatic database upgrading to con...

There appears to be a problem accessing the database. When I launch the server this is what pops up.

Quote:
[World Server] Loading server configuration..
[World Server] CURRENT_VERSION: 1.1.3
[World Server] Added loginserver login.eqemulator.net:5998
[World Server] Connecting to MySQL...
[World Server] HTTP world service disabled.
[World Server] Checking Database Conversions..
[Upgrade Script] No script update necessary
Perl Version is 5.12.3
MySQL path not found, please add the path for automatic database upgrading to continue...

Exiting...
[World Server] Loading variables..
[World Server] Loading zones..
[World Server] Clearing groups..
[World Server] Clearing raids..
[World Server] Loading items..
[World Server] Loading skill caps..
[World Server] Loading guilds..
[World Server] Loaded default rule set 'default'
[World Server] Loading EQ time of day..
[World Server] Loading launcher list..
[World Server] Reboot zone modes OFF
[World Server] Deleted 0 stale player corpses from database
[World Server] Loading adventures...
[World Server] Purging expired instances
[World Server] Loading char create info...
[World Server] Zone (TCP) listener started.
[World Server] Client (UDP) listener started.
[World Server] New TCP connection from 127.0.0.1:49337
[World Server] New TCP connection from 127.0.0.1:49339
[World Server] New TCP connection from 127.0.0.1:49340
[World Server] New TCP connection from 127.0.0.1:49342
When I try to connect using the client it just sits there and kicks me. It doesn't say I'm being added to the database.
I've triple checked to make sure the password/db name is correct and made sure the ports were forwarded. I tried changing the password but not updating eqemu_config.xml and it reacted differently so it sees the database but it has trouble accessing it and perhaps updating it? I'm somewhat new to this. I ran a server several months back and it worked just fine. I tried re-sourcing the database and it started doing this.
It's also having trouble connecting using the EOC but Navicat has no problem connecting using root@localhost.
Reply With Quote