Hello Jamie, What you described sounds exactly like what I am seeing on two fresh new and different environments (even different hardware) here. Looks to me the xCATd server never answers with a "ready" to the updateflag.awk call, causing the updating AWK to loop forever.
A colleague found a workaround from this same mailing list: he altered the postscripts calling updateflag.awk, commenting the call to it and inserting instead a `ssh $MASTER "nodeset $NODE boot"` to prevent the node from installing forever. He needed also to fix ssh keys for root in the installing node so that passwordless access to $MASTER is available. To recap my previous posts: mine is a diskfull installation and I see no errors being logged anywhere on the node I am installing. Still digging this out as I am concerned about yet unseen problems that might be haunting me in the future if I don't understand what's going on :-) Ciao, Dario ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
