Re: [Fedora-directory-users] Difficulties with fedora-idm-console
by leonhardt@hawaii.rr.com
Hi Benny, thanks for responding
---- Benny Chee <chee.benny(a)gmail.com> wrote:
> hi,
> Login username should be "admin".
Tried that first, actually...then tried the cn=Directory Manager after reading this: http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Introduction_to_RHDS...
What hostname was given to your ldap
> directory server?
should be 'server'. hostname returns "server.leonhardt.lan" I'm running my own DNS on this box...
Try putting a hostname to your interface IP address inside
> /etc/hosts and try again.
I'm attaching my /etc/hosts, below are the contents of my install log (sorry crappy rr webmail wouldn't attach):
Thanks again for helping me with this.
Matt
[root@server tmp]# cat setupIx15Y1.log
[08/01/16:20:21:47] - [Setup] Info This program will set up the Fedora Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
[08/01/16:20:21:47] - [Setup] Info Would you like to continue with set up?
[08/01/16:20:21:47] - [Setup] Info yes
[08/01/16:20:21:47] - [Setup] Info BY SETTING UP AND USING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY
AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE
LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS
OF THIS AGREEMENT, PLEASE DO NOT SET UP OR USE THIS SOFTWARE.
[08/01/16:20:21:47] - [Setup] Info Do you agree to the license terms?
[08/01/16:20:21:51] - [Setup] Info yes
[08/01/16:20:21:51] - [Setup] Info Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
Fedora Directory Server system tuning analysis version 10-AUGUST-2007.
NOTICE : System is i686-unknown-linux2.6.23.9-85.fc8 (1 processor).
WARNING: 503MB of physical memory is available on the system. 1024MB is recommended for best performance on large production system.
NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes). This may cause temporary server congestion from lost
client connections.
WARNING: There are only 1024 file descriptors (hard limit) available, which
limit the number of simultaneous connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
[08/01/16:20:21:51] - [Setup] Info Would you like to continue?
[08/01/16:20:21:53] - [Setup] Info yes
[08/01/16:20:21:53] - [Setup] Info Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
[08/01/16:20:21:53] - [Setup] Info Choose a setup type
[08/01/16:20:21:55] - [Setup] Info 2
[08/01/16:20:21:55] - [Setup] Info Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
[08/01/16:20:21:55] - [Setup] Info Computer name
[08/01/16:20:22:05] - [Setup] Info server.leonhardt.lan
[08/01/16:20:22:05] - [Setup] Info The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
[08/01/16:20:22:05] - [Setup] Info System User
[08/01/16:20:22:07] - [Setup] Info nobody
[08/01/16:20:22:07] - [Setup] Info System Group
[08/01/16:20:22:07] - [Setup] Info nobody
[08/01/16:20:22:07] - [Setup] Info Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
<hostname>.<domainname>(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
[08/01/16:20:22:07] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[08/01/16:20:22:14] - [Setup] Info no
[08/01/16:20:22:14] - [Setup] Info Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
[08/01/16:20:22:14] - [Setup] Info Configuration directory server
administrator ID
[08/01/16:20:22:15] - [Setup] Info admin
[08/01/16:20:22:15] - [Setup] Info Password
[08/01/16:20:22:18] - [Setup] Info Password (confirm)
[08/01/16:20:22:20] - [Setup] Info The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
[08/01/16:20:22:20] - [Setup] Info Administration Domain
[08/01/16:20:22:30] - [Setup] Info leonhardt.lan
[08/01/16:20:22:30] - [Setup] Info The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
[08/01/16:20:22:30] - [Setup] Info Directory server network port
[08/01/16:20:22:31] - [Setup] Info 389
[08/01/16:20:22:31] - [Setup] Info Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
[08/01/16:20:22:31] - [Setup] Info Directory server identifier
[08/01/16:20:22:36] - [Setup] Info server
[08/01/16:20:22:36] - [Setup] Info The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
[08/01/16:20:22:36] - [Setup] Info Suffix
[08/01/16:20:22:45] - [Setup] Info dc=leonhardt, dc=lan
[08/01/16:20:22:45] - [Setup] Info Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
[08/01/16:20:22:45] - [Setup] Info Directory Manager DN
[08/01/16:20:22:54] - [Setup] Info cn=Directory Manager
[08/01/16:20:22:54] - [Setup] Info Password
[08/01/16:20:22:59] - [Setup] Warning The password contains invalid characters. Please choose another one.
[08/01/16:20:22:59] - [Setup] Info Password
[08/01/16:20:23:02] - [Setup] Info Password (confirm)
[08/01/16:20:23:05] - [Setup] Info The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
[08/01/16:20:23:05] - [Setup] Info Administration port
[08/01/16:20:23:08] - [Setup] Info 9830
[08/01/16:20:23:08] - [Setup] Info The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
[08/01/16:20:23:08] - [Setup] Info Are you ready to set up your servers?
[08/01/16:20:23:12] - [Setup] Info yes
[08/01/16:20:23:12] - [Setup] Info Creating directory server . . .
[08/01/16:20:23:18] - [Setup] Info Your new DS instance 'server' was successfully created.
[08/01/16:20:23:18] - [Setup] Info Creating the configuration directory server . . .
[08/01/16:20:23:21] - [Setup] Info Beginning Admin Server creation . . .
[08/01/16:20:23:21] - [Setup] Info Creating Admin Server files and directories . . .
[08/01/16:20:23:21] - [Setup] Info Updating adm.conf . . .
[08/01/16:20:23:21] - [Setup] Info Updating admpw . . .
[08/01/16:20:23:21] - [Setup] Info Registering admin server with the configuration directory server . . .
[08/01/16:20:23:22] - [Setup] Info Updating adm.conf with information from configuration directory server . . .
[08/01/16:20:23:22] - [Setup] Info Updating the configuration for the httpd engine . . .
[08/01/16:20:23:22] - [Setup] Info Starting admin server . . .
[08/01/16:20:23:23] - [Setup] Info The admin server was successfully started.
[08/01/16:20:23:23] - [Setup] Info Admin server was successfully created, configured, and started.
[08/01/16:20:23:23] - [Setup] Success Exiting . . .
Log file is '/tmp/setupIx15Y1.log'
> benny
>
> On 19/01/2008, leonhardt(a)hawaii.rr.com <leonhardt(a)hawaii.rr.com> wrote:
> >
> > Hi everyone...I'm new to LDAP and FDS, so please bear with me.
> >
> > I just install FDS 1.1 on a clean F8 box. I got through the setup scripts
> > but when I launch fedora-idm-console, and enter my login info I keep getting
> > an Error 400 response. My login looks like this:
> >
> > User ID: cn=Directory Manager
> > Password: ********
> > Administration URL: http://localhost:9830
> >
> > I've tried all kinds of variations, username w/o the "cn=", logging in as
> > "admin", and every variation of IP/partially/fully-qualified domain name I
> > could think of for the box. I've also tried running with '-a' (it didn't
> > recognize the -d option, recommended to me by someone in the #fedora-ds
> > room). This is my error, no matter what I do:
> >
> > Can't logon because of an incorrect User ID,
> > Incorrect password or Directory problem.
> > HttpException:
> > Response: HTTP/1.1 400 Bad Request
> > Status: 400
> > URL: http:/admin-serv/authenticate
> >
> > This last line bothers me...it looks as if the console is not even trying
> > to pass the login info to a valid URL! If I just point my browser at
> > http://localhost:9830/ I get the HTML back-end and can authenticate there
> > to get into the "Adminsitration Express" tool, so I'm fairly convinced I'm
> > using the correct login info...
> >
> > I's confused...
> >
> > Matt
> >
> > --
> > Fedora-directory-users mailing list
> > Fedora-directory-users(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-directory-users
> >
16 years, 2 months
[Fedora-directory-users] So I have a Samba PDC + FDS, What now?
by Gary Martin
I have successfully completed the Howto:Samba documentation. I think
I have a working Samba PDC with a FDS backend. I can add users with
smbpasswd -a. The problem I have is connecting a windows workstation
to the domain. The connection fails complaining about the user name
or password. What user should I be using to add workstations to the
domain, a member of the 'Domain Admins' or the Administrator user? I
have tried both and neither seem to work. Thanks.
16 years, 2 months
[Fedora-directory-users] FDS config problem with GSSAPI: No such file or directory
by Charles Hymes
Hi folks,
I'm having a real hard time debugging this.
I'm trying to do a new Fedora Directory Server+kerberos install , on a new
Fedora 7 box. I can kinit, but I can't get ldapsearch or ldapwhoami to work
locally. I thought it was a read problem with the keytab files, but I tried
setting KRB5_KTNAME to a keytab file I knew ware readable by slapd, and that
did not help. I also checked permissions on my certificates, and that seems
OK too. ldapsearch -x does work, but ldapsearch -Y GSSAPI does not.
I tried running strace on ldapwhoami, slapd and krb5kdc, but strace does not
show which resource is not accessible. Actually I'm surprised that strace
does not show any attempts to open the keytabs or anything in
/etc/openldap/cacerts...
I tried making briefly making /etc/krb5.keytab world readable, it did not
change the "No such file" error.
The logs I check are /var/log/messages, slapd and krb5kdc.log. The logs do
not show the ldap client error. I DID see some SELINUX errors for
krb5kdc_rcache and krb5.conf, but I ran restorecon and fixed those. This did
not stop the error. I guess I'll try turning SELINUX off, and see if that
makes any difference.
Any help would be greatly appreciated :)
*******************************************
*******************************************
[installer@trixter ~]$ ldapwhoami -V -Y GSSAPI
ldapwhoami: @(#) $OpenLDAP: ldapwhoami 2.3.34 (Nov 2 2007 08:16:20) $
[email]kojibuilder@xenbuilder2.fedora.redhat.com[/email]:/builddir/build/BUI
LD/openldap-2.3.34/openldap-2.3.34/build-clients/clients/tools
(LDAP library: OpenLDAP 20333)
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS
failure. Minor code may provide more information (No such file or directory)
*******************************************
*******************************************
[installer@trixter ~]$ klist
Ticket cache: FILE:/tmp/krb5cc_500
Default principal: [email]installer(a)HYMESRUZICKA.ORG[/email]
Valid starting Expires Service principal
01/15/08 13:11:43 01/16/08 13:11:43 krbtgt/HYMESRUZICKA.ORG(a)HYMESRUZICKA.ORG
01/15/08 13:12:35 01/16/08 13:11:43
ldap/trixter.hymesruzicka.org(a)HYMESRUZICKA.ORG
Kerberos 4 ticket cache: /tmp/tkt500
klist: You have no tickets cached
*******************************************
*******************************************
[installer@trixter ~]$ cat /etc/openldap/ldap.conf # # LDAP Defaults # #
This file should be world readable but not world writable.
BASE dc=hymesruzicka,dc=org
URI ldap://trixter.hymesruzicka.org:11562
ldaps://trixter.hymesruzicka.org:636
TLS_CACERTDIR /etc/openldap/cacerts/
TLS_REQCERT allow
#SIZELIMIT 12
TIMELIMIT 5
#DEREF never
*******************************************
*******************************************
[root@trixter ~]# find / -iname "*keytab*" -ls
49547109 8 -rw-r--r-- 1 root root 712 Jan 15 13:00
/etc/krb5.keytab
49610949 8 -rw-r--r-- 1 fdirsvr fdirsvr 712 Jan 15 13:00
/etc/dirsrv/slapd-trixter/dirsrv.keytab
22746332 8 -rw------- 1 root root 454 Jan 13 10:26
/var/kerberos/krb5kdc/kadm5.keytab
*******************************************
*******************************************
BTW: Here's the command with debug on:
[installer@trixter ~]$ ldapwhoami -V -d 1 -Y GSSAPI
ldapwhoami: @(#) $OpenLDAP: ldapwhoami 2.3.34 (Nov 2 2007 08:16:20) $
[email]kojibuilder@xenbuilder2.fedora.redhat.com[/email]:/builddir/build/BUI
LD/openldap-2.3.34/openldap-2.3.34/build-clients/clients/tools
(LDAP library: OpenLDAP 20333)
ldap_create
ldap_sasl_interactive_bind_s: user selected: GSSAPI
ldap_int_sasl_bind: GSSAPI
ldap_new_connection 1 1 0
ldap_int_open_connection
ldap_connect_to_host: TCP trixter.hymesruzicka.org:11562
ldap_new_socket: 3
ldap_prepare_socket: 3
ldap_connect_to_host: Trying 192.168.0.3:11562
ldap_connect_timeout: fd: 3 tm: -1 async: 0
ldap_int_sasl_open: host=trixter.hymesruzicka.org
SASL/GSSAPI authentication started
ldap_sasl_bind_s
ldap_sasl_bind
ldap_send_initial_request
ldap_send_server_request
ber_scanf fmt ({it) ber:
ber_scanf fmt ({i) ber:
ber_flush: 589 bytes to sd 3
ldap_result ld 0x8d82038 msgid 1
ldap_chkResponseList ld 0x8d82038 msgid 1 all 1
ldap_chkResponseList returns ld 0x8d82038 NULL
wait4msg ld 0x8d82038 msgid 1 (infinite timeout)
wait4msg continue ld 0x8d82038 msgid 1 all 1
** ld 0x8d82038 Connections:
* host: trixter.hymesruzicka.org port: 11562 (default)
refcnt: 2 status: Connected
last used: Wed Jan 16 10:11:11 2008
** ld 0x8d82038 Outstanding Requests:
* msgid 1, origid 1, status InProgress
outstanding referrals 0, parent count 0
** ld 0x8d82038 Response Queue:
Empty
ldap_chkResponseList ld 0x8d82038 msgid 1 all 1
ldap_chkResponseList returns ld 0x8d82038 NULL
ldap_int_select
read1msg: ld 0x8d82038 msgid 1 all 1
ber_get_next
ber_get_next: tag 0x30 len 148 contents:
read1msg: ld 0x8d82038 msgid 1 message type bind
ber_scanf fmt ({eaa) ber:
read1msg: ld 0x8d82038 0 new referrals
read1msg: mark request completed, ld 0x8d82038 msgid 1
request done: ld 0x8d82038 msgid 1
res_errno: 0, res_error: <>, res_matched: <>
ldap_free_request (origid 1, msgid 1)
ldap_free_connection 0 1
ldap_free_connection: refcnt 1
ldap_parse_sasl_bind_result
ber_scanf fmt ({eaa) ber:
ldap_msgfree
ldap_perror
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS
failure. Minor code may provide more information (No such file or directory)
16 years, 2 months
[Fedora-directory-users] Can't open fedora ds with ldapeditor
by todd.hammer@us.atlascopco.com
I have fedora ds running on Redhat 5 and it works great..... as long as I
use the fedora admin tool.
I can't use any other tools to modify the ldap data.
For example, the following will not run:
ldapadd -h 12.34.56.789 -x -D "cn=manager,dc=example,dc=com" -W -f /tmp
/user.ldif (modified actual IP and dn for security)
After giving the correct password, all I get is this:
ldap_bind: No such object (32)
matched DN: dc=acds,dc=com
Any ideas what I've done? This used to work in openldap.
Thanks in advance.
Todd Hammer
Technical Support Analyst
16 years, 2 months
[Fedora-directory-users] Paged Results support?
by Ben
Does FDS support Paged Results?
I ask this because with FDS configured with "nsslapd-sizelimit: 2000"
and a client search configured to return 1000 results per page it
appears that 2000 results are returned and a "Sizelimit exceeded" error
is returned by the server.
Attached is a perl snippet to test paged results.
Thanks,
Ben
use strict;
use Net::LDAP;
use Net::LDAP::Control::Paged;
use Net::LDAP::Constant qw( LDAP_CONTROL_PAGED );
my @server = ( "ldap2.example.com", "ldap3.example.com" );
my $base = "o=Company";
my $filter = "(|(objectClass=posixAccount)(objectClass=posixGroup))";
my $pagesize = 1000;
my $ldap = Net::LDAP->new( \@server, onerror => undef ) || die;
my $mesg = undef;
$mesg = $ldap->start_tls( verify => 'none' ) if $ldap;
$mesg = $ldap->bind(); # anonymous bind
# bind with username and password.
#
# $mesg = $ldap->bind( $userdn, password => $userpassword );
my $page = Net::LDAP::Control::Paged->new( size => $pagesize );
while (1) {
$mesg = $ldap->search(
base => $base,
filter => $filter,
scope => 'sub',
control => [$page],
callback => \&dosomething, # Subroutine to process each entry returned.
);
$mesg->code && die "ERROR: Search " . $base . ":(" . $mesg->error . ") " . $mesg->error;
# Get cookie from paged control
my ($resp) = $mesg->control(LDAP_CONTROL_PAGED) or last;
my $cookie = $resp->cookie or last;
# Set cookie in paged control
$page->cookie($cookie);
}
sub dosomething {
my ( $mesg, $entry ) = @_;
if ( !defined($entry) ) {
return;
}
elsif ( $entry->isa('Net::LDAP::Reference') ) {
return;
}
my @classes = $entry->get_value('objectClass');
if ( grep /organizationalUnit/i, @classes ) {
print $entry->dn() . " is an organizationalUnit.\n";
}
elsif ( grep /computer/i, @classes ) {
print $entry->dn() . " is an computer.\n";
}
elsif ( grep /person/i, @classes ) {
print $entry->dn() . " is an user.\n";
}
elsif ( grep /group/i, @classes ) {
print $entry->dn() . " is an group.\n";
}
else {
print $entry->dn() . " is an unknown type.\n";
print "objectClass: " . join ( ':', @classes ) . "\n";
$entry->dump();
}
}
16 years, 2 months
[Fedora-directory-users] Trouble installing fds on debian 4
by Prigent, Glenn
Hello,
I have trouble installing fds on a debian 4.
The installation complete well but when I start fds I have a exception.
../startconsole -u admin -a http://localhost:64233/
java.lang.ExceptionInInitializerError
caused by java/lang/ArrayIndexOutOfBoundsException:
at
com.netscape.management.client.util.ResourceSet$StackLookup.getLoader
(source file unknown:line unknown, pc 0x85bc45e)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x85bf0e2)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x8589a68)
at com.netscape.management.client.console.Console.<clinit> (source
file unknown:line unknown, pc 0x85ba276)
caused by: java.lang.ArrayIndexOutOfBoundsException
at
com.netscape.management.client.util.ResourceSet$StackLookup.getLoader
(source file unknown:line unknown, pc 0x85bc45e)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x85bf0e2)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x8589a68)
at com.netscape.management.client.console.Console.<clinit> (source
file unknown:line unknown, pc 0x85ba276)
java.lang.ArrayIndexOutOfBoundsException
at
com.netscape.management.client.util.ResourceSet$StackLookup.getLoader
(source file unknown:line unknown, pc 0x85bc45e)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x85bf0e2)
at com.netscape.management.client.util.ResourceSet.<init> (source
file unknown:line unknown, pc 0x8589a68)
at com.netscape.management.client.console.Console.<clinit> (source
file unknown:line unknown, pc 0x85ba276)
Is anyone succeeded installing fds on debian ?
Can anyone help me ?
Thank you.
Glenn Prigent
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
16 years, 2 months
[Fedora-directory-users] RE: Contemplating an upgrade to Fedora DS 1.1
by Jeff Tharp
>Rich Megginson wrote:
>Can you be more specific about your planned deployment? Number of
entries? Average entry size? Search rate? >Update rate? Number of
masters? Total number of replicas? Number and type of clients?
Sorry, I have my list subscription set to digest mode, but I saw that
you sent this question, so I thought I'd respond ahead of actually
receiving the email :-) Let's see...number of entries = 529,809 (I was
a little off in my estimate earlier, it's been a while since I checked
the exact count). Average entry size...not sure exactly how to
calculate this, if you mean by memory size. We maintain 45 attributes
per entry. My particular entry (which could be considered average, I
suppose) is ~4 KB when exported to LDIF.
I'll run some performance monitoring today as far as the number of
search and update operations. We only have two masters, no other
replicas. One master is active and gets all the load, the other is on
standby (via Heartbeat) ready to take over if the first fails. All
requests come from two front-end application servers and one back-end
administration web application. The authentication application always
bind's as the admin user then does a compare on the password hash of a
particular user.
In case you're wondering, current production hardware is a pair of Dell
PowerEdge 2850's, each with 1x3.2 GHz CPU, 2 GB RAM, single RAID 10
array with 15K RPM disks.
One other consideration I want to look into is enabling Berkeley DB
transaction logging--last year we had a power outage that caused the
servers to go down hard (our generator was on the fritz :-P). The
database on both masters was corrupted and had to be restored. I do
nightly backups but lost all the account creations/updates for the day
of the outage. I'd like to setup transaction logs and write these off
to tape or another server so that we can recover to within 30 min to 1
hour of an outage. I looked into this with our current setup, but I
wasn't able to get more than 1 transaction log written per day, which
doesn't help much beyond our current nightly backups.
Thanks for your help,
Jeff Tharp
System Administrator
ESRI - Redlands, CA
http://www.esri.com
> -----Original Message-----
> From: Jeff Tharp
> Sent: Tuesday, January 15, 2008 8:38 PM
> To: 'Fedora-directory-users(a)redhat.com'
> Subject: Contemplating an upgrade to Fedora DS 1.1
>
> I am looking into the feasibility of upgrading the LDAP
> backend used for authentication on many of our web sites
> (roughly 300K users). Currently we are using FedoraDS 1.0.2
> running on RHEL 4 in a multi-master configuration of two
> nodes configured as a high-availability cluster using
> Heartbeat from the Linux-HA project. My underlying database
> is Berkeley DB 4.2.52. My goal would be to upgrade to
> FedoraDS 1.1 running on RHEL 5.1. I have managed to complete
> the initial installation on my test system and so I'm now
> digging into the details of the migration.
>
> Some questions that have come up:
> 1. RHEL5.1 ships with Berkeley DB 4.3 and I noticed a note
> that this has been found subpar for production use in large
> environments. Should I consider reverting back to Berkeley
> DB 4.2.52 or should I look into installing Berkeley DB 4.5 or
> 4.6? If I installed the FedoraDS 1.1 fc6 binary packages, do
> I need to be worried that these were built against a specific
> Berkeley DB version?
>
> 2. Most of the migration notes I see on the site mention
> migrating from 1.0.4 to 1.1. Is it necessary to migrate our
> current 1.0.2 install to 1.0.4 as an intermediate step to
> upgrading to 1.1? Or should the 1.0.4 migration steps be sufficient?
>
> 3. Previously, we had separate physical filesystems for / and
> /opt, so that the directory server files were separated from
> the system files. I understand that in FedoraDS 1.1 the
> decision has been to standardize the pathing so this is no
> longer feasible. If I still wanted at least the
> instance-specific files (or at least the instance-specific
> database files) to be in a separate filesystem, say /data,
> what would be the recommended way of accomplishing this? Or
> should I just go crazy with symbolic links to accomplish the
> structure I want? :-)
>
> I greatly appreciate any advice you can provide regarding
> these questions. I must say that we originally deployed
> FedoraDS 1.0.2 two years ago to replace a much older OpenLDAP
> 2.0 implementation and have generally been happy with both
> its performance and stability.
>
> Thanks,
> Jeff Tharp
> System Administrator
> ESRI - Redlands, CA
> http://www.esri.com
16 years, 2 months
[Fedora-directory-users] Contemplating an upgrade to Fedora DS 1.1
by Jeff Tharp
I am looking into the feasibility of upgrading the LDAP backend used for
authentication on many of our web sites (roughly 300K users). Currently
we are using FedoraDS 1.0.2 running on RHEL 4 in a multi-master
configuration of two nodes configured as a high-availability cluster
using Heartbeat from the Linux-HA project. My underlying database is
Berkeley DB 4.2.52. My goal would be to upgrade to FedoraDS 1.1 running
on RHEL 5.1. I have managed to complete the initial installation on my
test system and so I'm now digging into the details of the migration.
Some questions that have come up:
1. RHEL5.1 ships with Berkeley DB 4.3 and I noticed a note that this has
been found subpar for production use in large environments. Should I
consider reverting back to Berkeley DB 4.2.52 or should I look into
installing Berkeley DB 4.5 or 4.6? If I installed the FedoraDS 1.1 fc6
binary packages, do I need to be worried that these were built against a
specific Berkeley DB version?
2. Most of the migration notes I see on the site mention migrating from
1.0.4 to 1.1. Is it necessary to migrate our current 1.0.2 install to
1.0.4 as an intermediate step to upgrading to 1.1? Or should the 1.0.4
migration steps be sufficient?
3. Previously, we had separate physical filesystems for / and /opt, so
that the directory server files were separated from the system files. I
understand that in FedoraDS 1.1 the decision has been to standardize the
pathing so this is no longer feasible. If I still wanted at least the
instance-specific files (or at least the instance-specific database
files) to be in a separate filesystem, say /data, what would be the
recommended way of accomplishing this? Or should I just go crazy with
symbolic links to accomplish the structure I want? :-)
I greatly appreciate any advice you can provide regarding these
questions. I must say that we originally deployed FedoraDS 1.0.2 two
years ago to replace a much older OpenLDAP 2.0 implementation and have
generally been happy with both its performance and stability.
Thanks,
Jeff Tharp
System Administrator
ESRI - Redlands, CA
http://www.esri.com
16 years, 2 months
[Fedora-directory-users] Setting Up Fedora DS Client on HP Unix ???
by Singh Raina, Ajeet
Hello Guys,
I have been installing fedora DS on RHEL and configuring different
clients like Solaris 10,9,8 and they seem to work fine.
But I couldn't get docs related to Setting Up Fedora DS on HP-Unix.Can
you please let me how we can go for it??
Thanks in Advance,
Ajeet
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
16 years, 2 months