Anonymous_User Absent Member.
Absent Member.
1200 views

Problems after updating new OES sp2 installation

After I ran all the updates via Red Carpet the system now will not boot to
the gui even though I have rulevel 5 selected. I am also unable to create
an NSS pool using nssmu. I am using EVMS as the volume manager an have free
space. When I try I get "Write Error" "ERR_USER_ABORTED(20017)" It seemd
the updates have broken something, This has happened on 2 different
installations now and there were no errors during the update process.

Thanks
Jerry


Labels (2)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Problems after updating new OES sp2 installation

Jerry, I sympathise with you!

OES Linux is an incomplete product which has been rushed through by Novell.

The updates through RUG are poor to say the least.

I have broken my OES server on countless number of times through RUG and
now we have our rollout on hold.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Problems after updating new OES sp2 installation

I'm not sure if this is the case for you, but I learned the hard way.
When doing updates through red-carpet (the gui) it is a BAD idea to do the
updates on the "updates" tab. Especially before the "patches" tab is
cleared. They are individual packages, and some of them, while higher
versions and all the depedencies are met, break some OESand GNU stuff. Only
do those updates if you absolutely need that package updated, and it is not
provided by a "patch".

In other words, doing the updates from the "patches" tab will take care of
most of the packages, and will take care of some dependency issues as well.
I would make sure all of the "patches" are done before doing anything from
the updates tab, and then only if you know you need it.

I'm pretty sure using the command line only does the "patches" as well, but
very well may be mistaken
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Problems after updating new OES sp2 installation

On Fri, 23 Feb 2007 03:02:03 +0000, Adam Gabriel wrote:

> I'm not sure if this is the case for you, but I learned the hard way. When
> doing updates through red-carpet (the gui) it is a BAD idea to do the
> updates on the "updates" tab. Especially before the "patches" tab is
> cleared. They are individual packages, and some of them, while higher
> versions and all the depedencies are met, break some OESand GNU stuff.
> Only do those updates if you absolutely need that package updated, and it
> is not provided by a "patch".



NEVER do updates! As per the docs, patches are all you should ever
install. If you're going to patch OES Linux, then apply patch-11371 first
to fix rug...

>
> In other words, doing the updates from the "patches" tab will take care of
> most of the packages, and will take care of some dependency issues as
> well. I would make sure all of the "patches" are done before doing
> anything from the updates tab, and then only if you know you need it.
>
> I'm pretty sure using the command line only does the "patches" as well,
> but very well may be mistaken


The command line will do both. rug pin is the patches one.

--
Mark Robinson
Novell Volunteer SysOp
www.nds8.co.uk
One by one the penguins steal my sanity...

0 Likes
Anonymous_User Absent Member.
Absent Member.

Problems after updating new OES sp2 installation

Are these installations on HP Servers? There is a known issue with OES SP2
and specifically HP DL380 systems. We see the same issue occur on DL360's
also. These systems are all systems that have been setup to use EVMS. What
we have experienced is that after rebooting with SP2, we loose networking
and CDROM funtionality.

I don't have the TID for the solution, but do have a detailed cut from the
TID.
---------------------------------------------------------------------------
Solution:
The HP agent installation modified the grub menu to default to an HP
derivative or the original kernal. When RUG updates were applied the
default kernel was changed, but not the HP version that was the default
for GRUB.

Changing the default for /boot/grub/menu.lst back to Linux, option 0 from
the HP kernel, option 3 fixed the problem.
---------------------------------------------------------------------------

> After I ran all the updates via Red Carpet the system now will not boot

to
> the gui even though I have rulevel 5 selected. I am also unable to

create
> an NSS pool using nssmu. I am using EVMS as the volume manager an have

free
> space. When I try I get "Write Error" "ERR_USER_ABORTED(20017)" It

seemd
> the updates have broken something, This has happened on 2 different
> installations now and there were no errors during the update process.
>
> Thanks
> Jerry
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Problems after updating new OES sp2 installation

On Wed, 28 Feb 2007 21:55:36 +0000, davedk wrote:

> Are these installations on HP Servers? There is a known issue with OES SP2
> and specifically HP DL380 systems. We see the same issue occur on DL360's
> also. These systems are all systems that have been setup to use EVMS. What
> we have experienced is that after rebooting with SP2, we loose networking
> and CDROM funtionality.


Hmm, I have just built a 6 node cluster on DL380 G5s. No problems at all!
Mind you, I haven't touched the HP agent stuff - no way that's getting
near my servers 🙂

--
Mark Robinson
Novell Volunteer SysOp
www.nds8.co.uk
One by one the penguins steal my sanity...

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Problems after updating new OES sp2 installation

I don't fully understand the concept myself. We built the system to use
EVMS and then just swapped CD's as the system requested. A basic load of
OES SP1. That build works fine. Then when we either update the system
through RUG or directly from the OES SP2 CD, the system breaks. Networking
and CDROM functionality become inopperable. Making a recover pretty
diffucult when you can't access a CD or the network.

The support person that I spoke with indicated at the time that there was
no fix other than rebuilding the system. (Difficult to do when the system
was put into production on SP1 pre SP2.)

DK
> On Wed, 28 Feb 2007 21:55:36 +0000, davedk wrote:
>
> > Are these installations on HP Servers? There is a known issue with OES

SP2
> > and specifically HP DL380 systems. We see the same issue occur on

DL360's
> > also. These systems are all systems that have been setup to use EVMS.

What
> > we have experienced is that after rebooting with SP2, we loose

networking
> > and CDROM funtionality.

>
> Hmm, I have just built a 6 node cluster on DL380 G5s. No problems at

all!
> Mind you, I haven't touched the HP agent stuff - no way that's getting
> near my servers 🙂
>
> --
> Mark Robinson
> Novell Volunteer SysOp
> www.nds8.co.uk
> One by one the penguins steal my sanity...
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Problems after updating new OES sp2 installation

On Thu, 01 Mar 2007 16:40:51 +0000, davedk wrote:

> I don't fully understand the concept myself. We built the system to use
> EVMS and then just swapped CD's as the system requested. A basic load of
> OES SP1. That build works fine. Then when we either update the system
> through RUG or directly from the OES SP2 CD, the system breaks. Networking
> and CDROM functionality become inopperable. Making a recover pretty
> diffucult when you can't access a CD or the network.


True, but you should be able to get boot from the SP2 CD and use the
system repair functionality

> The support person that I spoke with indicated at the time that there
> was no fix other than rebuilding the system. (Difficult to do when the
> system was put into production on SP1 pre SP2.)


Well, the upgrade from SP1 to SP2 should be quite easy. I did a few, and
none broke. How exactly did you do the update, and do you have more to
do?

--
Mark Robinson
Novell Volunteer SysOp
www.nds8.co.uk
One by one the penguins steal my sanity...

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.