How odd. This happens all the time or occasionally? Can you do nodels bc081 ipmi.bmc
Then, do nodels ipmi.bmc=<value from above> That means the BMC rejected our attempt to connect as it had already reached the maximum user count. From: Stuart Barkley <[email protected]> To: xCAT Users Mailing list <[email protected]>, Date: 07/26/2013 06:09 PM Subject: [xcat-user] rvitals error messages [was: xCAT 2.8.2 Released] On Fri, 26 Jul 2013 at 07:53 -0000, Lissa Valletta wrote: > We have just released xCAT 2.8.2 . Review the notes for new function and > fixes. > https://sourceforge.net/apps/mediawiki/xcat/index.php?title=XCAT_2.8.2_Release_Notes I'm still seeing issues with the ipmi traffic between xCAT and the nodes: # rvitals all all > /tmp/xx.tmp bc081: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc049: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc081: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc049: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc021: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc081: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc049: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc021: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc081: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc049: Error: Insufficient resources to create new session (wait for existing sessions to timeout) bc021: Error: Insufficient resources to create new session (wait for existing sessions to timeout) # The errors seem to happen with rvitals, rinv and reventlog commands. This looks similar to the RCMP errors we were seeing with 2.7.X. (The errors messages are different, but the effect looks about the same). This cluster was updated to 2.8.1 two days ago and had this problem and was just updated to 2.8.2 today. This is a cluster with ~100 nodes total with a mix of x3650 and x3850 nodes. The problem also happens on our dx360 M2 compute cluster. Stuart -- I've never been lost; I was once bewildered for three days, but never lost! -- Daniel Boone ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
