On your node what is in the /tmp/mypostscript file. Is there anything in /var/log/xcat/xcat.log. There should be a /tmp/wget.log also might show you something. Can you run with conserver and see if there are any errors. When you logon to the nodes, is ssh setup so you don't have to supply a password? You are installing from the Management Node correct ( no service nodes). What level of xCAT are your running?
Lissa K. Valletta 2-3/T12 Poughkeepsie, NY 12601 (tie 293) 433-3102 From: Bruce Pennypacker <[email protected]> To: xCAT Users Mailing list <[email protected]> Date: 07/29/2011 02:22 PM Subject: Re: [xcat-user] updateflag.awk:22: fatal: remote host and port information invalid Lissa, Thanks for the pointers. It appears that everything is set up properly. 192.168.3.6 is the IP of the xcatmaster. # lsdef node24 Object name: node24 addkcmdline=console=ttyS0,115200 arch=x86_64 bmc=node24-bmc bmcpassword=xxxx bmcusername=xxxx currchain=boot currstate=boot groups=idataplex initrd=xcat/rhels5.6/x86_64/initrd.img ip=192.168.3.34 kcmdline=nofb utf8 ks=http://192.168.3.6/install/autoinst/node24 ksdevice=bootif noipv6 kernel=xcat/rhels5.6/x86_64/vmlinuz mac=00:02:c9:0f:a0:fc mgt=ipmi netboot=pxe nfsserver=192.168.3.6 os=rhels5.6 postbootscripts=otherpkgs postscripts=syslog,remoteshell,syncfiles,hardeths profile=idataplex provmethod=install status=booting statustime=07-29-2011 13:45:04 tftpserver=192.168.3.6 xcatmaster=192.168.3.6 When the install completes I can log into the node and from there tftp, http, etc. back to 192.168.3.6. There's no firewall in place so nothing is getting blocked (actually there's an iptables rule in place to allow anything from 192.168.3.0/24 on that interface). Any other suggestions? Is there some relatively easy way to trace whats going on to get a better idea of where its failing? Thanks, -Bruce On 7/29/11 1:44 PM, Lissa Valletta wrote: > So a couple of things we have hit in the past and it usually revolves > around hostname resolution. Can the node during install get the the > address defined as it's xcatmaster, the node that is installing it. In > most cases this is the Management node unless you are using service nodes. > That can happened with changes to /etc/hosts or problems > with /etc/resolv.conf. > Run lsdef<nodename> and see if the attributes are correct. If there is > no xcatmaster defined then look to what you have defined in the site table > the master attribute. A /etc/resolv.conf that points to addresses the > node cannot access on the node during install can also cause problems. > > Lissa K. Valletta > 2-3/T12 > Poughkeepsie, NY 12601 > (tie 293) 433-3102 > > ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
