Differences

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

--- huibintemaspamfaq [2019/06/18 06:23] – huibintema
+++ huibintemaspamfaq [2019/09/10 06:36] – [SPAM crashes in screen session] huibintema
@@ Line 48: / Line 48: @@
 Q: Why is libncurses.so.6 reported to be missing during the AIPS install?
-A: The AIPS install may fail because the libncurses.so.6 library cannot be found. This library is available in the lib subdirectory of the spam install directory. The library can be copied to one of the standard locations (e.g., /usr/lib), or the LD_LIBRARY_PATH can be modified to include the spam/lib directory before running AIPS install again. The latter can be done in bash:
+A: The AIPS install may fail because the libncurses.so.6 library cannot be found. This library is available in the lib subdirectory of the spam install directory. The library can be copied to one of the standard locations (e.g., /usr/lib) or the LD_LIBRARY_PATH environment variable can be modified to include the spam/lib directory before running AIPS install again. The latter can be done in bash:
 <code bash>
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${SPAM_PATH}/lib
@@ 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)
 -----