Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NNLS on SLES 9.1 LDAP problem

0 views
Skip to first unread message

ric...@co.mason.wa.us

unread,
Mar 11, 2005, 6:37:53 PM3/11/05
to
We are installing NNLS on SLES 9.1 (going through the CLE Study Guide)
and having many adventures. I was so excited when I finally got to the
point I could actually install NNLS.

Imagine my disappointment when, while attempting to install LDAP, the
script reported that it couldn't do so because LDAP port 389 was already
in use! OF COURSE IT'S IN USE; IT WAS ALREADY INSTALLED WITH SLES 9.1!
(Sorry about the shouting. I feel better now. I'll try not to do it
again.)

Since LDAP doesn't install, neither do any of the features that install
after it and depend on it. I tried running chkconfig ldap off from
another terminal window, but that didn't help. Then I tried to uninstall
everything and have another go at it, but it won't uninstall eDirectory
because -- guess what? -- the admin user can't authenticate via LDAP (I
had already re-started LDAP).

I'll re-start the computer and try uninstalling again, but if that
doesn't work, I'm stuck. Even if I start from scratch (re-install SLES
9.1), how can I get past this Catch-22?

Richard

Paul Gear

unread,
Mar 13, 2005, 6:42:08 PM3/13/05
to
ric...@co.mason.wa.us wrote:
> We are installing NNLS on SLES 9.1 (going through the CLE Study Guide)
> and having many adventures. I was so excited when I finally got to the
> point I could actually install NNLS.
> ...

> I'll re-start the computer and try uninstalling again, but if that
> doesn't work, I'm stuck. Even if I start from scratch (re-install SLES
> 9.1), how can I get past this Catch-22?

Make sure you don't install the OpenLDAP servers with the SLES
install. If you choose minimal install (recommended by the NNLS
documentation, if i remember correctly), then it should work.

If you can't get the right results this way, then after you've
installed SLES but before NNLS, remove the LDAP server packages with
YaST or 'rpm -ev' on the command line.

BTW, are you talking about SuSE Pro 9.1, or SLES9 SP1? There is
nothing that Novell have released actually called SLES 9.1, to my
knowledge.

--
Paul Gear, Manager IT Operations, Redlands College
38 Anson Road, Wellington Point 4160, Australia
(Please send attachments in portable formats such as PDF, HTML, or
OpenOffice.)
--
The information contained in this message is copyright by Redlands
College. Any use for direct sales or marketing purposes is expressly
forbidden. This message does not represent the views of Redlands
College.

ric...@co.mason.wa.us

unread,
Mar 14, 2005, 11:29:10 AM3/14/05
to
> BTW, are you talking about SuSE Pro 9.1, or SLES9 SP1? There is
> nothing that Novell have released actually called SLES 9.1, to my
> knowledge.

For reasons not entirely clear to me, the CDs I'm using are labeled 9.1.
The license filed on it says it is SLES 9. I guess it is just that.

Richard

ric...@co.mason.wa.us

unread,
Mar 14, 2005, 7:51:53 PM3/14/05
to

> Make sure you don't install the OpenLDAP servers with the SLES
> install. If you choose minimal install (recommended by the NNLS
> documentation, if i remember correctly), then it should work.

Thanks. I did it that way (select Minimum install, then Details. The CLE
Study Guide doesn't say anything about that.). I did encounter some
gotchas, however.

1) This time the SLES install put in openslp-server-1.1.5-73.9, which is
newer than the one I had downloaded from SUSE's ftp server; it was
openslp-server-1.1.5-73.i586. I tried doig what the study guide said and
downloading the latest stable build binary, which is
openslp-1.2.0-1.i386, but it has a missing dependency. So I stayed with
what I had.

2) In setting up DNS according to the study guide, one of the steps is
creating /var/named/named.hosts. The named.hosts file is referenced in a
previous step, in which I edited the /etc/named.conf file. The problem is
that there is no /var/named directory, so I created one, but I am most
puzzled as to whether the /etc/named.conf file needs to reference that
file with a full path.

3) NNLS installed fine up to the very last package, which is Red Carpet.
It said it had a dependency on python version 1.5.2 or better, and asked
if I wanted to continue anyway. I said "yes", then started YAST2,
searched for "python" (a lot of items showed up), selected them all and
installed. This hit some conflicts in apache, which I resolved by
overwriting the existing items, and also some NetMail problems. YAST
claimed that NetMail depended on NDSslp. The book said not to use this,
but to install openslp. I selected the bottom item (whatever that was; I
haven't got to NetMail yet) and proceeded.

4) Thinking that it had not installed Red Carpet because of the missing
dependency, I ran install.sh again, but it claimed that RC was installed.
So I proceeded to the first exercises, which require iManager. iManager
started OK and the first steps went OK, but when I got to the part where
I am supposed to manage the RCD group I had just created. When I hit the
Get Devices button, my server -- cle1.cle.com -- showed up but its status
was Unavailable.

So eDirectory was up and running, but it didn't think that this server
was an NCP server. So I re-booted the server, thinking that some service
didn't start. NOW I can't get iManager running. When I try to go to
https://10.1.17.3/nps/iManger.html, I get:

An error occurred while loading https://10.1.17.3/nps/iManager.html:
The process for the https://10.1.17.3 protocol died unexpectedly.

I suspect this is a Tomcat or Apache error.

This is so exasperating. While this stuff is rather new, I am not
incompetent in this field. I have found a couple of gotchas in this book
and solved them on my own. It seems, though, that every time I get over
one obstacle I encounter another one, even though I have performed every
step in the book, and this book is from Novell Press.

My boss and I are going to Brainshare and hope to learn enough to use
NNLS here. Our experience so far has not made us optimistic. He's talking
about using Linux without any Novell stuff. My problem with that is file
system rights, which are far more challenging in Linux than in Novell, at
least where shared directories are concerned. But that's another topic.

Tks n rgds,
Richard

ric...@co.mason.wa.us

unread,
Mar 15, 2005, 7:33:25 PM3/15/05
to
If you have read my last post, then I have made some progress. The
problem with iManger was actually with DNS. My /etc/named.conf file got
funny. When I corrected that, I could load iManger OK, but it still
doesn't recognize that my server is "up" when I am in Manage RCD Group.

Well, I guess I will press on with the exercises in the Study Guide. I
have learned a lot more than the authors of the Study Guide intended,
since there are some "holes" in their text.

Tks n rgds,
Richard

Paul Gear

unread,
Mar 20, 2005, 7:22:53 PM3/20/05
to
ric...@co.mason.wa.us wrote:
>
>
>>Make sure you don't install the OpenLDAP servers with the SLES
>>install. If you choose minimal install (recommended by the NNLS
>>documentation, if i remember correctly), then it should work.
>
>
> Thanks. I did it that way (select Minimum install, then Details. The CLE
> Study Guide doesn't say anything about that.).

I think that part's in the NNLS install guide.

> ...


> 2) In setting up DNS according to the study guide, one of the steps is
> creating /var/named/named.hosts. The named.hosts file is referenced in a
> previous step, in which I edited the /etc/named.conf file. The problem is
> that there is no /var/named directory, so I created one, but I am most
> puzzled as to whether the /etc/named.conf file needs to reference that
> file with a full path.

I think /var/named is a typo for /var/lib/named. You usually
shouldn't have to touch anything in there. Which manual refers you to it?

> ...


> This is so exasperating. While this stuff is rather new, I am not
> incompetent in this field. I have found a couple of gotchas in this book
> and solved them on my own. It seems, though, that every time I get over
> one obstacle I encounter another one, even though I have performed every
> step in the book, and this book is from Novell Press.

They do seem to need to polish their installation software and process
documentation... Sorry i can't help on any of the other issues.

0 new messages