Differences

This shows you the differences between two versions of the page.

--- huibintemaspamfaq [2019/06/18 06:30] – [libncurses.so.6 is missing] huibintema
+++ huibintemaspamfaq [2020/10/05 17:48] – [Problems running SPAM on new Intel CPUs, possibly after Linux update] huibintema
@@ Line 173: / Line 173: @@
 ==== SPAM crashes in screen session ====
-Q: Why does my SPAM pipeline run crash when the screen session in which I run SPAM is interrupted?
+Q: Why does my SPAM pipeline run crash when the screen session in which I run SPAM is interrupted, or when I reconnect?
 A: As the SPAM pipeline can take several hours to days to run, it is useful to execute it in a screen session when working remotely. However, some users found that the SPAM pipeline crashed during a disconnect from the screen session with the error "Fatal IO error 11 (Resource temporarily unavailable) on X server localhost:1.0.", or something similar. This is likely due to the fact that the screen is started in an environment with the X server available that becomes unavailable after the disconnection, causing the crash of SPAM. A solution might be to use a "fake" X server, such as xvfb, in the screen session. Another solution is to run SPAM remotely via a VNC session. Note that checking the progress of the pipeline can also be done by checking the spam*.log in the datfil subdirectory.
-(Kindly contributed by Andrea Botteon)
+Another problem with using screen was found when reconnecting, leading to an "error: (4, 'Interrupted system call')". A fix has been added to ParselTongue which captures this exception without crashing the SPAM pipeline.
+(Kind contributions from Andrea Botteon and Błażej Nikiel-Wroczyński)
 -----
@@ Line 206: / Line 209: @@
 -----
-Feedback: [[huib.intema@curtin.edu.au|Click here]]
+Feedback: [[intema@strw.leidenuniv.nl|Click here]]