What is & how to solve File error: VP1_test.xml.state (Remote I/O error)?

26 views
Skip to first unread message

Pavel Rinkman

unread,
Apr 21, 2022, 1:11:44 AM4/21/22
to beast-users
Hello everyone,

I caught the next exception during my phylogeographical analysis. What could be the reason? & how to evade this in the future?

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

I hope, please, anyone could help me out!

Best wishes,

      ...
      850000000     -3668.6658      5954.3044     -9622.9702 43m15s/Msamples
      851000000     -3765.5214      5933.4457     -9698.9672 43m9s/Msamples
      852000000     -3575.0587      6006.1062     -9581.1650 42m59s/Msamples
      853000000     -3564.4313      6056.8377     -9621.2691 42m49s/Msamples
      854000000     -3526.2056      6090.5743     -9616.7799 42m39s/Msamples
      855000000     -3543.4126      6077.3957     -9620.8083 42m28s/Msamples
      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.<init>(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)

Remco Bouckaert

unread,
Apr 25, 2022, 11:48:20 PM4/25/22
to beast...@googlegroups.com
Hi Pavel,

This may be the result of a full hard disk (or you may have reached your quota if this is on a server). To prevent this, just make sure there is sufficient hard disk space, and also make sure the log files are not logging more than necessary: more than 10.000 samples for an MCMC run is sufficient, and logging more frequently usually does not help but does take up disk space. By setting the logEvery values on the trace and tree log to the chain length divided by 10000, the log files may be kept a reasonable size.

Hope this helps,

Remco

--
You received this message because you are subscribed to the Google Groups "beast-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beast-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beast-users/bc7c1f1b-5641-43ca-bdc1-feee5e9d5ff7n%40googlegroups.com.

Pavel Rinkman

unread,
Apr 26, 2022, 2:22:24 PM4/26/22
to beast-users
Thank you very much!

вторник, 26 апреля 2022 г. в 06:48:20 UTC+3, higg...@gmail.com:
Reply all
Reply to author
Forward
0 new messages