Rick Butland wrote:
Christian,
something went wrong here - when you upgrade an array, the basic
procedure is to break the array, which in your case, would leave you
with two "primaries" - the original primary would have a copy of all of
your license key(s), ENS objects, etc. The orphaned secondary (now
primary), will also have a copy of all the ENS objects, and will likely
be in "evaluation/expired" mode, that is, no license keys.
You then upgrade each server, and then re-build the array, using the
original primary as the primary. This should retain all of your license
keys, ENS objects, etc. I can't really imagine what went wrong - if it
backed up your ENS, the installer knew to perform an upgrade operation,
not a fresh install.
All I can think of is that when you rebuilt your array, you might've
used your previous secondary as the primary, which would've
lost/over-written your license keys. But all your ENS objects should
still be there - kind of the whole point of an upgrade / patch
installation is that it preserve all of your system setup, at least to
the extent possible. You should have a setup.log and a
tta.2_postinstall.log - anything, well, "unusual" in there? Any errors
or complaints?
The logs mention "running upgrade script: UpgradeFrom_430000 430915 -> 431905"
and change some attributes.
Then it has
Setting up server beans...
...finished setting up server beans.
Creating objects and links in o=organization
after which it appears to create new objects
+ echo new_person --name "o=Tarantella System Objects/cn=LDAP Profile"
--surname Profile --shared 0 --enabled 1 --inherit 0 -
-links "o=organization"
I'm not sure if this means what it sounds like it means
./loadprobe_config: Set the path, args and filter
Changed tarantella-config-server-tier2loadbalancing-probe for host
iego.cens.nau.edu.
Adding upgraded keys
Removing old keys
But removing old keys makes it sound scary.
Hmmm, I don't know. In general nothing looks particularly scary, but through
most of the process it seems to be creating new ldap objects, which sounds
pretty strange. I can send you the logs if you think it might help.
The process you describe is the same that we followed. Broke the array,
upgraded the primary, then the secondary, then joined the secondary to the
primary again. Strangely the secondary seemed to have more settings saved than
our primary. For example, we were using the firewall transversal mode, and
thus our security port was set to 443. Post upgrade, after rebuilding the
array again, the secondary still had that set, while the primary server has
lost it all.
Is there any hope of being able to recover the old objects, or should I start
adding that information back in again?
Thanks,
Christian McHugh
_______________________________________________
SGD-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sgd-users
