> Then the thing turns to you need make sure the nodeset has been run
correctly on your management node. Did you see the message like this?
> : netboot sles11.2-x86_64-compute
Actually, no, nodeset didn't return anything. I tried "nodeset xcat-serv1
install". The hyphen in the node name isn't pro
On startup, it looks at every database table and column it thinks should
exist at the time. If it isn't there, it adds it.
So in theory with fast enough kill, you could have a half-completed schema
update, and it would still be ok since the next startup would just do the
second half.
If you hav
Whew. Great! I thought I caused that by terminating the schema update early
at first. So, speaking of which, would the schema update have completed
when I launched it the next time? I'm still not clear on that. Would the
xcat daemon just refuse to launch if it hadn't completed the schema update?
T
Suddenly the lsxcatd command is returning 2.8.3 to me now. I'm not sure why
it would take time to update, but it looks fine now:
[root@x3650-head01 init.d]# lsxcatd -a
Version 2.8.3 (built Tue Nov 12 23:16:15 EST 2013)
This is a Management Node
cfgloc=mysql:dbname=xcatdb;host=10.X.X.X|xx
dbeng
Oh, I see where you were going with that now. Yes, I hunted down all
remaining processes after that and manually killed them. Thanks.
On Tue, Jan 14, 2014 at 1:47 PM, Russell Jones wrote:
> Your old xcatd is probably still running. Do a "service xcatd stop",
> then "ps aux | grep xcat" and kil
Unrecognized escape \h passed through
at /opt/xcat/lib/perl/xCAT/zvmUtils.pm line 2408 is a known problem.
You can ignore it. The file is only used on z-series.
if you want to get rid of it
mv /opt/xcat/lib/perl/xCAT/zvmUtils.pm /opt/xcat/lib/perl/xCAT/zvmUtils.pm.save
and
mv /opt/xcat/li
You do not have to stop xcatd the database or anything. Just don't be
running any xcat commands. The upgrade will stop and start xcatd as
needed.
Lissa K. Valletta
8-3/B10
Poughkeepsie, NY 12601
(tie 293) 433-3102
From: Josh Nielsen
To: xCAT Users Mailing list ,
Date: 01/14/201
By the way you normally do not have to stop xcatd before upgrading.
Lissa K. Valletta
8-3/B10
Poughkeepsie, NY 12601
(tie 293) 433-3102
From: Russell Jones
To: xcat-user@lists.sourceforge.net,
Date: 01/14/2014 01:14 PM
Subject:Re: [xcat-user] Update schema after upgrade prem
Two possibilities the daemon did not restart correctly and that has been
common when upgrading from < 2.7.6 to higher levels.
service xcatd stop
ps -ef | grep xcatd
kill -9 any hung xcatd processes
service xcatd start
The other thing is make sure your rpms are all at the 2.8.3 level.
rpm -qa |
Your old xcatd is probably still running. Do a "service xcatd stop",
then "ps aux | grep xcat" and kill any process still running. Then start
xcatd back up and see what you get.
On 1/14/2014 1:41 PM, Josh Nielsen wrote:
Unfortunately, no. Would the MySQL database have to be off as well? I
th
Unfortunately, no. Would the MySQL database have to be off as well? I
thought the daemon might automatically restart after the upgrade, but you
are right that I should have turned it off first.
At this point things still work, but I am most confused about lsxcatd still
returning 2.7.3 to me. Maybe
"makedns " fails with the following message:
"Ignoring host wbire1-en01, it does not belong to any nets defined in
networks
table or the net it belongs to is configured to use an external
nameserver."
After doing some digging, I discovered that the subroutine "my_ip_facing"
in
NetworkUtils.pm
FYI, that should be safe. The schema updates *within* 2.x have generally
been backward compatible. The schema update is done (it checks the tables
and columns instead of something like a version string), so you are good on
that front.
The error message you are getting is unrelated, would have t
FYI, if you look at ipmi.pm, you'll see that it actually has some http
support to get a java webstart file for imm. Having 'ipmi' branch on
mfg/product ids to do non-ipmi stuff wouldn't be a terrible thing.
Unfortunately, it's written in a pretty ugly way (totally my fault, I wrote
the ugliest fa
Did you remember to stop the xcatd service before doing the upgrade?
On 1/14/2014 12:02 PM, Josh Nielsen wrote:
I seem to be getting myself in all kinds of trouble with xCAT lately.
I was upgrading from xCAT 2.7.3 to 2.8.3, I grabbed the latest core
and dep tarballs, and made local yum repos,
I seem to be getting myself in all kinds of trouble with xCAT lately.
I was upgrading from xCAT 2.7.3 to 2.8.3, I grabbed the latest core and dep
tarballs, and made local yum repos, and installed all the newer packages
from them. Then to check if the daemon had been upgraded I did an 'lsxcatd
-v'
When you run nodeset it will try and broadcast the command to any defined
service nodes.We do a better job of checking whether we should
broadcast in 2.8.3.
Lissa K. Valletta
8-3/B10
Poughkeepsie, NY 12601
(tie 293) 433-3102
From: Josh Nielsen
To: xCAT Users Mailing list ,
Date:
Unfortunately that requires some hacking on the wvid script, and we
are trying to avoid customizing default files so that future updates
are much easier.
We'll go forward with implementing nodehm.mgt=iKVM,
nodehm.power=ipmi. That seems to work even though xCAT compla
18 matches
Mail list logo
