<p>You can restart this at the place you left 'cause is Beast2.</p>
<pre><code>  860000000     -3470.6562      6160.7143     -9631.3706 41m35s/Msamples
</code></pre>
<p>However, this is almost 1 billion replications and should be sufficient for convergence. The fact it ends on a round number might infer a algorithm limit is in place. If the Beast2 was restarted from this point and it abruptly ended this would be a very likely reason.</p>
<p>The alternative is an error external to the algorithm such as a RAM error - it has been running a long time.</p>
<p>Whatever the reason I would simply perform ESS statistics and convergence diagnostics on what you have now. There's no real reason to continue if it has converged for 10e6 replications maximum and this is much, much bigger than that.</p>
<hr />
<p>The terminated processes have not spoiled the work again you can simply input the terminated chains into the restart for Beast2. This is because Beast2 uses <code>checkpoints</code>. Brief information on how to resume from the last checkpoint is highlighted here <a href="https://www.beast2.org/2014/04/07/checkpointing-tricks.html" rel="nofollow noreferrer">https://www.beast2.org/2014/04/07/checkpointing-tricks.html</a>. Convergence checks are important.</p>
<p>The situation is only is only catastrophic for Beast1 where you would have needed to start from the beginning.</p>

CC BY-SA 4.0
2022-04-21T09:42:13.677Z
Unfortunately, big number of parameters demands big number of iterations. I have several thousands of leaves, some sequences are the same but with different dates & locations. Moreover, continuous phylogeography with complex region shapes is really a hard task.
Vovin
CC BY-SA 4.0
2022-04-20T22:39:58.977Z
2022-04-21T13:47:05.407Z
2022-04-21T13:47:05.407Z
M__
<p>I caught the next exception during my phylogeographical analysis in <strong>BEAST 2</strong> with <em>GEO_SPHERE</em>. What could be the reason? &amp; how to evade this in the future?</p>
<pre><code>      ...
      856000000     -3662.2647      5969.5577     -9631.8225 42m16s/Msamples
      857000000     -3522.3540      6105.9849     -9628.3389 42m5s/Msamples
      858000000     -3621.7922      6022.9359     -9644.7282 41m54s/Msamples
      859000000     -3463.1050      6107.9766     -9571.0817 41m43s/Msamples
      860000000     -3470.6562      6160.7143     -9631.3706 41m35s/Msamples
File error: VP1_test.xml.state (Remote I/O error)
java.lang.RuntimeException: An error was encounted. Terminating BEAST
        at beast.app.util.ErrorLogHandler.publish(Unknown Source)
        at java.logging/java.util.logging.Logger.log(Logger.java:979)
        at java.logging/java.util.logging.Logger.doLog(Logger.java:1006)
        at java.logging/java.util.logging.Logger.log(Logger.java:1029)
        at java.logging/java.util.logging.Logger.severe(Logger.java:1776)
        at beast.app.beastapp.BeastMain.&lt;init&gt;(Unknown Source)
        at beast.app.beastapp.BeastMain.main(Unknown Source)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at beast.app.beastapp.BeastLauncher.run(Unknown Source)
        at beast.app.beastapp.BeastLauncher.main(Unknown Source)
</code></pre>
<p>Unfortunately, googling this error with <strong>&quot;BEAST&quot;</strong> gave me nothing. If without it, there are a lot of irrelevant problems.</p>
<hr />
<p><strong>Update</strong></p>
<p>I have just found out that this error happened simultaneously onto all my nodes (different processors, RAM, &amp; common hards &amp; SSDs). All logs of BEAST 2 analyses have it. What is stranger, some of the analyses pressed on after this &amp; someones were broken. To the present I got more interested not in the broken ones but could this exception spoil those which continued their work?</p>

<phylogenetics><phylogeny><beast>
What is & how to solve File error: my.xml.state (Remote I/O error)?
# What is & how to solve File error: my.xml.state (Remote I/O error)?

(Asked by: username_0 on 2022-04-20)

I caught the next exception during my phylogeographical analysis in BEAST 2 with GEO_SPHERE. What could be the reason? & how to evade this in the future?
      ...
      856000000     -3662.2647      5969.5577     -9631.8225 42m16s/Msamples
      857000000     -3522.3540      6105.9849     -9628.3389 42m5s/Msamples
      858000000     -3621.7922      6022.9359     -9644.7282 41m54s/Msamples
      859000000     -3463.1050      6107.9766     -9571.0817 41m43s/Msamples
      860000000     -3470.6562      6160.7143     -9631.3706 41m35s/Msamples
File error: VP1_test.xml.state (Remote I/O error)
java.lang.RuntimeException: An error was encounted. Terminating BEAST
        at beast.app.util.ErrorLogHandler.publish(Unknown Source)
        at java.logging/java.util.logging.Logger.log(Logger.java:979)
        at java.logging/java.util.logging.Logger.doLog(Logger.java:1006)
        at java.logging/java.util.logging.Logger.log(Logger.java:1029)
        at java.logging/java.util.logging.Logger.severe(Logger.java:1776)
        at beast.app.beastapp.BeastMain.(Unknown Source)
        at beast.app.beastapp.BeastMain.main(Unknown Source)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at beast.app.beastapp.BeastLauncher.run(Unknown Source)
        at beast.app.beastapp.BeastLauncher.main(Unknown Source)

Unfortunately, googling this error with "BEAST" gave me nothing. If without it, there are a lot of irrelevant problems.

Update
I have just found out that this error happened simultaneously onto all my nodes (different processors, RAM, & common hards & SSDs). All logs of BEAST 2 analyses have it. What is stranger, some of the analyses pressed on after this & someones were broken. To the present I got more interested not in the broken ones but could this exception spoil those which continued their work?

**Tags:** phylogenetics, phylogeny, beast

---

## 1 answers

### Answer by username_1 on 2022-04-20. Score: 2 | Accepted answer

You can restart this at the place you left 'cause is Beast2.
  860000000     -3470.6562      6160.7143     -9631.3706 41m35s/Msamples

However, this is almost 1 billion replications and should be sufficient for convergence. The fact it ends on a round number might infer a algorithm limit is in place. If the Beast2 was restarted from this point and it abruptly ended this would be a very likely reason.
The alternative is an error external to the algorithm such as a RAM error - it has been running a long time.
Whatever the reason I would simply perform ESS statistics and convergence diagnostics on what you have now. There's no real reason to continue if it has converged for 10e6 replications maximum and this is much, much bigger than that.

The terminated processes have not spoiled the work again you can simply input the terminated chains into the restart for Beast2. This is because Beast2 uses checkpoints. Brief information on how to resume from the last checkpoint is highlighted here https://www.beast2.org/2014/04/07/checkpointing-tricks.html. Convergence checks are important.
The situation is only is only catastrophic for Beast1 where you would have needed to start from the beginning.

> **Comments:**
> **username_0**: Unfortunately, big number of parameters demands big number of iterations. I have several thousands of leaves, some sequences are the same but with different dates & locations. Moreover, continuous phylogeography with complex region shapes is really a hard task.  

---

