Crash with error code 0177

[Grizzly]

Howdy folks,

Core/Setup info isn't atm relevant to this post, but when it becomes relevant I will add it.

I do have one question though as I am not as experienced in debugging/tracing as I would like to be.

Could anyone enlighten me as to why I am getting this error on a crash?

Program exited with code 0177.

CRASH ON Fri Jun 11 00:27:28 EDT 2010
The program being debugged is not being run.

BACKTRACE


BACKTRACE FULL


THREADS

I think it has to do with bad directory setup. Any light is much appreciated - thanks!

Also - relevant in the console output:

2010-06-18  ERROR:World Thread hangs, kicking out server!
2010-06-18  ERROR:InstanceMap::SetResetSchedule: cannot turn schedule on, no save available for instance 32 of 36
2010-06-18  ERROR:Creature guid overflow!! Can't continue, shutting down server. 

[VladimirMangos]

2010-06-18 ERROR:Creature guid overflow!! Can't continue, shutting down server.

You use in DB too big indexes for creature_template data and created problem for self. Just one from "shot to own foot" cases.

[Grizzly]

You use in DB too big indexes for creature_template data and created problem for self. Just one from "shot to own foot" cases.

(If russian is your native language you can just post in that - I can read it , спасибо)

So what you're saying is that:

In my `mangos`.`creature_template`, a field is out of the Int32(unsigned) range?

In my `mangos`.`creature` table the maximum `GUID` entry is '16775623'

[VladimirMangos]

I write wrong, ofc, i meaning `creature` guids....

This described many times why use big guids numbers is wrong...

Main point: any in game summoned/created at instance loading creatures use incremental guids starting from next after last used in `creature` table.

So if you have higher used guid in table then you make less amount guids available for dynamic creating and then make less time in server work until this guids overflow

and server will shutdown.

[Grizzly]

I write wrong, ofc, i meaning `creature` guids....

This described many times why use big guids numbers is wrong...

Main point: any in game summoned/created at instance loading creatures use incremental guids starting from next after last used in `creature` table.

So if you have higher used guid in table then you make less amount guids available for dynamic creating and then make less time in server work until this guids overflow

and server will shutdown.

Our GUID table starts at 0, so what this means is that someone bumped it up from say 10,000,000 to 11,000,000 at some point (after checking the db this is true)

Correct?

So with this in mind, I need to do the following:

Run a surgery script on my entire mangos database (all tables included) that does this:

Make multidimensional array (2) template [OLDGUID, NEWGUID]

For `mangos`.`creature`

1) set $new_guid = 0

2) get $old_guid, add to array as well

3) set $old_guid to $new_guid+1, add to array as well

THEN

For all other tables in `mangos`

1) where $guid(old guid) == array.OLDGUID

2) set $guid = array.NEWGUID

And make sure it runs on all fields with creature guid's do they will link properly with the new ID's

Gonna be some nasty surgery, ahhhhh working with other peoples work is so fun!

[Grizzly]

Just posting the results of this.

I had to realign my database to new ID's, had to work through about 7 tables. Everything is up and running fine. спасибо vladmir!