Sim crasht wenn man gegen die Grenzen fliegt

Slow Ibanez
Slow Ibanez
 Member edited March 26 in Technical Support

Hallo zusammen, wir habe mal ein neues Phänomen,

wenn wir gegen unsere Simgrenzen fliegen crasht die Sim.

Wir benutzen zwei normale Sims (keine Var) nebeneinander.

Root Server mit Debian Linux 9.8. Normal läuft die Simulation

mit mysql, ein Umstellen auf sqlite brachte auch keine Änderung, wir haben alles versucht,

Cache geleert, Server mehrmals neugestartet nichts schafft Abhilfe. Vielleicht hat jemand von euch einen Tipp für uns.


Grüße

Slow


Thanked by: Pius Noel

Comments

  • Lena Vanilli
    Lena Vanilli
     Administrator
    Hallo Slow, so auf Anhieb hab ich da keine Erklärung. Gibst du uns noch die Regionsnamen? Dann können die Leutz mal testen.

    LG, Lena

  • Slow Ibanez
    Slow Ibanez
     Member edited March 27
    Vielen Dank für deine Rückmeldung Lena. Es betraf die Regionen Pais Natal und Cupid. Wir hatten
    die Koordinaten rund um diese beiden Regionen für spätere zusätzliche Sims "isoliert". Haben heute morgen weiter probiert, unter anderem haben wir die Isolierung der beiden Regionen aufgehoben, danach war das "Problem" behoben.

    Wenn die Sim abschmiert bekommen wir folgende Fehlermeldung:

    1. APPLICATION EXCEPTION DETECTED: System.UnhandledExceptionEventArgs

      Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
        at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_delegate_end_invoke (object,intptr)
        at (wrapper delegate-end-invoke) <Module>:end_invoke_ScenePresence__this___IAsyncResult (System.IAsyncResult)
        at OpenSim.Region.CoreModules.Framework.EntityTransfer.EntityTransferModule.CrossCompleted (System.IAsyncResult iar) [0x00006] in <9d77697fb5f4444c947e7caf0f67f861>:0
        at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult:Invoke (System.Runtime.Remoting.Messaging.AsyncResult)
        at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
        at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <8f2c484307284b51944a1a13a14c0266>:0
        at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0

      Application is terminating: True




  • Pius Noel
    Pius Noel
     Member edited March 27
    Ich kann das für Ubuntu 18.04.2 LTS bestätigen. Ohne Isolierung bin ich am Simrand schlimmstenfalls hängen geblieben. Nach der Isolierung kam es zu Crash. Getestet habe ich mit den Regionen Piust1 und Piust2. Ich lasse die Regionen mal 2 Tage laufen. Sie werden nach dem Crash nach 2 Minuten automatisch neu gestartet.

    2019-03-27 09:54:11,812 ERROR - OpenSim.Application [APPLICATION]:
    APPLICATION EXCEPTION DETECTED: System.UnhandledExceptionEventArgs

    Exception: System.Collections.Generic.KeyNotFoundException: The given key 'result' was not present in the dictionary.
      at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_delegate_end_invoke(object,intptr)
      at (wrapper delegate-end-invoke) <Module>.end_invoke_ScenePresence__this___IAsyncResult(System.IAsyncResult)
      at OpenSim.Region.CoreModules.Framework.EntityTransfer.EntityTransferModule.CrossCompleted (System.IAsyncResult iar) [0x00006] in <9d77697fb5f4444c947e7caf0f67f861>:0
      at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult.Invoke(System.Runtime.Remoting.Messaging.AsyncResult)
      at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x7f97a8a9ef30 + 0x00005> in <b0fbce3aded24cd69a2794df353ebd0a>:0
      at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <b0fbce3aded24cd69a2794df353ebd0a>:0
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7f97a8a19ad0 + 0x00005> in <b0fbce3aded24cd69a2794df353ebd0a>:0

    Application is terminating: True

  • Lena Vanilli
    Lena Vanilli
     Administrator
    Ja, da verhält sich OS 0.9.1 gänzlich anders als OS 0.8.3. Bislang haben wir die Reservierungen mit einem minimalen Datenset gespeichert. Wie es jetzt ausschaut, brauchen die Reservierungs-Regionen wohl auch mehr Daten. Wir arbeiten daran und geben wieder Bescheid.

    Liebe Grüße
    Lena

  • Han Held
    Han Held
     Member
    I have a region connected from a Ubuntu 18.04 server, using the opensim install I downloaded from metro.

    I've tried flying into the southern border, and the western border; I didn't end up crashing.

    I'm not sure if there's something else to do to reproduce it?

    A few days back I drove a motorcycle I was testing off into the void but didn't crash; I just stood up, reposistioned it and kept riding.

    Take that for whatever it's worth.

    I do get errors when I shut down the region, however...but I think that's a known problem?

  • Pius Noel
    Pius Noel
     Member
    @Han Held : Metropolis has an option to isolate regions, that is a ring of pseudo regions around your region. They look like regions, but are only placeholders. They can be set in the Region Management on the Dashboard. The crashes reported in this thread only happen in case a region is "isolated".

    I can confirm the shutdown errors, but since they only appear in the log (I cant see them in the console window, do you?) I'm not sure they are known.
    Thanked by: Han Held
  • Han Held
    Han Held
     Member
    Pius Noel said:
    @Han Held : Metropolis has an option to isolate regions, that is a ring of pseudo regions around your region. They look like regions, but are only placeholders. They can be set in the Region Management on the Dashboard. The crashes reported in this thread only happen in case a region is "isolated".


    @Pius Noel thank you -I was confused on that point. I thought the problem was happening when they were *not* isolated.

    I can't test this because I don't see an option to isolate my region in the new Region Manager page. I'm not sure if that is because it hasn't been implemented yet, or because it isn't on the english page, or because I'm being an idiot and looking in the wrong place. (the smart money is on the last one ;))

    I can confirm the shutdown errors, but since they only appear in the log (I cant see them in the console window, do you?) I'm not sure they are known.
    I see them on my console window. Here's a demonstration from 9pm SLT:


    I get this message when I run OpenSim in Screen, or when I run it just from the console (not in screen).
    Thanked by: Pius Noel
  • Pius Noel
    Pius Noel
     Member
    Han Held schrieb:
    I get this message when I run OpenSim in Screen, or when I run it just from the console (not in screen).
    Aah, I see.The same here. I run my simulators in tmux (much similar to screen) which closes the window too fast to see the message.

    Btw, I can see the "Isolate" button only for single regions.
  • Lena Vanilli
    Lena Vanilli
     Administrator
    Pius Noel schrieb:

    Btw, I can see the "Isolate" button only for single regions.
    @Pius Noel , that's right! Cause the isolation for Var-Regions under 0.8.3 caused always troubles. We have to test the new 0.9.1 if it's solved. 

    Thanked by: Han Held Pius Noel
Sign In or Register to comment.

Welcome

It looks like you're new here. If you want to get involved, click one of these buttons!

Discussions

© Copyright 2019 - Metropolis Metaversum
All times are GMT