Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.xml.state not found #1146

Open
kesiaeds opened this issue Apr 2, 2024 · 5 comments
Open

.xml.state not found #1146

kesiaeds opened this issue Apr 2, 2024 · 5 comments

Comments

@kesiaeds
Copy link

kesiaeds commented Apr 2, 2024

Dear all I am trying to run BEAST2 2.6 version and I keep getting this err message. The full log file and xml file is attached. I would really apppreciate if you could help me figure out what is the problem.
slurm-4281671.txt
cluster9.old.fixed.w.xml.zip
cluster9.old.w.xml.zip

Restoring from file
File error: /oak/stanford/scg/lab_jandr/Kesia/TB/tb_genomics/study/cluster/BEAST/cluster9.old.fixed.w.xml.state (No such file or directory)
java.lang.RuntimeException: An error was encounted. Terminating BEAST
at beast.app.util.ErrorLogHandler.publish(Unknown Source)
at java.util.logging.Logger.log(Logger.java:738)
at java.util.logging.Logger.doLog(Logger.java:765)
at java.util.logging.Logger.log(Logger.java:788)
at java.util.logging.Logger.severe(Logger.java:1464)
at beast.app.beastapp.BeastMain.(Unknown Source)
at beast.app.beastapp.BeastMain.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at beast.app.beastapp.BeastLauncher.run(Unknown Source)
at beast.app.beastapp.BeastLauncher.main(Unknown Source)

@zyy-1111
Copy link

have you fixed it?I met the same problem

@rbouckaert
Copy link
Member

This can happen when the state file moved. First thing to do is check whether the file that is missing is somewhere else. If so, start beast with the --statefile option, like so:

beast -statefile /path/to/where/the/state/file/is/beast.xml.state -resume beast.xml

where /path/to/where/the/state/file/is/ the path to where the state file is.

@zyy-1111
Copy link

zyy-1111 commented Jun 20, 2024 via email

@zyy-1111
Copy link

Could u share a xml file that can run successfully?

@rbouckaert
Copy link
Member

Any of the example files that come with BEAST should run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants