I believe the xnba.kpxe is retrieved via TFTP, while the next two steps should happen by HTTPS. Maybe there is a problem with https?
Check to see if you have a firewall enabled, and also use netstat -ltunp to check that something is actually listening on port 3001. _______________________________________________________________________ Kevin Keane | Systems Architect | University of San Diego ITS | [email protected] Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859 | Text: 760-721-8339 *REMEMBER! **No one from IT at USD will ever ask to confirm or supply your password*. These messages are an attempt to steal your username and password. Please do not reply to, click the links within, or open the attachments of these messages. Delete them! On Thu, May 23, 2019 at 11:49 AM Andrew Loftus <[email protected]> wrote: > Thank you for pointing me to ` journalctl -u xcatd -f`, that shows me > that xcat/xnba.kpxe is requested (and I assume provided to the booting > node). > However, after that, I see no more activity on the xcat master. I would > expect activity recorded on the xcat master at the steps: > xcat.genesis.doxcat: Getting initial certificate --> 172.30.18.6:3001 > xcat.genesis.doxcat: Running getdestiny --> 172.30.18.6:3001 > > Both of those commands above seem to timeout with no apparent response > from the xcat master. The ip address and port specified are correct for the > xcat master. > I have ensured that iptables is open for those ports. > I have ensure that there is a process listening on port 3001. > > What else should I check? > > Can I get more debug info from the genesis kernel? > > Can I get more debug info from the xcat master? > > On Thu, May 23, 2019 at 4:51 AM Song BJ Yang <[email protected]> wrote: > >> Hi, >> >> You can watch the output of `journalctl -u xcatd -f` in another session >> during nodediscovery >> >> there are some similar issues reported before, see >> https://sourceforge.net/p/xcat/mailman/search/?q=Unrecognized+directive+ , >> you can simply go through them for any hint >> >> ------------------------------------------------------------------------------ >> YANG Song (杨嵩) >> IBM China System Technology Laboratory >> Tel: 86-10-82452903 >> Email: [email protected] >> Address: Building 28, ZhongGuanCun Software Park, >> No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC >> >> 北京市海淀区东北旺西路8号中关村软件园28号楼 >> 邮编: 100193 >> >> >> >> ----- Original message ----- >> From: Andrew Loftus <[email protected]> >> To: xCAT Users Mailing list <[email protected]> >> Cc: >> Subject: [EXTERNAL] [xcat-user] Unrecognized directive (dest=) during >> nodediscovery >> Date: Thu, May 23, 2019 6:58 AM >> >> Setting up a new test cluster and getting the following on the compute >> node during nodediscovery: >> >> xcat.genesis.doxcat: Running getdestiny --> 172.30.18.6:3001 >> >> xcat.genesis.doxcat: Received destiny= >> xcat.genesis.doxcat: The destiny=, destiny parameters= >> xcat.genesis.doxcat: Unrecognized directive (dest=) >> xcat.genesis.doxcat: ... Will retry xCAT in 40 seconds >> xcat.genesis.doxcat: ... Will retry xCAT in 30 seconds >> >> There are no "discovery" type messages in /var/log/messages or in >> /var/log/xcat/cluster.log. >> >> Where to look for more troubleshooting information? >> >> >> Version info: >> # lsxcatd -a >> Version 2.14.6 (git commit 7c787c499ebca7a98d6fcdb3577f701ac16d7ab3, >> built Fri Mar 29 03:19:08 EDT 2019) >> This is a Management Node >> dbengine=SQLite >> _______________________________________________ >> xCAT-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xcat-user >> >> >> >> _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user >
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
