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 <[email protected]> To: [email protected], Date: 01/14/2014 01:14 PM Subject: Re: [xcat-user] Update schema after upgrade prematurely terminated 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, and installed all the newer packages from them. Then to check if the daemon had been upgraded I did an 'lsxcatd -v' and it still said 2.7.3. So I decided to run the xcat daemon manually from the command line with the verbose flag but wasn't expecting to see the schema updates (honestly all I saw were SQL commands scrolling in the screen - I didn't know they were for the schema at the time) and I panicked and hit CRTL+C. This halted the daemon & updates but the next time I tried to run it I got an error although the daemon ran in the background. This is from my terminal: root@x3650-head01 yum.repos.d]# /opt/xcat/sbin/xcatd -v updateschema: Running ALTER TABLE mpa ADD `displayname` TEXT updateschema: Running ALTER TABLE mpa ADD `slots` TEXT updateschema: Running ALTER TABLE mpa ADD `urlpath` TEXT updateschema: Running ALTER TABLE servicenode ADD `dhcpinterfaces` TEXT updateschema: Running ALTER TABLE switches ADD `protocol` TEXT updateschema: Running ALTER TABLE hypervisor ADD `interface` TEXT updateschema: Running ALTER TABLE vmmaster ADD `specializeparameters` TEXT updateschema: Running ALTER TABLE linuximage ADD `boottarget` TEXT updateschema: Running ALTER TABLE linuximage ADD `addkcmdline` TEXT updateschema: Running ALTER TABLE linuximage ADD `partitionfile` TEXT updateschema: Running ALTER TABLE linuximage ADD `driverupdatesrc` TEXT updateschema: Running ALTER TABLE nodelist ADD `updatestatus` TEXT updateschema: Running ALTER TABLE nodelist ADD `updatestatustime` TEXT updateschema: Running ALTER TABLE networks ADD `staticrange` TEXT updateschema: Running ALTER TABLE networks ADD `staticrangeincrement` TEXT updateschema: Running ALTER TABLE vm ADD `mgr` TEXT updateschema: Running ALTER TABLE vm ADD `storagecache` TEXT updateschema: Running ALTER TABLE vm ADD `storageformat` TEXT updateschema: Running ALTER TABLE vm ADD `cluster` TEXT updateschema: Running ALTER TABLE vm ADD `physlots` TEXT updateschema: Running ALTER TABLE litetree ADD `mntopts` TEXT updateschema: Running ALTER TABLE domain ADD `authdomain` TEXT updateschema: Running ALTER TABLE domain ADD `adminuser` TEXT updateschema: Running ALTER TABLE domain ADD `adminpassword` TEXT updateschema: Running ALTER TABLE domain ADD `type` TEXT updateschema: Running ALTER TABLE nodegroup ADD `membergroups` TEXT updateschema: Running ALTER TABLE noderes ADD `nameservers` TEXT updateschema: Running ALTER TABLE osimage ADD `groups` TEXT updateschema: Running ALTER TABLE osimage ADD `description` TEXT updateschema: Running ALTER TABLE osimage ADD `osdistroname` TEXT updateschema: Running ALTER TABLE osimage ADD `osupdatename` VARCHAR (1024) updateschema: Running ALTER TABLE osimage ADD `cfmdir` TEXT updateschema: Running ALTER TABLE osimage ADD `serverrole` TEXT updateschema: Running ALTER TABLE osimage ADD `isdeletable` TEXT updateschema: Running ALTER TABLE osimage ADD `kitcomponents` TEXT updateschema: Running ALTER TABLE passwd ADD `authdomain` TEXT updateschema: Running ALTER TABLE nodepos ADD `height` TEXT updateschema: Running ALTER TABLE nodehm ADD `cmdmapping` TEXT [root@x3650-head01 yum.repos.d]# /opt/xcat/sbin/xcatd -v Unrecognized escape \h passed through at /opt/xcat/lib/perl/xCAT/zvmUtils.pm line 2408. Despite this I can still use 'service xcatd restart' and start the daemon, and I can run psh commands and tabdump etcetera, but now I'm unsure whether the xCAT MySQL database is in an inconsistent state and has not received all the schema updates it was supposed to. I was hoping that by running xcatd -v again I would see it try again but I haven't. And even after all that I still see 2.7.3 when I type 'lsxcatd'. Maybe I need to restart the node. Any clue if there is a way to rerun the schema changes? Thanks, Josh Nielsen ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
