On Mon, 2018-07-02 at 08:47 +, Song BJ Yang wrote:
> hi Daniel,
Hi!
>
> which discovery method are you using? mtms-based or switch-based? The
> invalid ipmi commands in dodiscovery will break the mtms-based discovery and
> the task like `bmcsetup` defined in the chain attribute.
I was trying
Hi Kevin,
Yeah, I know what you mean when you say very, very difficult. There is some kind
of support for emulating IPMI. There are some -device and -chardev magic that I
never understood. For basic testing it passes, but I couldn't connect to node
with ipmi-tool.
Having physical machines is the
Well, I went through and restored all updated files in /install/postscripts
back to previous version, and now
my node boots again. Something in one of the scripts probably depends on
something in the newer binaries
that were not updated. Thanks for the debugging tips.
— ddj
> On Jul 2, 2
.
.
.
Running command on mgt5.oscar.ccv.brown.edu: chmod -R a+r /install/postscripts
2>&1
mgt5.oscar.ccv.brown.edu: Internal call command: xdsh node552 --nodestatus -s
-v -e /install/postscripts/xcatdsklspost 1 -m 172.20.0.6 'setupntp' --tftp
/tftpboot --installdir /install --nfsv4 no -c -V
R
After the chdef command and reboot the message in /var/log/xcat/xcat.log is
exactly the same
[root@node552 xcat]# cat xcat.log
Mon Jul 2 15:18:10 EDT 2018 [info]: xcat.xcatdsklspost: trying to download
postscripts...
Mon Jul 2 15:18:26 EDT 2018 [err]: xcat.xcatdsklspost: failed to download the
updatenode will issue command from management node and process command
(postscripts) on the compute node after node is booted.
postscripts on the compute node /xcatpost/ will be downloaded again from
MN:/install/postscripts (not sure if you want to do this)
]# updatenode mid21tor24cn01 setupntp -
I have never used updatenode. Just reboot. Would that help debug?
> On Jul 2, 2018, at 2:16 PM, Casandra H Qiu wrote:
>
> on the site table, turn on the "xcatdebugmode"
>
> chdef -t site xcatdebugmode=1
>
> Did u try to run "updatenode" again for the current compute node? add verbose
> "-V"
on the site table, turn on the "xcatdebugmode"
chdef -t site xcatdebugmode=1
Did u try to run "updatenode" again for the current compute node? add
verbose "-V" to the option, should able to get more logs.
Thanks,
Casandra Qiu
..
Thanks, it’s good to know I’ve got a hundred or so copies with changes back to
9/2017 on our compute nodes.
However even after restoring postscripts/hostkeys, postscripts/_xcat and
postscripts/_ssh and checking the
files we created are still there, the diskless boot still fails:
Mon Jul 2 10:27:
hi David Johnson,
In the scenario you described, I think xCAT installation will affect the stuff under `/install/postscripts`
1) files with the same name with the files under `/install/postscripts` shipped by xCAT will be overwritten
2) the credentials under "/install/postscripts/hostkeys", "/
Hi Yuan,
that’s what I thought should be happening – but it isn’t working properly.
When I log into the node and compare /etc/resolv.conf and
/.default/etc/resolv.conf they are not the same.
I wondering if there’s a configuration setting that I’ve got wrong.
Best,
Jeff
From: Yuan Y Bai
hi Daniel,
which discovery method are you using? mtms-based or switch-based? The invalid ipmi commands in dodiscovery will break the mtms-based discovery and the task like `bmcsetup` defined in the chain attribute.
For switch-based discovery, the mandatory information is the mac address, which
12 matches
Mail list logo
