Connection problems

[gpadmin]

Hello all. Server work last 3 months, no problem. But now i cant connect ot server. I am never change. Have error in GlobalDBAgent.log.

What i find. When you trying to connect first time, you cant. When you trying to connect second time have error. Message from server - The ID in already in use. Push YES, but not help.

After first connect, DB change collum cabal_auth_table/login to 1, and dont drop flag to 0 anymore... strange.

You can made new acc. on server and play, but OLD acc. not work anymore.

[Sun Jul 12 2009 09:44:01.827802 3086550720]: open log file '/var/log/cabal/GlobalDBAgent.log'
[Sun Jul 12 2009 09:44:01.828158 3086550720]: LOG LEVEL: 3
[Sun Jul 12 2009 09:44:01.828227 3086550720]: MemPoolUnitSizeClass(0): 14336Bytes
[Sun Jul 12 2009 09:44:01.831025 3086550720]: Start GlobalDBAgent Server
[Sun Jul 12 2009 09:44:01.835216 3086550720]: UseEcryptText (Off)
[Sun Jul 12 2009 09:44:01.842799 3086547872]: CProcessLayer(0)::svc Start [3086547872]
[Sun Jul 12 2009 09:44:01.843087 3076058016]: CProcessLayer(0)::svc Start [3076058016]
[Sun Jul 12 2009 09:44:01.843929 3065568160]: CProcessLayer(0)::svc Start [3065568160]
[Sun Jul 12 2009 09:44:01.844139 3055078304]: CProcessLayer(0)::svc Start [3055078304]
[Sun Jul 12 2009 09:44:01.844980 3044588448]: CProcessLayer(0)::svc Start [3044588448]
[Sun Jul 12 2009 09:44:01.845113 3034098592]: CProcessLayer(0)::svc Start [3034098592]
[Sun Jul 12 2009 09:44:01.845909 3023608736]: CProcessLayer(0)::svc Start [3023608736]
[Sun Jul 12 2009 09:44:01.846798 3013118880]: CProcessLayer(0)::svc Start [3013118880]
[Sun Jul 12 2009 09:44:01.847133 3086550720]: try listening 38180 port
[Sun Jul 12 2009 09:44:01.848068 3002629024]: CProcessLayer(0)::svc Start [3002629024]
[Sun Jul 12 2009 09:44:01.848907 2992139168]: CProcessLayer(0)::svc Start [2992139168]
[Sun Jul 12 2009 09:44:03.150711 3086550720]: accept success 8(127.0.0.1:32825)
[Sun Jul 12 2009 09:44:03.155790 3086550720]: 1.open user 8 [A0EDAB8] (127.0.0.1)
[Sun Jul 12 2009 09:44:11.947843 3086550720]: accept success 10(127.0.0.1:32833)
[Sun Jul 12 2009 09:44:11.948728 3086550720]: 2.open user 10 [A0FC1F8] (127.0.0.1)
[Sun Jul 12 2009 09:46:48.309918 3044588448]: Database Connect success!
[Sun Jul 12 2009 09:46:56.460224 3076058016]: Database Connect success!
[Sun Jul 12 2009 09:46:56.463826 3076058016]: [##ERROR##] OnIPCAuthAccount fail (usernum: 0)
[Sun Jul 12 2009 09:46:56.463913 3076058016]: [##ERROR##] DB ERROR(MSG) : [FreeTDS][SQL Server]Difference of two datetime columns caused overflow at runtime.
[Sun Jul 12 2009 09:46:56.463965 3076058016]: [##ERROR##] DB ERROR(CODE) : 535
[Sun Jul 12 2009 09:46:56.464014 3076058016]: [##ERROR##] DB ERROR(VAR_INFO) :
[Sun Jul 12 2009 09:46:56.464063 3076058016]: [##ERROR##] DB ERROR(SQLSTATE) : 22007
[Sun Jul 12 2009 09:46:56.464112 3076058016]: [##ERROR##] DB ERROR(STM_TEXT) : {call cabal_sp_auth( ? , ? , ? , ? )}
[Sun Jul 12 2009 09:46:56.483374 3076058016]: Database Connect success!
[Sun Jul 12 2009 09:46:56.483681 3076058016]: [##ERROR##] 'OnIPCAuthAccount' fail (Database/Auth.cpp:283)
[Sun Jul 12 2009 09:46:56.483767 3076058016]: [##ERROR##] UsrMap Fail : MainCmd(30) Ret(11B:0:283) Addr(127.0.0.1)

Someone have idea what happen?

Thank you for help. Sry for not perfect english : )

[MentaL]

[chumpywumpy]

It sounds like a date format on either centos or windows isn't translating to sql properly. What timezone settings are you?

[gpadmin]

Hello chumpywumpy

On my sql server i add GMT+7 (Krasnoyarsk) on my cent OS add Moscow +4 = its same i think.

Add:
Tnx chumpywumpy
I am remade time zone for server and sql server and set to 0 collum in cabal_auth_table/login and set to NULL collums:
[LoginTime]
[LogoutTime]

Work now, but i am test it on my GMaccs. I am ask players check old acc. waiting info. Tnx chumpywumpy for idea : ))))

Eh damn. Problem still actual for some acc's. Cant undestand why...

chumpywumpy what you mean?
"a date format on either centos or windows isn't translating to sql properly"

how translate it corect??? i have at the moment same time for sql and centOS servers.

[chumpywumpy]

SQL server uses a specific date format (2009-07-15 11:00:25.000) and some date format settings don't convert to that format well. One example i saw recently was a windows machine that had a normal date format but the time shoed like 0430PM and without the : in the time the server couldn't translate to the right format for the db.

Setting the columns to allow nulls should not be necessary and at best it _might_ stop the SQL server complaining (probably not though). The proper fix is to work out why SQL can't translate the date format it is being given into SQL format. You might be able to set the date format on the windows and centos machine but the better way would be to use the SQL profiler so you can see exactly what values cabal_sp_auth is being given.