From 63b2017e6bf4d151a43036e4f4d8fa93223a3e62 Mon Sep 17 00:00:00 2001 From: Moe Jette <jette1@llnl.gov> Date: Fri, 19 Dec 2008 16:37:26 +0000 Subject: [PATCH] Describe Beat's SUSE problem with limits. --- doc/html/faq.shtml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/html/faq.shtml b/doc/html/faq.shtml index e179faf723e..e4e3da23e9d 100644 --- a/doc/html/faq.shtml +++ b/doc/html/faq.shtml @@ -96,6 +96,9 @@ information between major SLURM updates?</li> execute on DOWN nodes?</li> <li><a href="#batch_lost">What is the meaning of the error "Batch JobId=# missing from master node, killing it"?</a></li> +<li><a href="#accept_again">What does the messsage +"srun: error: Unable to accept connection: Resources termporarily unavailable" +indicate?</a></li> </ol> @@ -1096,8 +1099,15 @@ failure that can not be recovered from. The equivalent message in earlier releases of slurm is "Master node lost JobId=#, killing it". +<p><a name="accept_again"><b>33. What does the messsage +"srun: error: Unable to accept connection: Resources termporarily unavailable" +indicate?</b><br> +This has been reported on some larger clusters running Suse Linux when +a user's resource limits are reached. You may need to increase limits +for locked memory and stack size to resolve this problem. + <p class="footer"><a href="#top">top</a></p> -<p style="text-align:center;">Last modified 26 November 2008</p> +<p style="text-align:center;">Last modified 19 December 2008</p> <!--#include virtual="footer.txt"--> -- GitLab