WORLD_CLIENT_ERR and constantly rebooting zones

[Randymarsh9]

I have been having two problems since bringing my server up, and I still have not found a solution to either of them. Occasionally, when someone zones or logs in, I get a huge list of messages in world.exe saying WORLD_CLIENT_ERR followed by a long string of random characters. Also, my zones crash a lot which is possibly related to the former problem, but sometimes, they will restart and shut themselves off over and over again. For instance, one dynamic zone rebooted itself 3000 times even though nobody was in it. I was just wondering if anyone has solutions to these generic problems or any tips for dealing with them.

[lerxst2112]

Look in the logs. They are often filled with tons of great information like the last thing that was logged before the crash.

Another solution is to build with debugging information and attach the debugger to a zone that crashes often, then you will have a call stack and can tell the exact line the crash happened on as well as what led up to it.

[sorvani]

Rebuild again with the current source. Akkadius's changes ensure that everything that you need is already there.

Zone crashing all the time does not happen with a clean SVN build and the correct versions of Perl and MySQL.

In regards to the world errors, those are normal. Basically there is an opcode being sent by the client that world is not handling. It is not required for the client to successfully connect, but it would be nice if someone who knows opcode stuff would take the time to add it to world so that it does not spew out in the the error handler to the console like that.

[Randymarsh9]

I actually have the most updated svn and database with Perl 5.12 . The zone crashes themselves are annoying, but it's worse when they reboot over and over.