[Opensim-users] Crash on collision

[Chris Hart]

If I have physical prims causing trouble on a region then here's what I
normally do: 

Log in to the region and turn on beacons in your client (View - Beacons) and
check the box to view Physical Objects. Even with physical_prim set to false
you will still see green lines highlighting objects with the physical flag
set to true (though thankfully they should not be moving or causing trouble
while you have physical prims disabled). 

If you see any of those highlighted objects embedded in the ground, or
something set to be physical that shouldn't be, then you may have found the
cause of your crashes - you could then right-click and edit the object, then
in the uncheck the physical checkbox and change it to be a regular prim,
reboot the region with physics re-enabled and see if your crashes return or
not. If it crashes, repeat the process 'til you find the nasty that causes
the trouble :)

Hope this helps,

Chris 

-----Original Message-----
From: opensim-users-bounces at lists.berlios.de
[mailto:opensim-users-bounces at lists.berlios.de] On Behalf Of Justin
Clark-Casey
Sent: 06 January 2012 4:35 PM
To: opensim-users at lists.berlios.de
Subject: Re: [Opensim-users] Crash on collision

Ok, so at least it's not completely insane.  If physical objects aren't
important to you then I suggest running with this setting for now until/if
git master physics libraries are updated or some other change is made.

Or you may want to see how many "Active objects" are in the script stats
(active objects are physical objects) and try removing them if they
shouldn't be there.  Unfortunately, you might need to hunt for them.

On 06/01/12 21:18, Klaus-E. Klingner wrote:
> Hallo Justin,
>
> this seems to be working. Without problems.
>
> Regards,
>
> Klaus
>
> On 05.01.2012 00:07, Justin Clark-Casey wrote:
>> What happens if you set physical_prim = false in [Startup] with no 
>> avatars? As this prevents prims temporarily being physical then there 
>> will be no colliding active at all and nothing should crash. If it still
does then something more bizarre is going on.
>>
>> On 04/01/12 23:04, Klaus-E. Klingner wrote:
>>> Done. Without success :( Same result. This time even without an 
>>> avatar online. It crashed shortly after the world started.
>>>
>>> Regards
>>>
>>> Klaus
>>>
>>> Von meinem iPad gesendet
>>>
>>> Am 04.01.2012 um 23:20 schrieb "M.E. Verhagen"<marceled9 at gmail.com>:
>>>
>>>> I also changed the ulimit settings in the limits.conf file in 
>>>> /etc/security/limits.conf
>>>>
>>>> Changing the ulimit with the ulimit -s 212144 does not seem to be
persistent, it gets setted back.
>>>>
>>>> The values I entered are:
>>>>
>>>> * hard stack 524288
>>>> * soft stack 524288
>>>> * soft nofile 2048
>>>> * hard nofile 2048
>>>> * soft memlock 256
>>>> * hard memlock 256
>>>>
>>>> The settings get effective after a reboot.
>>>>
>>>> As a bonus OpenSim uses a thirth less memory !
>>>>
>>>> You can try experimenting with these values, you should be carefull 
>>>> though these settings (just like the sysctl -a) can reduce crashes, 
>>>> increase system speed and reduce memory usage, but false settings can
also also cause system unresponsiveness and system crashes.
>>>>
>>>> _______________________________________________
>>>> Opensim-users mailing list
>>>> Opensim-users at lists.berlios.de
>>>> https://lists.berlios.de/mailman/listinfo/opensim-users
>>> _______________________________________________
>>> Opensim-users mailing list
>>> Opensim-users at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-users
>>>
>>
>>
> _______________________________________________
> Opensim-users mailing list
> Opensim-users at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-users
>


--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
Opensim-users at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-users