[Opensim-dev] Varregions have appeared on my grid - and new errors?

[Ai Austin]

From: Mister Blue <misterblue at misterblue.com>
>At the top of this thread, you had a problem with an overlapping varregion
>and a mention of a BulletSim linkset rebuild warning. The latter is just a
>warning and sometimes happens when regions start up and the physics engine
>has to wait for assets (meshes or sculpties) to be fetched.
>
>Is the error about region registration failing because of varregion overlap
>still happening? Depending on how long ago you upgraded from, it used to be
>that varregion overlapping was not checked for thus causing problems
>(multiple regions trying to use the same place cause many unexplicable
>errors). So, it could be there was an overlap from long ago that is now
>reporting and error after the upgrade. The fix is to manually delete the
>offending region from the server database.


Thanks for your inputs on this Mister Blue and JustinCC...

The update when this first appeared was just from r/25466 to 
r/25566... after all the OSCC14 version ghost enhancements went in, 
hence my question as to whether it might relate or just be a 
coincidence. This was just one day of 0.8.1 dev master updates. So 
its not a big update from a long time ago at all.

I a beginning to think this was just a nasty blip.. perhaps related 
to an NPC being generated and immediately sat down on a complex mesh 
multi-part vehicle that was not "ready" and that crashes the region 
OpenSim.exe instance.  After that I could not start up.  I can now 
start up that region with ODE physics but not when BulletSim is 
enabled.  Disabling NPCs and map generation has no effect.

I have recovered by making a NEW region with a new UUID and loading 
the old OAR from a backup onto that.. which works fine with Bulletsim 
and all. I will just ditch the faulty region.  I assume there is no 
quick way to delete all the contents on that region from the MySQL 
data base to keep it lean?

The message about overlapping var region may just have been an odd 
message phrasing.. as I have never had varregions.. but I did find a 
region MySQL data base entry for the faulty region even after it was 
shut down... perhaps due to the crash on its load.. So I removed 
that.  I am not seeing the overlapping var region messages, so as you 
say it was related to a stuck data base entry.  But just for a single 
normal region, not a var region. maybe the message ought not to 
mention var regions if its a simple 1-1 overlap of a normal 256x256 region?