Trying to connect to localhost:15000 [SF2010] Dedicate server

Hello, when I turn on the server [/ start],
I have everything correctly, but writes that: connect: connection refused

Syslog:
Jun 22 05:20:49 :: SYSTEM: Trying to connect to localhost:15000
SYSERR: Jun 22 05:20:49 :: socket_connect: HOST localhost:15000, could not connect.

Firewall not blocking this port.

Auth:

HOSTNAME: auth
CHANNEL: 1
PORT: 11002
P2P_PORT: 12000
DB_PORT: 15000 or 15001 (when is it port 3306 so it does not write: refused connect, but can not login.)
DB_ADDR: localhost
TABLE_POSTFIX:
ITEM_ID_RANGE: 000000001 000000002
PASSES_PER_SEC: 25
SAVE_EVENT_SECOND_CYCLE: 180
PING_EVENT_SECOND_CYCLE: 180
AUTH_SERVER: master
PLAYER_SQL: localhost mt2 mt2!@# account
COMMON_SQL: localhost mt2 mt2!@# common
LOG_SQL: localhost mt2 mt2!@# log


DB:
SQL_ACCOUNT = "localhost account mt2 mt2!@# 0"
SQL_PLAYER = "localhost player mt2 mt2!@# 0"
SQL_COMMON = "localhost common mt2 mt2!@# 0"
SQL_HOTBACKUP = "localhost hotbackup mt2 mt2!@# 0"

TABLE_POSTFIX = ""

BIND_PORT = 15000 or 15001
__________________
Do you know?
____________
Thanks you for your answers. :-)

Channel1:

HOSTNAME: Channel1
CHANNEL: 1
PORT: 13000
P2P_PORT: 13000
DB_PORT: 15000 or 15001 (when is it port 3306 so it does not write: refused connect, but can not login.)
DB_ADDR: localhost
TABLE_POSTFIX:
ITEM_ID_RANGE: 000000001 000000002
PASSES_PER_SEC: 25
SAVE_EVENT_SECOND_CYCLE: 180
PING_EVENT_SECOND_CYCLE: 180
PLAYER_SQL: localhost mt2 mt2!@# player
COMMON_SQL: localhost mt2 mt2!@# common
LOG_SQL: localhost mt2 mt2!@# log

Do you know? :-(

Control the database maybe a table is broken.

i have the same prblem

Yes you must create the right mysql user!

when you look at your Configs you see "mt2" an "mt2!@#"

mt2 = user

mt2!@# = pw

set all rights to the user and try again

Hm, I have the same problem. My server was OK, but once when I started something went wrong and I got the same error. I reinstalled everything but it doesn't work anymore, Although everything is the same.... What does that problem exactly cause?

upp

Look at "db" syserr :)