Anonymous_User Absent Member.
Absent Member.
819 views

Is TID 3009743 still an issue?

Content of TID listed below; Is this still an issue that I need to
work through (i.e. run red carpet oes patches, break clustering,
reinstall the novell-cluster-services-cli to get it going again..)

Thanks for any feedback.
Scott


This document (3009743) is provided subject to the disclaimer at the
end of this document.

environment
Novell Open Enterprise Server (Linux based) Support Pack 2





situation
If you installed a new server from the OES Support Pack 2 media and
added this server to a cluster, then applied patches from the OES
Channel, Novell Cluster Services might stop working because of a file
mismatch.
resolution
To resolve this, complete the following using the OES SP2 Media:
From Yast, click Software . Install and Remove Software
Search for novell-cluster-services-cli
Right click the package, and select Update
Click Accept and follow the prompts
To download the OES SP2 media, see the Consolidated Support Pack
Website

additional notes
The first time you update from the channel using Red Carpet or RUG
after installing a new server, all patches are downloaded form the
channel. Due to a change in the Novell Cluster Services RPM, an older
package is installed causing a file mismatch even though the RPM
Database shows NCS is up-to-date. Updating the
novell-cluster-services-cli package from the OES SP2 media corrects
the file mismatch and the issue is resolved for any future channel
updates
document
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Is TID 3009743 still an issue?

I'm not Novell, and neither tested this solution, but I would.
Apply PATCH 11147 before anything else.
stop all red-carpet client.
/etc/init.d/rcd stop
ps ax | grep rcd (to make sure rcd is stopped... it may hang...)
/etc/init.d/rcd start
then apply your patchs.
patch 11147 will patch red-carpet, to prevent download all patchs again
(should download around 800mb, instead of 1200mb)

Marc


Scott S wrote:
> Content of TID listed below; Is this still an issue that I need to
> work through (i.e. run red carpet oes patches, break clustering,
> reinstall the novell-cluster-services-cli to get it going again..)
>
> Thanks for any feedback.
> Scott
>
>
> This document (3009743) is provided subject to the disclaimer at the
> end of this document.
>
> environment
> Novell Open Enterprise Server (Linux based) Support Pack 2
>
>
>
>
>
> situation
> If you installed a new server from the OES Support Pack 2 media and
> added this server to a cluster, then applied patches from the OES
> Channel, Novell Cluster Services might stop working because of a file
> mismatch.
> resolution
> To resolve this, complete the following using the OES SP2 Media:
> From Yast, click Software . Install and Remove Software
> Search for novell-cluster-services-cli
> Right click the package, and select Update
> Click Accept and follow the prompts
> To download the OES SP2 media, see the Consolidated Support Pack
> Website
>
> additional notes
> The first time you update from the channel using Red Carpet or RUG
> after installing a new server, all patches are downloaded form the
> channel. Due to a change in the Novell Cluster Services RPM, an older
> package is installed causing a file mismatch even though the RPM
> Database shows NCS is up-to-date. Updating the
> novell-cluster-services-cli package from the OES SP2 media corrects
> the file mismatch and the issue is resolved for any future channel
> updates
> document

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Is TID 3009743 still an issue?

Thanks Marc...that is an improvement to the process. I'm giving up on
the oes linux cluster project and going back to netware. It's taken
too long with too many complications in the process. I might give it
another shot when OES has Sles 10 as the kernel.

On Tue, 17 Oct 2006 00:31:37 GMT, Marc-Andre Vallee
<marc-andre.vallee.remove-this@complys.dotalsothat.com> wrote:

>I'm not Novell, and neither tested this solution, but I would.
>Apply PATCH 11147 before anything else.
>stop all red-carpet client.
>/etc/init.d/rcd stop
>ps ax | grep rcd (to make sure rcd is stopped... it may hang...)
>/etc/init.d/rcd start
>then apply your patchs.
>patch 11147 will patch red-carpet, to prevent download all patchs again
>(should download around 800mb, instead of 1200mb)
>
>Marc
>
>
>Scott S wrote:
>> Content of TID listed below; Is this still an issue that I need to
>> work through (i.e. run red carpet oes patches, break clustering,
>> reinstall the novell-cluster-services-cli to get it going again..)
>>
>> Thanks for any feedback.
>> Scott
>>
>>
>> This document (3009743) is provided subject to the disclaimer at the
>> end of this document.
>>
>> environment
>> Novell Open Enterprise Server (Linux based) Support Pack 2
>>
>>
>>
>>
>>
>> situation
>> If you installed a new server from the OES Support Pack 2 media and
>> added this server to a cluster, then applied patches from the OES
>> Channel, Novell Cluster Services might stop working because of a file
>> mismatch.
>> resolution
>> To resolve this, complete the following using the OES SP2 Media:
>> From Yast, click Software . Install and Remove Software
>> Search for novell-cluster-services-cli
>> Right click the package, and select Update
>> Click Accept and follow the prompts
>> To download the OES SP2 media, see the Consolidated Support Pack
>> Website
>>
>> additional notes
>> The first time you update from the channel using Red Carpet or RUG
>> after installing a new server, all patches are downloaded form the
>> channel. Due to a change in the Novell Cluster Services RPM, an older
>> package is installed causing a file mismatch even though the RPM
>> Database shows NCS is up-to-date. Updating the
>> novell-cluster-services-cli package from the OES SP2 media corrects
>> the file mismatch and the issue is resolved for any future channel
>> updates
>> document

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.