r2182 build problem

[biboy]

I will try that thank you. As soon as as I finish testing a fresh install of ff11 according to our Troubleshooting guide. I'm not worried about time spent, I wanted to check if the guide really works. After client side I will try it thank you.

[biboy]

ok, tested 2179 item_mods.sql on 2183 build and DSGame-server loads fine. Thank you for all the input. If I load item_mods.sql then build it again, it does crash again though. Ok have to finish this client side re-intallation. fun fun fun.

[metronet]

the messed up was rev. 2181

edit: with a july patch client - 2181 onwards is intended to be used with dec. patch, so it will be broken on july patch

can you guys test the item_mods crash on rev. 2180 only?

I think the segfault happens at the dsgame process startup, before any client could connect to it. According to strace it crashes right after it did a select sql query...

The workaround appears to work with both client version 3 & 4 (December update?); although I did not do much QA testing myself

[bluekirby0]

I also cannot make this break on my windows box. I'll try on my Lubuntu box, though I don't see anything in that update that could cause these problems.

[diminish]

I was also having the same issue with my server instantly crashing on r2180. I have a question though, is it required for the server machine to have ffxi installed on it, and if so does ffxi need to be fully updated? Will r2180 crash with no client on the server machine? I have ffxi installed on my server machine but i log in on a separate PC. I will try updating ffxi on my server machine. Side note, if i rebuild with visual studio it works fine and game server wont crash, but i will try updating ffxi on my server machine then try again with dsp updater

[metronet]

I run dsgame on a separate box (Debian VM on a ESX chassis) and have gone back to as far as r2156 and with the same item_mods.sql change it segfaults when it started to do the select statement.

However, that might not be a legit test as I don't know enough about this application

[bluekirby0]

The client is absolutely NOT needed on the server system.

[anglos]

Running the following script fixed the issue on my end:

Code: Select all

DELETE FROM item_mods WHERE itemId NOT IN (SELECT itemid FROM item_basic);

So my guess is it was trying to link item mods to items that don't exist in your database.

[whasf]

I had the same problem on the old-school server, I ran the delete and it's loading. See below:

Code: Select all

select * FROM item_mods WHERE itemId NOT IN (SELECT itemid FROM item_basic);

gets me:

Code: Select all

"itemId"	"modId"	"value"
"10552"	"73"	"2"
"10281"	"369"	"2"
"10282"	"369"	"1"
"10288"	"369"	"1"
"10467"	"369"	"1"
"10492"	"369"	"1"
"10564"	"369"	"1"
"11876"	"369"	"1"
"27788"	"369"	"2"
"27791"	"369"	"2"
"27792"	"369"	"2"
"27797"	"369"	"2"
"10468"	"370"	"3"
"10491"	"370"	"2"
"11875"	"370"	"1"
"27788"	"370"	"2"
"27931"	"370"	"2"
"28069"	"370"	"1"

So there are mods for items that dont exist!

[biboy]

same problem still exists in 2189, 2180 started the issue i think. Using item_mods.sql from 2179 with the 2189 causes another issue. As suggested I tried that but if you talk to any npc, your character switches to a different model, you nations flag appears on your head like in balista, and your name shows a question mark. You also unable to switch equipment and cannot access your ws and ja. All these problems are all gone when I reverted back to 2179. I can't quite explain it right but maybe maybe the issue will be fixed soon. Thank you team. good luck.