[Solved] TDP 2.8.7 - DC while using 3. Inventtab, premiumtype 1

[Alphakilo23]

Hello there,

im having a hard time tracking down an error on my cabalserver.

When a user with premiumtype 1 tries to put an item on his third invent- or warehousepage he'll get disconnected with an errorcode 6 type 159. All other premiumtypes works (e.g type 4).

Heres what happens serverside:

Spoiler:

[Fri Jul 2 2010 01:21:41.602724 7260656]: 1.open user 11 [A6F74B8] (***.***.***.***)
[Fri Jul 2 2010 01:21:49.034728 34454416]: AntiAddictInit UserNum:410, CharIdx:3280, IsAdult:1, PersonId:0, PlayTimeMin:0
[Fri Jul 2 2010 01:21:59.041461 34454416]: [##ERROR##] CheckInvenItemSlotByServiceType(): CharacterIdx(3280), sloatIdx(129)
[Fri Jul 2 2010 01:21:59.049515 34454416]: [##ERROR##] 'OnCSCItemPutting' fail (Proc/Inventory.cpp:2882)
[Fri Jul 2 2010 01:21:59.049575 34454416]: [##ERROR##] UsrMap Fail : MainCmd(159) Ret(290B42:41:2882) Addr(***.***.***.***)
[Fri Jul 2 2010 01:21:59.050937 7260656]: sock 11=> close by finish waiting(***.***.***.***)
[Fri Jul 2 2010 01:21:59.051165 7260656]: 1.close user 11 [A6F74B8] (***.***.***.***)

[Fri Jul 2 2010 01:21:50.004360 3086666224]: 2.open user 10 [8753030] (***.***.***.***)
[Fri Jul 2 2010 01:21:54.003420 3044432784]: Enter(): ok. charIdx(3280), guildNo(1), (Alphakilo23)
[Fri Jul 2 2010 01:21:59.682677 3033942928]: Leave(): charIdx(3280), guildNo(1), (Alphakilo23)
[Fri Jul 2 2010 01:21:59.683036 3086666224]: sock 10=> close by finish waiting(***.***.***.***)
[Fri Jul 2 2010 01:21:59.683220 3086666224]: 2.close user 10 [8753030] (***.***.***.***)

I have two servers, my liveserver (SQL 2008, CentOS 4.8 with TDP 2.8.7) and my testserver (SQL2008, CentOS 5.5 also with TDP 2.8.7).
The first time this error occured was after i updated the liveserver from v2.5 to v2.8.7.

Heres a list of things i tried so far:

1. Using a clean installation of the client w/ the patchfiles from the server;
2. Installing clean 2.8.7 serverfiles
3. Installing clean 2.8.1 serverfiles and upgrading to 2.8.7;
4. Using clean databases;
5. USing SQL-Server 2000 w/ clean databases;

Nothing fixed the error. Thats one persistant little bit^H^H^H bug.

[MentaL]

[Alphakilo23]

Today, while stumbling upon this thread, I got an idea.

I ran a quick diff on the (/etc/cabal/Data/)Const.scp from the 2.5 final release versus the new one aaaand bingo:


So I deleted line 304 from the new Const.scp and restarted the server. To my own suprise, the server started without moaning and the problem was gone.

There is however a small limitation:
If you change your rates, your fix will be overwritten.
So in order to make this change permanent, you may also want to edit the /etc/cabal/templates/Const.cfg

Delete the following line:

1	0	4	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0

Disclaimer:
Don't consider this a fix, it's a dirty hack.
I havent really tested this so far, so I can't guarantee for stability or if the server gains self-awareness and starts eating kittens and/or users.

[tikkaroe]

2.8.7 where to get it

[Alphakilo23]

You can get it from chumpys mediafire page:
http://www.mediafire.com/chumpy

[Xc0deRed93]

I think its its 2.8 not 2.8.7 the 7z there is extension file name xD ;)

[chumpywumpy]

That bug (and a similar warehouse bug) exist in 2.8 because i merged the wrong tables into const.scp. v2.81 has a full fix and there should be a patch. I have removed the server patch from my mf page for some reason but if you copy const.scp from v2.81 and caz.enc/caz_msg.enc from the 2.81 client patch that will give you the proper fix.

[tikkaroe]

oh thank, i think chumpy has new release