[Fedora-directory-users] how to bind fedora-ds to one of IPs?
by Sergey Ivanov
Hi,
I'd like to restrict ns-slapd to listen to LAN. It is installed at the
computer having 2 interfaces, pointing to WAN and LAN. Are there some
way to bind ns-slapd to listen for one of these 2 IPs, not to 0.0.0.0?
--
WBR,
Sergey
17 years, 7 months
RE: [Fedora-directory-users] Problems installing FDS
by James Richardson
Doh!
I spent a lot of effort tracking this down, making sure I had everything
in order.... And I fat-fingered the address in DNS.
Install works great now. :)
Thanks,
James T. Richardson, Jr.
jrichardson(a)x-iss.com
eXcellence in IS Solutions, Inc.
Office: 713-862-9200 x226
-----Original Message-----
From: fedora-directory-users-bounces(a)redhat.com
[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Richard
Megginson
Sent: Tuesday, August 29, 2006 3:31 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] Problems installing FDS
James Richardson wrote:
> Hi All,
>
> I'm trying to get a test Fedora Directory server up and running and am
> not having much success.
>
> When I complete the setup program I get the following output:
>
>
> ----------------------------------------------------------------------
> --
> --
> [slapd-fds01]: starting up server ...
> [slapd-fds01]: Fedora-Directory/1.0.2 B2006.060.1928
> [slapd-fds01]: fds01.mydomain.tld:389 (/opt/fedora-ds/slapd-fds01)
> [slapd-fds01]:
> [slapd-fds01]: [29/Aug/2006:15:23:05 -0500] - Fedora-Directory/1.0.2
> B2006.060.1
> 928 starting up
> [slapd-fds01]: [29/Aug/2006:15:23:06 -0500] - slapd started.
> Listening on All I nterfaces port 389 for LDAP requests Your new
> directory server has been started.
> Created new Directory Server
> Start Slapd Starting Slapd server configuration.
> Fatal Slapd ERROR: Ldap authentication failed for url
> ldap://fds01.mydomain.tld:
> 389/o=NetscapeRoot user id admin (151:Unknown error.) Fatal Slapd Did
> not add Directory Server information to Configuration Server.
> Configuring Administration Server...
> Setting up Administration Server Instance...
> ERROR: Administration Server configuration failed.
> You can now use the console. Here is the command to use to start the
> console:
> cd /opt/fedora-ds
> ./startconsole -u admin -a http://fds01.mydomain.tld:55573/ INFO
> Finished with setup, logfile is setup/setup.log
> [root@fds01 ~]#
> ----------------------------------------------------------------------
> --
> --
>
> I am a bit troubled by the errors it reports. Also,
"fds01.mydomain.tld"
> is in DNS correctly.
err 151 usually indicates some problem with hostname or IP address
resolution. Could it be that your /etc/nsswitch.conf or /etc/hosts or
NIS settings cause fds01.mydomain.tld to resolve to a different IP, or
that the IP resolves to a different hostname?
> Also, nothing is listening on port 55573 as it tells me to connect the
> console to.
>
Right. Installation failed, so the admin server is not running.
> I also am not using the default Java that comes with CentOS 4.3. I
> downloaded and installed IBMJava2 1.4.2 and am running it. I could not
> use the bundled CentOS4.3 Java as it would not run the console
> application.
>
Right.
> Can someone please help, I am not sure where to go next.
>
>
>
>
>
> Thanks,
>
> James T. Richardson, Jr.
> jrichardson(a)x-iss.com
> eXcellence in IS Solutions, Inc.
> Office: 713-862-9200 x226
> NOTICE:
> This message may contain privileged or otherwise confidential
information. If you are not the intended recipient, please immediately
advise the sender by reply email and delete the message and any
attachments without using, copying or disclosing the contents.
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
NOTICE:
This message may contain privileged or otherwise confidential information. If you are not the intended recipient, please immediately advise the sender by reply email and delete the message and any attachments without using, copying or disclosing the contents.
17 years, 7 months
[Fedora-directory-users] Problems installing FDS
by James Richardson
Hi All,
I'm trying to get a test Fedora Directory server up and running and am
not having much success.
When I complete the setup program I get the following output:
------------------------------------------------------------------------
--
[slapd-fds01]: starting up server ...
[slapd-fds01]: Fedora-Directory/1.0.2 B2006.060.1928
[slapd-fds01]: fds01.mydomain.tld:389 (/opt/fedora-ds/slapd-fds01)
[slapd-fds01]:
[slapd-fds01]: [29/Aug/2006:15:23:05 -0500] - Fedora-Directory/1.0.2
B2006.060.1
928 starting up
[slapd-fds01]: [29/Aug/2006:15:23:06 -0500] - slapd started. Listening
on All I
nterfaces port 389 for LDAP requests
Your new directory server has been started.
Created new Directory Server
Start Slapd Starting Slapd server configuration.
Fatal Slapd ERROR: Ldap authentication failed for url
ldap://fds01.mydomain.tld:
389/o=NetscapeRoot user id admin (151:Unknown error.)
Fatal Slapd Did not add Directory Server information to Configuration
Server.
Configuring Administration Server...
Setting up Administration Server Instance...
ERROR: Administration Server configuration failed.
You can now use the console. Here is the command to use to start the
console:
cd /opt/fedora-ds
./startconsole -u admin -a http://fds01.mydomain.tld:55573/
INFO Finished with setup, logfile is setup/setup.log
[root@fds01 ~]#
------------------------------------------------------------------------
--
I am a bit troubled by the errors it reports. Also, "fds01.mydomain.tld"
is in DNS correctly. Also, nothing is listening on port 55573 as it
tells me to connect the console to.
I also am not using the default Java that comes with CentOS 4.3. I
downloaded and installed IBMJava2 1.4.2 and am running it. I could not
use the bundled CentOS4.3 Java as it would not run the console
application.
Can someone please help, I am not sure where to go next.
Thanks,
James T. Richardson, Jr.
jrichardson(a)x-iss.com
eXcellence in IS Solutions, Inc.
Office: 713-862-9200 x226
NOTICE:
This message may contain privileged or otherwise confidential information. If you are not the intended recipient, please immediately advise the sender by reply email and delete the message and any attachments without using, copying or disclosing the contents.
17 years, 7 months
[Fedora-directory-users] uninstall
by devel - Fashion Content
The server installation worked fine, except I need to use a different
hostname.
But the DS admin is now configured with the old hostname, and trying to
figure out how to
hack it with ldapmodify seems too much time wasted. So I am trying to
uninstall.
rpm -e fedora-ds-1.0.2-1.Linux ......... hangs
./uninstall -s -u admin ...... hangs
So how to I get rid of the bloody thing and start installation over?
Henrik
17 years, 7 months
[Fedora-directory-users] Cant start console
by devel - Fashion Content
I have installed 1.02 on FC5.
I have gotten as far a running startconsole after starting sldapd & admin-serv.
When I try to log in it sais the url is wrong or the server isnt started.
The documentation recommends recompiling apache2 in order to get workers,
but that seems so braindead that I just ignored it and selected the default FC5 apache2.2
Is that the cause?
I have changed the hostname, I suppose that is a more likely cause !?
Henrik
17 years, 7 months
RE: [Fedora-directory-users] [FDS] Error: Cannot connect to the AdminServer
by kenwood
Jorge,
Did you start the other services?
/opt/fedora-ds
./slapd-slapd-what-you-named-it
./start-admin
Then try to start your console.
Ken Wood
TLW Sports Company, LLC
Information Systems
p. 805.987.2255
c. 720.937.8295
________________________________
From: fedora-directory-users-bounces(a)redhat.com
[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Jorge
Santos
Sent: Monday, August 28, 2006 12:31 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] [FDS] Error: Cannot connect to the
AdminServer
It's not working yet!!!
I ran it as follow:
# ./startconsole -D -u admin -a http://localhost:1600/
Fedora-Management-Console/1.0 B2006.060.1930
CommManager> New CommRecord (
http://localhost:1600/admin-serv/authenticate)
and when I put the password for user "admin" and I got this message:
Cannot connect to the Admin Server " http://localhost:1600/"
The url is not correct or the server is not running!!!
The log's file (/opt/fedora-ds/admin-serv/logs/error) is:
[Mon Aug 28 15:37:59 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 28 15:38:05 2006] [notice] Access Host filter is: *
[Mon Aug 28 15:38:05 2006] [notice] Access Address filter is: *
[Mon Aug 28 15:38:06 2006] [notice] Access Host filter is: *
[Mon Aug 28 15:38:06 2006] [notice] Access Address filter is: *
[Mon Aug 28 15:38:06 2006] [notice] Apache/2.0 configured -- resuming
normal operations
I don't understand what is happening!!!
Jorge Santos
On 8/28/06, Richard Megginson <rmeggins(a)redhat.com> wrote:
Jorge Santos wrote:
> Hi There,
> I need a help about fds running.
> i did the download of fedora-ds-1.0.2-1.FC4.i386.opt.rpm package and i
> follow the instructions in
> http://directory.fedora.redhat.com/wiki/Setup#Running_Setup
> but, when i tried to execute the command:
> # ServerRoot/startconsole -u admin -a http://localhost:1500
> the console openned and after i put my password which was configured
> during installation. But, the follow message is always returned:
> Cannot connect to the Admin Server " http://localhost:1500
<http://localhost:1500> " The url is
> not correct or the server is not running.
> I'd executed the follow tests:
> Open my browser and put the url "http://localhost:1500 " and the
> page of Fedora Management Console was openned
> execute the command telnet: telnet localhost 1500 and the follow
> message was returned Connected to localhost.localdomain ( 127.0.0.1
<http://127.0.0.1>
> <http://127.0.0.1>)
>
> anybody have the some problem???
> I'm using the FCS4
try startconsole -D
>
> att,
> Jorge Santos
>
>
>
------------------------------------------------------------------------
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
17 years, 7 months
[Fedora-directory-users] Re: Memory leak in FDS?
by Philip Kime
> The new nss files fixed the issue for me, I've had several million
> operations and memory use has stayed steady. I'll keep an eye
open...
Well, it's interesting - it's certainly better than it was but memory
use is rising almost monotonically - it levelled out at about 245Mb for
a while (several days) and is now at almost 300Mb after another few days
- this may well just be increased traffic though. I think it probably is
fixed to be honest. The leak just masked the normal memory usage
patterns.
17 years, 7 months
[Fedora-directory-users] timelimits and timeouts
by Robert Viduya
I've just set up a couple of directory servers in multi-master mode.
I've installed fedora-ds-1.0.2-1.RHEL4.x86_64 on RHEL AS 4.
Occasionally, some of our searches have been failing a timeout error
(err=3) despite not taking any time at all (etime=0). It's not
consistent either; repeat the exact same search again and it succeeds.
The dn we are binding to has an "nstimelimit" attribute set to "-1",
so that shouldn't be an issue.
I tried to set the "nsslapd-timelimit" to "-1" in the dse.ldif file (as
documented in the Configuration, Command and File Reference manual) and
got the following error when I tried to start up the server:
dse - The entry cn=config in file /opt/fedora-ds/slapd-connie/config/dse.ldif is invalid, error code 1 (Operations error) - nsslapd-timelimit: invalid value "-1", time limit must range from 0 to -1
Trying to set it from the java console reports the exact same error.
There doesn't seem to be a way to set unlimited timelimits.
Has anyone else noticed either of these 2 issues? Timelimit errors with
0 elapsed time and inability to set an unlimited timelimit for the
entire server?
--
Robert T. Viduya robert(a)shangri-la.ts.gatech.edu
Office of Information Technology
Georgia Institute of Technology
17 years, 7 months
