Re: [xcat-user] Unrecognized directive (dest=) during nodediscovery

Song BJ Yang Thu, 23 May 2019 19:57:17 -0700

Hi,

You can run `rinstall [CN] shell` to provision the node to genesis shell, and then run `/bin/dodiscovery` manually.

------------------------------------------------------------------------------
YANG Song (杨嵩)
IBM China System Technology Laboratory
Tel: 86-10-82452903
Email: yang...@cn.ibm.com
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 <alof...@illinois.edu>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Cc:
Subject: [EXTERNAL] Re: [xcat-user] Unrecognized directive (dest=) during nodediscovery
Date: Fri, May 24, 2019 4:10 AM

I copied the XML request from the getdestiny bash script and built the node by hand (from ISO) and sent this request to the master node.
On the master node, in /var/log/xcat/cluster.log, I see:

DEBUG xcatd: connection from testvm30
DEBUG xcatd: open new process : xcatd SSL: getdestiny for testvm30
DEBUG xcatd: dispatch request 'getdestiny ' to plugin 'destiny'
DEBUG xcatd: handle request 'getdestiny' by plugin 'destiny''s process_request
DEBUG destiny->process_request: starting getdestiny...
DEBUG destiny->process_request: getdestiny...
INFO xcat.updatestatus - testvm30: changing status=shell
DEBUG destiny->process_request: processing is finished for getdestiny
DEBUG xcatd: close connection with testvm30

For me, this confirms networking and firewalls are okay.

It also looks like discovery is okay on the master node.

It seems to me that something is not working in the genesis kernel.

How can I customize the "doxcat" script (or customize the genesis kernel) so I can force it to drop to a shell and then troubleshoot from within the live genesis kernel?

On Thu, May 23, 2019 at 1:50 PM Loftus, Andrew J <alof...@illinois.edu> 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 <yang...@cn.ibm.com> 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: yang...@cn.ibm.com
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 <alof...@illinois.edu>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
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
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Re: [xcat-user] Unrecognized directive (dest=) during nodediscovery

Reply via email to