Hi Chris,
Hmm, according to the following code in nodediscover.pm, you will not see "$node has been discoveryed" if you see "Failed to notify..." message.
#now, notify the node to continue life
my $sock = new IO::Socket::INET (
PeerAddr => $clientip,
PeerPort => '3001',
Timeout => '1',
Proto => 'tcp'
);
unless ($sock) { syslog("local4|err","Failed to notify $clientip that it's actually $node."); return; } #Give up if the node won't hear of it.
print $sock $restartstring;
close($sock);
# sleep 2 seconds for genesis to complete the disocvery process
sleep (2);
#Update the discoverydata table to indicate the successful discovery
xCAT::DiscoveryUtils->update_discovery_data($request);
syslog("local4|info","$node has been discovered");
Can you show the discoverydata table? (tabdump discoverydata). Is the mac defined for the node after the discovery?
Thanks,
Ling
To: xCAT Users Mailing list <[email protected]>
From: Christopher Samuel <[email protected]>
Date: 08/19/2015 07:32PM
Subject: [xcat-user] "Failed to notify" during xCAT discovery of any node
From: Christopher Samuel <[email protected]>
Date: 08/19/2015 07:32PM
Subject: [xcat-user] "Failed to notify" during xCAT discovery of any node
xCAT 2.10 - when discovering any node on our system we always
see the equivalent of:
Aug 13 23:07:03 snowy-m xcat[23013]: xcatd: Processing discovery request from 10.14.3.3
Aug 13 23:07:06 snowy-m xcat[23013]: snowy001 has been discovered
Aug 13 23:07:06 snowy-m xcat[23013]: Failed to notify 10.14.3.3 that it's actually snowy001.
[...]
Aug 14 14:18:26 snowy-m xcat[18089]: xcatd: Processing discovery request from 10.14.3.99
Aug 14 14:18:29 snowy-m xcat[18089]: snowy-test has been discovered
Aug 14 14:18:29 snowy-m xcat[18089]: Failed to notify 10.14.3.99 that it's actually snowy-test.
Everything *seems* to work OK despite this so it seems to be
something cosmetic, but I'm just curious in case it's something
that we've missed in our configuration?
All the best,
Chris
--
Christopher Samuel Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
Email: [email protected] Phone: +61 (0)3 903 55545
http://www.vlsci.org.au/ http://twitter.com/vlsci
------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
see the equivalent of:
Aug 13 23:07:03 snowy-m xcat[23013]: xcatd: Processing discovery request from 10.14.3.3
Aug 13 23:07:06 snowy-m xcat[23013]: snowy001 has been discovered
Aug 13 23:07:06 snowy-m xcat[23013]: Failed to notify 10.14.3.3 that it's actually snowy001.
[...]
Aug 14 14:18:26 snowy-m xcat[18089]: xcatd: Processing discovery request from 10.14.3.99
Aug 14 14:18:29 snowy-m xcat[18089]: snowy-test has been discovered
Aug 14 14:18:29 snowy-m xcat[18089]: Failed to notify 10.14.3.99 that it's actually snowy-test.
Everything *seems* to work OK despite this so it seems to be
something cosmetic, but I'm just curious in case it's something
that we've missed in our configuration?
All the best,
Chris
--
Christopher Samuel Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
Email: [email protected] Phone: +61 (0)3 903 55545
http://www.vlsci.org.au/ http://twitter.com/vlsci
------------------------------------------------------------------------------
_______________________________________________
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
