Looks like the 'n042' is not a free node. Could you show out the node definition by 'lsdef n042'? If you did not set hostip and bmcip for the node definition. Could you use the parameter [hostiprange=imageprofile] [bmciprange=bmciprange] for nodediscoverstart command?
 
 

Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
 
Manager for HPC SW Dev: xCAT, ESSL, SMI, Test
IBM China Systems Laboratory (CSL)

Tel: 86-10-82453455
Email: [email protected]
 
 
----- Original message -----
From: Nicolas Roosen <[email protected]>
To: <[email protected]>
Cc:
Subject: Re: [xcat-user] 回复: xcat.genesis.doxcat: Unrecognized directive (dest=)
Date: Thu, Jul 6, 2017 4:31 PM
 
On 07/06/2017 03:29 AM, Xiao Peng Wang wrote:
> 1. please be sure that you can see the message like
> 'xcat.discovery.seqdiscovery' in your MN log. This is important to know
> that the sequential discovery process has been triggered.

That's my problem I think, I tried this morning again, and although the
"nodediscoverstart" seems to be running, there are *no* messages into
the logs (debug is set to 2).

I'd like to debug this further but I have no clue where to look at.


nodediscoverstart -V noderange=n042
Sequential Discovery: Started:
     Number of free node names: 0

====================Free Nodes===================
NODE                HOST IP             BMC IP


* /var/log/messages


Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: connection from root@localhost
Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: open new process : xcatd
SSL: nodediscoverstart for root@localhost
Jul  6 10:15:41 adm xcat[16016]: DEBUG xcatd: dispatch request
'nodediscoverstart -V noderange=n042' to plugin 'seqdiscovery'
Jul  6 10:15:41 adm xcat[16016]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'seqdiscovery''s process_request
Jul  6 10:15:41 adm xcat[16015]: xCAT: Allowing nodediscoverstart -V
noderange=n042 for root from localhost
Jul  6 10:15:41 adm xcat[16017]: DEBUG xcatd: dispatch request
'nodediscoverstart -V noderange=n042' to plugin 'profilednodes'
Jul  6 10:15:41 adm xcat[16017]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'profilednodes''s process_request
Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: close connection with
root@localhost


* /var/log/xcat/cluster.log


Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: connection from root@localhost
Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: open new process : xcatd
SSL: nodediscoverstart for root@localhost
Jul  6 10:15:41 adm xcat[16016]: DEBUG xcatd: dispatch request
'nodediscoverstart -V noderange=n042' to plugin 'seqdiscovery'
Jul  6 10:15:41 adm xcat[16016]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'seqdiscovery''s process_request
Jul  6 10:15:41 adm xcat[16015]: xCAT: Allowing nodediscoverstart -V
noderange=n042 for root from localhost
Jul  6 10:15:41 adm xcat[16017]: DEBUG xcatd: dispatch request
'nodediscoverstart -V noderange=n042' to plugin 'profilednodes'
Jul  6 10:15:41 adm xcat[16017]: DEBUG xcatd: handle request
'nodediscoverstart' by plugin 'profilednodes''s process_request
Jul  6 10:15:41 adm xcat[16015]: DEBUG xcatd: close connection with
root@localhost

* /var/log/xcat/subcallingtrace is attached in any case.


Thanks.
Nicolas

> 2. The command 'nodediscoverstart noderange=' only supports a real
> noderange instea of IP ranges. so you need to make this command work as
> a charm before the discovery start.
>
> Best Regards
> ----------------------------------------------------------------------
> Wang Xiaopeng (王晓朋)
> Manager for HPC SW Dev: xCAT, ESSL, SMI, Test
> IBM China Systems Laboratory (CSL)
>
> Tel: 86-10-82453455
> Email: [email protected]
>
>     ----- Original message -----
>     From: Nicolas Roosen <[email protected]>
>     To: <[email protected]>
>     Cc:
>     Subject: Re: [xcat-user] 回复: xcat.genesis.doxcat: Unrecognized
>     directive (dest=)
>     Date: Wed, Jul 5, 2017 11:34 PM
>     Hi,
>
>     On 07/05/2017 04:42 PM, Xiao Peng Wang wrote:
>      > No, bmcdiscovery is not mandatory for sequential discovery.
>      > The correct procedure should be:
>      > 1. start sequential discovery first: nodediscoverstart
>      > 2. boot the node, then you could see the following messages
>      > xcat.discovery.seqdiscovery
>      > But in your case that there was no any discovery messages after
>     starting
>      > 'nodediscoverstart', so you need check the status of the your nodes.
>      >
>
>     Yes, so I tried the nodediscoverstart with an IP range instead of just
>     the single node hostname:
>
>     # nodediscoverstart noderange=172.30.241.2-200 -V
>     Sequential Discovery: Started:
>           Number of free node names: 1
>
>     ====================Free Nodes===================
>     NODE                HOST IP             BMC IP
>     172.30.241.2-200     --no free--         --no free--
>
>
>     If I understand correctly, there are no free nodes available for
>     discover, which might be my problem?
>
>     On the node side console, the only logs I have are the bellow:
>
>     Jul  5 17:22:51 172.30.241.69 (none)  xcat.genesis.doxcat: Getting
>     initial certificate --> 172.30.240.1:3001
>     Jul  5 17:23:11 172.30.241.69 (none)  xcat.genesis.doxcat: Running
>     getdestiny --> 172.30.240.1:3001
>     Jul  5 17:23:31 172.30.241.69 (none)  xcat.genesis.doxcat: Received
>     destiny=
>     Jul  5 17:23:31 172.30.241.69 (none)  xcat.genesis.doxcat: The destiny=,
>     destiny parameters=
>     Jul  5 17:23:31 172.30.241.69 (none)  xcat.genesis.doxcat: Unrecognized
>     directive (dest=)
>     Jul  5 17:23:37 172.30.241.69 (none)  xcat.genesis.doxcat: ... Will
>     retry xCAT in 210 seconds
>     Jul  5 17:23:47 172.30.241.69 (none)  xcat.genesis.doxcat: ... Will
>     retry xCAT in 200 seconds
>     Jul  5 17:23:57 172.30.241.69 (none)  xcat.genesis.doxcat: ... Will
>     retry xCAT in 190 seconds
>     Jul  5 17:24:07 172.30.241.69 (none)  xcat.genesis.doxcat: ... Will
>     retry xCAT in 180 seconds
>
>
>
>      > Best Regards
>      >
>     ----------------------------------------------------------------------
>      > Wang Xiaopeng (王晓朋)
>      > Manager for HPC SW Dev: xCAT, ESSL, SMI, Test
>      > IBM China Systems Laboratory (CSL)
>      >
>      > Tel: 86-10-82453455
>      > Email: [email protected]
>      >
>      >     ----- Original message -----
>      >     From: Nicolas Roosen <[email protected]>
>      >     To: <[email protected]>
>      >     Cc:
>      >     Subject: Re: [xcat-user] 回复: xcat.genesis.doxcat: Unrecognized
>      >     directive (dest=)
>      >     Date: Wed, Jul 5, 2017 3:53 PM
>      >     Hi,
>      >
>      >     here are some logs.
>      >
>      >     So first we removed an unwanted server from the discovery
>     process:
>      >
>
>     [...]
>
>      >
>      >
>      >     I might miss something, but can't find out what.
>      >
>      >     Is the "bmcdiscover" absolutely mandatory in a sequential
>     discovery
>      >     process?
>      >
>      >
>      >     Thanks.
>      >     Nicolas
>      >
>      >     On 07/05/2017 03:23 AM, Xiao Peng Wang wrote:
>      >      > Please show out the logs in MN during the discovery happens.
>      >      >
>      >      > Using IBM Verse, send from my iPhone.
>      >      >
>      >      >
>      >    
>     ------------------------------------------------------------------------
>      >      > 在 2017年7月5日,上午12:37:37,[email protected] 写道:
>      >      >
>      >      > From: [email protected]
>      >      > To: [email protected]
>      >      > Cc:
>      >      > Date: 2017年7月5日 上午12:37:37
>      >      > Subject: [xcat-user] xcat.genesis.doxcat: Unrecognized
>     directive
>      >     (dest=)
>      >      >
>      >      > Hello,
>      >
>      >     [...]
>      >
>      >     --
>      >     Nicolas
>      >
>
>     --
>     Nicolas
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     _______________________________________________
>     xCAT-user mailing list
>     [email protected]
>     https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> xCAT-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>

--
Nicolas Roosen
HPC Support System Engineer
Mob.: +33 777 161 256
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to