headers
Joe Acquisto | 8 Jun 2011 21:55
Picon

OES1 (linux) to OES2 upgrade - cluster convert commit error

Having, at last, completed upgrading a test OES1 cluster ot OES2, get an
error doing the
"cluster convert commit" command-

"An LDAP error  occurred while converting the cluster - The cluster was not
converted."

Doing "cluster convert preview"  tells me that "no modification was
necessary" for Master IP, load and unload scripts.
An LDAP trace (done as a novice) is none too communicative.

The cluster man pages indicates this command is only necessary when
converting NetWare clusters to Linux.

Yet the OES 2 SP3 NCS 1.8.8 Admin Guide for Linux (pg 85 finalizing cluster
upgrade) states this command must
be run.

Oh, Wise Ones, what is to be done?

ioe a.
Permalink | Reply | 3 comments |
headers
Peter Van Lone | 8 Jun 2011 23:43
Picon

Re: OES1 (linux) to OES2 upgrade - cluster convert commit error

I've no idea - but I do wonder (in this case out loud):

How many OES1 and/or OES2 clusters do you think there are in
production anywhere in the world?

Do you think the total exceeds 1000? 5000?

I would bet few more than 1000 in the whole wide world - would be kind
of fun to know, for sure ...

P

------------------------------------
The whole problem with the world is that fools and fanatics are always
so certain of themselves, and wiser people so full of doubts.
  --Bertrand Russell

http://www.the-brights.net
http://xkcd.com/167
http://xkcd.com/836/

On Wed, Jun 8, 2011 at 2:55 PM, Joe Acquisto <joe.acquisto <at> gmail.com> wrote:
> Having, at last, completed upgrading a test OES1 cluster ot OES2, get an
> error doing the
> "cluster convert commit" command-
>
> "An LDAP error  occurred while converting the cluster - The cluster was not
> converted."
>
> Doing "cluster convert preview"  tells me that "no modification was
(Continue reading)

Permalink | Reply | 1 comment |
headers
Randy Grein | 9 Jun 2011 00:16

RE: OES1 (linux) to OES2 upgrade - cluster convert commit error

There are still a few hanging out in Washington State (at Microsoft even) so I'll bet it's over 5,000
worldwide - double that, easy. 

-----Original Message-----
From: novell-bounces <at> netlab1.oucs.ox.ac.uk [mailto:novell-bounces <at> netlab1.oucs.ox.ac.uk] On
Behalf Of Peter Van Lone
Sent: Wednesday, June 08, 2011 2:44 PM
To: Novell LAN Interest Group
Subject: Re: OES1 (linux) to OES2 upgrade - cluster convert commit error

I've no idea - but I do wonder (in this case out loud):

How many OES1 and/or OES2 clusters do you think there are in
production anywhere in the world?

Do you think the total exceeds 1000? 5000?

I would bet few more than 1000 in the whole wide world - would be kind
of fun to know, for sure ...

P

------------------------------------
The whole problem with the world is that fools and fanatics are always
so certain of themselves, and wiser people so full of doubts.
  --Bertrand Russell

http://www.the-brights.net
http://xkcd.com/167
http://xkcd.com/836/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Acquisto | 9 Jun 2011 14:57
Picon

Re: OES1 (linux) to OES2 upgrade - cluster convert commit error

Feedback from the Attachmate/Novell forums states this command does not need
to be run, in this circumstance
and that the online docs will be corrected.

joe a.

On Wed, Jun 8, 2011 at 3:55 PM, Joe Acquisto <joe.acquisto <at> gmail.com> wrote:

> Having, at last, completed upgrading a test OES1 cluster ot OES2, get an
> error doing the
> "cluster convert commit" command-
>
> "An LDAP error  occurred while converting the cluster - The cluster was not
> converted."
>
> Doing "cluster convert preview"  tells me that "no modification was
> necessary" for Master IP, load and unload scripts.
> An LDAP trace (done as a novice) is none too communicative.
>
> The cluster man pages indicates this command is only necessary when
> converting NetWare clusters to Linux.
>
> Yet the OES 2 SP3 NCS 1.8.8 Admin Guide for Linux (pg 85 finalizing cluster
> upgrade) states this command must
> be run.
>
> Oh, Wise Ones, what is to be done?
>
> ioe a.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Acquisto | 23 Jun 2011 19:22
Picon

SLES10 SP3 boot menu

Upgraded a server to OES2.  All fine.

Added an HP psp.  Upon reboot there were several additional boot menu
selections (all showing HP kernels) and the highlighted selection was one of
those.  Being quick, as usual,  I stood immobile while it began to boot.
A quick CTRL-ALT-DEL, soon brought back the menu, where I selected the
normal default and it appears to have booted without issue, and appears to
function normally.

Whilst I go out and research how to correct this oddness, (actually, I'm
going to sit right here and "surf"), can anyone save me perhaps hours of
tedium?

joe a.
Permalink | Reply | 3 comments |
headers
Joe Acquisto | 23 Jun 2011 19:26
Picon

Re: SLES10 SP3 boot menu

YAST to the rescue.   Oddly, tho, it shows the boot order as I expected it,
not with the incorrectly highlighted item.   I guess some reboots are in
order, to test.

joe a

On Thu, Jun 23, 2011 at 1:22 PM, Joe Acquisto <joe.acquisto <at> gmail.com>wrote:

> Upgraded a server to OES2.  All fine.
>
> Added an HP psp.  Upon reboot there were several additional boot menu
> selections (all showing HP kernels) and the highlighted selection was one of
> those.  Being quick, as usual,  I stood immobile while it began to boot.
> A quick CTRL-ALT-DEL, soon brought back the menu, where I selected the
> normal default and it appears to have booted without issue, and appears to
> function normally.
>
> Whilst I go out and research how to correct this oddness, (actually, I'm
> going to sit right here and "surf"), can anyone save me perhaps hours of
> tedium?
>
> joe a.
>
Permalink | Reply | 0 comments |
headers
Joe Doupnik | 23 Jun 2011 19:41
Picon
Picon
Favicon

Re: SLES10 SP3 boot menu

     Examine carefully /boot/grub/menu.lst. It will show you the default 
boot option.
     Joe D.

On 23/06/2011 18:22, Joe Acquisto wrote:
> Upgraded a server to OES2.  All fine.
>
> Added an HP psp.  Upon reboot there were several additional boot menu
> selections (all showing HP kernels) and the highlighted selection was one of
> those.  Being quick, as usual,  I stood immobile while it began to boot.
> A quick CTRL-ALT-DEL, soon brought back the menu, where I selected the
> normal default and it appears to have booted without issue, and appears to
> function normally.
>
> Whilst I go out and research how to correct this oddness, (actually, I'm
> going to sit right here and "surf"), can anyone save me perhaps hours of
> tedium?
>
> joe a.
> _______________________________________________
> Novell mailing list
> Novell <at> netlab1.oucs.ox.ac.uk
> http://netlab1.usu.edu/mailman/listinfo/novell
Permalink | Reply | 1 comment |
headers
Paul Koochin | 23 Jun 2011 19:43
Picon
Favicon

Re: SLES10 SP3 boot menu

You can also set the default in YAST under System -> Boot Loader

PK

>>> Joe Doupnik <jrd <at> netlab1.oucs.ox.ac.uk> 23/06/2011 11:41 AM >>>
Examine carefully /boot/grub/menu.lst. It will show you the default 
boot option.
     Joe D.

On 23/06/2011 18:22, Joe Acquisto wrote:
> Upgraded a server to OES2.  All fine.
>
> Added an HP psp.  Upon reboot there were several additional boot menu
> selections (all showing HP kernels) and the highlighted selection was one of
> those.  Being quick, as usual,  I stood immobile while it began to boot.
> A quick CTRL-ALT-DEL, soon brought back the menu, where I selected the
> normal default and it appears to have booted without issue, and appears to
> function normally.
>
> Whilst I go out and research how to correct this oddness, (actually, I'm
> going to sit right here and "surf"), can anyone save me perhaps hours of
> tedium?
>
> joe a.
> _______________________________________________
> Novell mailing list
> Novell <at> netlab1.oucs.ox.ac.uk 
> http://netlab1.usu.edu/mailman/listinfo/novell 

_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Acquisto | 23 Jun 2011 21:18
Picon

Fwd: SLES10 SP3 boot menu

HP does lay claim to having made those changes, setting default to 5, and
"fallback" to 4.  YAST still sees default as 1.

They may know what they are doing, but I do not.   Must I rely on their
expertise?

I confess to some consternation, as I installed the psp on my test box,
remotely, and did not witness the reboot "on the box", so missed this in
testing.  Not a mistake I will make again.

joe a.

On Thu, Jun 23, 2011 at 2:19 PM, Joe Doupnik <jrd <at> netlab1.oucs.ox.ac.uk>wrote:

> **
>     Please read that file again, starting at the top.
>     Joe D.
> -----------
>
> On 23/06/2011 19:01, Joe Acquisto wrote:
>
> It appears the only difference, beside Title info, is the initrd image.
> root and kernel info appears identical.
>
> Wondering now if I should have let it boot up.
>
> joe a.
>
> On Thu, Jun 23, 2011 at 1:41 PM, Joe Doupnik <jrd <at> netlab1.oucs.ox.ac.uk>wrote:
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Acquisto | 27 Jun 2011 17:00
Picon

OES2 upgrade - new registration code?

After and OES2 upgrade is complete, wondering if a new registration code is
needed and if a manual re-registration is needed.   Obviously, could "just
try it" but . . .sometimes that is just not the prudent course.

joe a.
Permalink | Reply | 1 comment |

Gmane