dschaldedfg Absent Member.
Absent Member.
5412 views

OES2 and SLES 10 SP3

Has anyone been noticing issues with adding OES2 to a SLES 10 SP3 server? I have been performing my normal installation routines as I have done in the past, however; I have noticed that during the SLES 10 install that there is an option for SP3. With this update now, I have been having trouble with the installation of NSS for OES2, back to the old dependencies issues, for NSS, talking about EVMS needing to be removed (sorry I do not have the exact error code right now) but wondering if anyone else has seen this, and can let me know what should not be selected in regard to patches? Thank you,
Labels (2)
0 Likes
13 Replies
jmarton2 Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

On Tue, 20 Oct 2009 15:26:03 +0000, dschaldedfg wrote:

> Has anyone been noticing issues with adding OES2 to a SLES 10 SP3
> server?


Do you mean adding OES2 SP2 to a SLES10 SP3 server?



--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.

Joe Marton Emeritus Knowledge Partner
0 Likes
dschaldedfg Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

jmarton;1875281 wrote:
On Tue, 20 Oct 2009 15:26:03 +0000, dschaldedfg wrote:

> Has anyone been noticing issues with adding OES2 to a SLES 10 SP3
> server?


Do you mean adding OES2 SP2 to a SLES10 SP3 server?

No sorry I should have been more clear, I have OES 2 SP 1B, I downloaded back in May of 2009. I am trying to patch the SLES 10 box to the latest and greatest that I have done in the past, when I try to install the OES2 components eDirectory, iManager, both load fine but I have a great deal of issues with NSS and dependencies.


--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

On Tue, 20 Oct 2009 17:06:03 +0000, dschaldedfg wrote:

>> No sorry I should have been more clear, I have OES 2 SP 1B,


That is only compatible with SLES10 SP2. To use SLES10 SP3 you must use
OES2 SP2.


--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.

Joe Marton Emeritus Knowledge Partner
0 Likes
dschaldedfg Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

jmarton;1875390 wrote:
On Tue, 20 Oct 2009 17:06:03 +0000, dschaldedfg wrote:

>> No sorry I should have been more clear, I have OES 2 SP 1B,


That is only compatible with SLES10 SP2. To use SLES10 SP3 you must use
OES2 SP2.

Okay I am trying to be careful with not installing that service pack 3, but it seems that I am still having some issues with EVMS, or LVM. I am trying again today and I will let you know. Is the OES2 SP2 out of Beta (Public) as of yet?

--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

On Tue, 20 Oct 2009 19:56:01 +0000, dschaldedfg wrote:

>> Is the OES2 SP2 out of Beta
>> (Public) as of yet?


I do not believe so.



--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.

Joe Marton Emeritus Knowledge Partner
0 Likes
dschaldedfg Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

jmarton;1875538 wrote:
On Tue, 20 Oct 2009 19:56:01 +0000, dschaldedfg wrote:

>> Is the OES2 SP2 out of Beta
>> (Public) as of yet?


I do not believe so.

Well here was the situation, I installed SLES 10 SP2 just like normal. Then patched it as I have also done in the past. Then installed OES2 Sp1B eDirectory iManager and then NSS when I hit the NSS I had dependencies issues cropping up that I have not seen since I did this same procedure back in May, I am right now trying the update without the EVMS, or LVM in an attempt to see if NSS will install correctly.

--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES2 and SLES 10 SP3

On 20/10/2009 21:16, dschaldedfg wrote:

>> Well here was the situation, I installed SLES 10 SP2 just like normal.
>> Then patched it as I have also done in the past. Then installed OES2
>> Sp1B eDirectory iManager and then NSS when I hit the NSS I had
>> dependencies issues cropping up that I have not seen since I did this
>> same procedure back in May, I am right now trying the update without the
>> EVMS, or LVM in an attempt to see if NSS will install correctly.


I'm wondering if patching SLES10 SP2 is applying the move-to-sles10-sp3
patch?

If so, you need to ensure this doesn't get applied.
--
Simon

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partners (TTP) group. See www.novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
dschaldedfg Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

smflood;1875902 wrote:
On 20/10/2009 21:16, dschaldedfg wrote:

>> Well here was the situation, I installed SLES 10 SP2 just like normal.
>> Then patched it as I have also done in the past. Then installed OES2
>> Sp1B eDirectory iManager and then NSS when I hit the NSS I had
>> dependencies issues cropping up that I have not seen since I did this
>> same procedure back in May, I am right now trying the update without the
>> EVMS, or LVM in an attempt to see if NSS will install correctly.


I'm wondering if patching SLES10 SP2 is applying the move-to-sles10-sp3
patch?

If so, you need to ensure this doesn't get applied.
--
Simon


Good morning Simon, I am now patching this way, grabbing the security patches first, rebooting, then grabbing the Recommended Updates (except for anything relating EVMS, LVM) and making sure that the move-to-sles10-sp3 is not selected. That has worked on one system so far will be checking this again today and will let you know. Not sure why but it only seems to be affecting NSS as mentioned previously eDirectory, and iManager install with no side effects or at least from what I have seen so far. If I apply those patches after I have the OES2 services installed would you foresee any issues?

DS

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partners (TTP) group. See Novell TTP Organization for more details.
------------------------------------------------------------------------
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

On Wed, 21 Oct 2009 14:26:05 +0000, dschaldedfg wrote:

>> Good morning Simon, I am now patching this way, grabbing the security
>> patches first, rebooting, then grabbing the Recommended Updates (except
>> for anything relating EVMS, LVM) and making sure that the
>> move-to-sles10-sp3 is not selected.


Honestly I wouldn't even recommend patching the system. There have been
too many issues in the past with SLES10 patches breaking OES2 components,
so as a result I would install OES2 SP1 as the same time as SLES10 SP2 or
at least not patch SLES prior to installing OES2. After OES2 is
installed feel free to apply all patches which should handle things
correctly.


--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.

Joe Marton Emeritus Knowledge Partner
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES2 and SLES 10 SP3

On 21/10/2009 15:26, dschaldedfg wrote:

>> Good morning Simon, I am now patching this way, grabbing the security
>> patches first, rebooting, then grabbing the Recommended Updates (except
>> for anything relating EVMS, LVM) and making sure that the
>> move-to-sles10-sp3 is not selected. That has worked on one system so far
>> will be checking this again today and will let you know. Not sure why
>> but it only seems to be affecting NSS as mentioned previously
>> eDirectory, and iManager install with no side effects or at least from
>> what I have seen so far. If I apply those patches after I have the OES2
>> services installed would you foresee any issues?


There are two trains of thought regarding installing OES2

1) install SLES10, patch and then add-on OES2
2) install SLES10 + add-on OES2 and then patch both

Both are correct since you should be able to take a SLES10 server and
turn it into an OES2 server at any stage.

However different people have had different results hence the 2 opinions.

I personally, if I know I want OES2 at the beginning, do option 2 and
then that way the right patches will get applied and not affect the OES2
install.

I believe things will be better with OES2 SP2 when released and if you
think about it option 1 should work since the OES2 SPn release is always
after SLES10 SPn+1 has been available ...
0 Likes
dschaldedfg Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

smflood;1876150 wrote:
On 21/10/2009 15:26, dschaldedfg wrote:

>> Good morning Simon, I am now patching this way, grabbing the security
>> patches first, rebooting, then grabbing the Recommended Updates (except
>> for anything relating EVMS, LVM) and making sure that the
>> move-to-sles10-sp3 is not selected. That has worked on one system so far
>> will be checking this again today and will let you know. Not sure why
>> but it only seems to be affecting NSS as mentioned previously
>> eDirectory, and iManager install with no side effects or at least from
>> what I have seen so far. If I apply those patches after I have the OES2
>> services installed would you foresee any issues?


There are two trains of thought regarding installing OES2

1) install SLES10, patch and then add-on OES2
2) install SLES10 + add-on OES2 and then patch both

Both are correct since you should be able to take a SLES10 server and
turn it into an OES2 server at any stage.


Well I tried to always follow option 1 and for the most part that has worked great until this week, when I was having issues with NSS not installing correctly, and so far I have traced it to the EVMS and LVM modules (When I have not installed them, NSS installs correctly). When ever I have tried to do option "2", but I usually had more issues with getting eDirectory products to work so I usually stuck with option "1"
However different people have had different results hence the 2 opinions.

I personally, if I know I want OES2 at the beginning, do option 2 and
then that way the right patches will get applied and not affect the OES2
install.

I believe things will be better with OES2 SP2 when released and if you
think about it option 1 should work since the OES2 SPn release is always
after SLES10 SPn+1 has been available ...


Agreed, I am looking forward to OES2 SP2 coming out and trying that out and seeing what improvements have been made (and hopefully nothing will break 🙂 )
0 Likes
sengkee Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

A side question - I am planning to upgrade to OES2_SP1 with SLES10_SP2, now that SLES10_SP3 is out and OES2_SP2 is coming. What do you all think, should I wait or go ahead now?
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: OES2 and SLES 10 SP3

On Fri, 23 Oct 2009 08:46:03 +0000, sengkee wrote:

> A side question - I am planning to upgrade to OES2_SP1 with SLES10_SP2,
> now that SLES10_SP3 is out and OES2_SP2 is coming. What do you all
> think, should I wait or go ahead now?


Unless you have a pressing need, such as needing to provide AFP access to
Macs *now* or needing to implement DSfW *now* I'd just wait for OES2 SP2.



--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.

Joe Marton Emeritus Knowledge Partner
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.