SOF bug
 

For some reason anyone with SOF can't log on to my server.. I have no clue why. I have the .conf file in the directory. Can anyone tell me how to figure this out possibly ? Seems a lot of the players want to be able to log on but they can not due to this bug so I need to get it fixed ASAP would really appreciate any help anyone can give :)

Thanks in advance

Morty

I can only imagine it is your custom code to blame for it. All compatible clients work fine and have worked fine for a long time now.

Mort just download a clean source and start fresh(source wise). Ive seen your 'custom' code and there is nothing you are losing and everything to gain(especially since you have goons disabled).

A server op really shouldn't run custom code if they don't know how to code as it just leads this type of situation where your fall hundreds of revisions behind just to save alittle bit of morally grey code(like charging for a free feature, coded by others).

There is no custom code lol.. I run stock binary's the only thing that was custom was i changed #bot commands to #goon..

Anyway when i attempted to compile the latest build without any of that put in this is the error i got.. No clue how to fix this , anyone able to help ?

Where is the error?

I'm assuming it's this line

Could it be something of an issue where it's been in the past "Case Sensative Issues" where one thing will say maybe `bot::rocessClientZoneChange` instead of Bot::ProcessCLientZoneChange` , Linux is very touchy about Case Sensative letters..

Not sure , any thoughts ?

Well, C++ is case sensitive on all platforms.

Did you maybe build once without bots and then build again with bots without cleaning in between?

Try typing 'make clean' and then rebuild again.

Yeah I made sure to make clean before the make and no dice :(

still comes up with the same error.

Well, you have several errors when linking all seemingly related to bot functions, and I don't see bot.o in your link command which is where they would be.

Well i ran the SVN direct to this DIR what am i doing wrong ?

I first ran a "Make Clean"

then "Make"

and this was the error i got is it something to do with my Makefiles or ?

Only thing i changed was I386 to Native ..

Any help on this , can some one help me ? I really need to get these compiled because of the amount of crazy bugs that are in my current build.

Can you post your zone/makefile ?

Last i heard no one with SoD could log in either. You know it would be real painless and alot better on yourself and the few people who still play there if you just switched to windows.

Windows is not an option for me.

Here is my Makefile

Try adding bot.o and botspellsai.o to makefile.common in the zone directory where the rest of the .o files are listed.

Thank you that did it ! :)

Alright well, Even after upgrading to the LATEST build, replaced all the .conf files with current.. People can't log on except titanium to my server.. Any ideas why this might be happening ?

Could it be a Database Issue or something i'm missing.

Again thanks for the help in advance , glad I upgraded but this issue still looms

Mort

SoF and SoD use a different port by default. Did you open up your firewall for it?

All ports opened, but when some one zones in with SOD or SOF, the zone actually crashes.. this is a few of the core dumps

And this is from the debug_zone log

Bump

Any one have any ideas as to why this is happening ? I have ruled out Binary's by freshly upgrading, I have ruled out all of the .conf files. What else could this be ?

Really appreciate the help so far guys :) Just have to figure out whats going on with this. Why would Titanium be fine and not the other clients? What would cause that other than the 2 things i listed above ?

Morty

Just looking at your last post, my guess is something in the client is modified from the original SoF. Have you tried reinstalling the client?

It's everyone who can't connect it seems , neither with SOD or SOF.. and then when they actually try and connect it crashes the zone.. I posted some of the CORE drops above it seems to be something to do with Items or inventory or.. something but I am not sure what exactly.

Looks like your opcodes are missing or corrupt. Try replacing those files.

Looking at your core dumps, I would guess the problem is with items.

Your zones are crashing when loading inventory/items, so something with them being sent is causing it. You can find a little more information about the crash if you go through the frames and list the code around each frame.

Example:
To prove your issue is item related, I started a char on your server on Titanium and deleted all items on it. Then, exited and logged him in using SoD and got in just fine. Though, it looks like you clearly have other issues, because I got myself killed and it crashed the zone as well. I think that zone crash was probably related to the new respawn window. You might want to try disabling that in your rules once you get your items issue worked out.

I told him the same thing regarding items last week...

I don't know how far he went with this tho.

Right yeah they are both the same now , it could be something with some items added recently. I'll also have to go in and check out the inventory table.

Thing's I've done THUS FAR:

* Replaced all .conf files
* Gone to latest build
* Confirmed Items Table is the same as PEQ

Here are the two core drops from today , Assuming one of them is yours Trev :) thanks for the help testing.

I am not sure why it works for Titanium and not other clients, but my best guess is that you still have some table issues. There are a lot of required SQL updates needed from the older revision you were probably running. You may have 1 or more fields set to incompatible default values that cause them to fail when loading or something like that. You might also need to make sure that when you compile, you are compiling all of the most recent files in the common/patches/ folder. If you are compiling older version of the patch files, who know what odd issues it would cause.

Since there are other crash issues related to the SoD client (and probably other new clients), I would think your problem is with the patch files you are compiling. It could probably also be an issue with your shared mem file compile, but I really have no clue how you have stuff setup.

There is also a chance you could be running into some 64bit issue, cause I don't know much about what to expect crash-wise from that. As far as I know, the source should work with 64 bit, but I haven't tested it myself to confirm.

And yeah, both of those crashes were me. One was when I first created the char using SoD and the other is when I died on the char after I deleted all items on him.

Still have no clue what is causing this.. What more info do people need in order to fix this issue ?? More Core Drops ?? I can put the schema of my tables in here, though i have double checked they are the same as PEQ's rev 1752 exactly...

I need to get this fixed !

After looking through all the SQL updates after trev said that might be whatsup I ran into some that were updating this table : "tblWorldServerRegistration"

Well, I don't have that table what is it.. Is it important , would it be causing this? (maybe not)

I couldn't find any of the updates really pertaining to the items or inventory table other than 1542_items_table_cleanup


Here is my Schema for Items and Inventory , maybe some one can see something I am not.

-=ITEMS=-

-=INVENTORY=-

Any help would be greatly appreciated

Oh also :

So the patch files are loading for sure.. I just have to figure out the exact cause of whats doing this in order to fix it.

The one thing I do see from most of these depending on what client they use of course is lines similar to this listed under frames 3 and 4..


I see no sign of SerializedItem anywhere in Inventory or Items, i do find a "serialized" in items but those are all set to either NULL or "0000-00-00 00:00:00" also i see "serialization" but those are all set to NULL as they should be.

Mort

Looks like your crashing issue is due to you running 64bit and also the combination of libs you are running. You had this exact same issue in 2009:

http://www.eqemulator.net/forums/arc...p/t-28455.html

Nice.. I do remember that, yes ok so should I be removing the -O on all the makefiles or just World.. Or should I just use the makefiles Gaeorn had put in there in it's entirety .. They don't exactly look the same.. Guess I can try just taking off the -O for now and see how it goes.

Well, I started this thread, and Now , I hereby CLOSE this thread.

Thank you Trevius , i don't know how you managed to remember that and everything.. (Gaeorn actually told me this like a dozen times, sorry Gaeorn)

It did work , I took the -O , off world and zone makefiles, and now SOD / SOF people can connect like they did normally before...

My Question to the community I guess at this time is why would that one little -O make that much difference?? It's true my Linux build is 64 bit but still makes me wonder why that little letter would cause all that trouble.. What is Optimization and what does it do for the binary's , will I be missing out on any performance from this or ?

Morty

I know this is an old thread but I'm having the same issue. Where exactly do I remove the -O's from?

Thanks,
Mike