Database error(s)

[stinkbeer]

Ok here are my config files:


db.ini

[Database]
host=localhost
user=username (no root)
password=password
database=eq1

Loginserver.ini

[LoginServer]
loginserver=127.0.0.1
loginserver2=newlogin1.eqemulator.net
loginport=5999
loginport2=5998
worldname=EQemulator
worldaddress=localhost
locked=false
account=username (no root)
password=password

[WorldServer]
Defaultstatus=0
Unavailzone=

[ChatChannelServer]
worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=minilogin
ServerPort=5999

Boot5zones.bat

REM: REM: Read this first!!!
REM: This file requires your real IP in the place of "YourIP" when you are connecting
REM: To the EQEmu Loginserver.
REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1
REM: If you still get errors try using localhost instead of 127.0.0.1
REM:
@echo off
if NOT exist spells_us.txt goto NOSPELL
start zoneperl . localhost 8780 localhost
start zoneperl . localhost 8781 localhost
start zoneperl . localhost 8782 localhost
start zoneperl . localhost 8783 localhost
start zoneperl . localhost 8784 localhost
exit
cls
:NOSPELL echo You did not copy the spells_us.txt from your everquest directory to this one. Please do so or zones will crash on startup. PAUSE


End of files

[fathernitwit]

might help
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

if you find the solution, please post it on the wiki, this has been run into several times, but I cannot recall the solution

[johane]

Originally Posted by fathernitwit

might help
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

if you find the solution, please post it on the wiki, this has been run into several times, but I cannot recall the solution

Worth reminding people that if you have logging turned on in mysql, and have set to log hostnames (not just ip addresses), then unless you have good name resolution (i.e. right entries in /etc/hosts or equivalent, or a local nameserver with in-addr.arpa zones properly set up) you can get DB timeouts very very easily.

[sdabbs65]

Originally Posted by johane

Worth reminding people that if you have logging turned on in mysql, and have set to log hostnames (not just ip addresses), then unless you have good name resolution (i.e. right entries in /etc/hosts or equivalent, or a local nameserver with in-addr.arpa zones properly set up) you can get DB timeouts very very easily.

I think this is a bug with max packets in mysql 4.0 , I have never seen this happen with 3.0

[johane]

Originally Posted by sdabbs65

I think this is a bug with max packets in mysql 4.0 , I have never seen this happen with 3.0

I've seen it happen with windows clients and Linux based MySQL v 3.x, when the server was protected by tcpwrappers, and the windows machine had that "update the DNS" setting turned on. I can't recall the exact number of times I've walked Users through turning off that checkmark, or have talked to clueless ISP people ( I can't call them admins and still preserve my self-respect. How can you "admin" an ISP and not have a clue about basic DNS and Bind?) about how to setup their DNS so that the Dyn-IP update works.

But little of this is relevant to the OP. Still, checking the hosts file is a good idea - if it's the problem, then it's easy to fix.

[stinkbeer]

I have checked the host file and didn't find any problems with it.
Can reach my host with the Windows ping command without any problem.

Cause im not a database expert, I gona install Mysql 3.23, run the DB part of the tutorial again.

[stinkbeer]

Ok guy's,

With Mysql 3.23 no databasedrops anymore. (dont know why. But the latest version of Mysql is not gona work for me)

Now im gona try to get connected with the client.