[Swift-commit] r5431 - branches/release-0.93/docs/siteguide

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2011-12-17 19:52:26 -0600 (Sat, 17 Dec 2011)
New Revision: 5431

Modified:
   branches/release-0.93/docs/siteguide/beagle
Log:
added troubleshooting section and some points for troubleshooting in beagle section

Modified: branches/release-0.93/docs/siteguide/beagle
===================================================================
--- branches/release-0.93/docs/siteguide/beagle	2011-12-16 21:22:51 UTC (rev 5430)
+++ branches/release-0.93/docs/siteguide/beagle	2011-12-18 01:52:26 UTC (rev 5431)
@@ -149,3 +149,25 @@
 </config>
 -----
 
+Troubleshooting
+~~~~~~~~~~~~~~~
+
+In this section we will discuss some of the common issues and remedies while using Swift on Beagle. The origin of these issues can be Swift or the Beagle's configuration, state and user configuration among other factors. We try to identify maximum known issues and address them here:
+
+* Command not found: Swift is installed on Beagle as a module. If you see the following error message:
+
+-----
+If 'swift' is not a typo you can run the following command to lookup the package that contains the binary:
+    command-not-found swift
+-bash: swift: command not found
+-----
+
+The most likely cause is the module is not loaded. Do the following to load the Swift module:
+
+-----
+$ module load swift
+Swift version swift-0.93RC5 loaded
+-----
+
+* Failed to transfer wrapperlog for job cat-nmobtbkk and/or Job failed with an exit code of 254. Check the <workdirectory> element on the sites.xml file. It is likely that it is set to a path where the compute nodes can not write, e.g. your /home directory. The remedy for this error is to set your workdirectory to the /lustre path where swift could write from compute nodes.
+