389-users January 2011

389-users@lists.fedoraproject.org

42 participants
45 discussions

Newly added users not showing up in DS
by harry.devine＠faa.gov 18 Jan '11

18 Jan '11

I am trying to add a few new users to my directory server, but after I add them, they don't show up under the Directory tab. I've pressed "Refresh All" a few times, and they don't show up. If I try to add them again (in case it didn't "take" the first time), I get an error saying that the user already exists. I looked at the logs but didn't see any errors, and restarting both the dirsrv and dirsrv-admin services didn't help. Any ideas? My 389-ds is version 1.2.1 and 389-ds-base is 1.2.7.5. Thanks! Harry Harry Devine Common ARTS Software Development AJT-144 (609)485-4218 Harry.Devine(a)faa.gov

2 5

CentOS 4.x
by Techie 18 Jan '11

18 Jan '11

Hi, Is there any chance that 389-ds will run on Cent-OS 4.x? Thank you

2 1

schema for dns
by Christopher Wood 17 Jan '11

17 Jan '11

Questions: When was the dNSDomain schema deprecated in 389 DS? Why was it deprecated in 389 DS? What schema do 389 Directory Server or Red Hat Directory Server users customarily use to store DNS zones in their directories? (Am I asking the right questions?) As well, my thanks to the list denizens for your collective threads, you're all terribly educational. Background: The task is exploring DNS schema storage in ldap, to be a DNS server backend. I can get the schema into 389 DS without any issues. I'm asking more for the "why" not the "how". So far everything is working out, but I'm concerned that I may have a blind spot in choice of schema. Am I going one way while the world goes another as far as ldap backend is concerned? The PowerDNS LDAP Backend specifies the dNSDomain2 schema, a child of the dNSDomain schema. http://www.linuxnetworks.de/doc/index.php/PowerDNS_ldapbackend Here is previous discussion on this: http://lists.fedoraproject.org/pipermail/389-users/2010-March/011146.html In 2007 this was apparently added to the fedora-ds schema, if I'm reading it right: https://bugzilla.redhat.com/show_bug.cgi?id=179956 An earlier email which discusses the issue and why it may have appeared in 2005: http://lists.fedoraproject.org/pipermail/389-users/2005-July/000520.html

1 0

Replication
by harry.devine＠faa.gov 15 Jan '11

15 Jan '11

6 13

Re: [389-users] New 389 ds install - cannot logon to adm console
by trisooma 15 Jan '11

15 Jan '11

If i am reading the code correctly (and looking at the logging below), the line that has a severity of 'crit' should dump info for the ldap server we are connecting to. In my case (and Eric's too) only 'ldap://:389' is printed; sometimes even with an odd number like 23395496 (see Eric's first post). [Tue Nov 30 22:01:43 2010] [crit] openLDAPConnection(): util_ldap_init failed for ldap://:389 [Tue Nov 30 22:01:43 2010] [warn] Unable to open initial LDAPConnection to populate LocalAdmin tasks into cache. [Tue Nov 30 22:01:44 2010] [notice] Apache/2.2.17 (Unix) configured -- resuming normal operations [Tue Nov 30 22:01:44 2010] [crit] openLDAPConnection(): util_ldap_init failed for ldap://:389 [Tue Nov 30 22:01:44 2010] [warn] Unable to open initial LDAPConnection to populate LocalAdmin tasks into cache. The code that logs this error looks like this [mod_admserv/mod_admserv.c:517] ap_log_error(APLOG_MARK, APLOG_CRIT, 0 /* status */, NULL, "openLDAPConnection(): util_ldap_init failed for ldap%s://%s:%d", data->secure ? "s" : "", data->host, data->port); It seems that the struct 'data' is not filled with the correct values. BTW. this code was taken from 389-admin-1.1.12.a2 I hope this helps, Regards, Trisooma

4 9

Can't access the management console
by Martial TADJO 13 Jan '11

13 Jan '11

Hi all, Since i have modified the FQDN of my 389-Directory Server into some configuration files (/etc/dirsrv/admin-serv/local.conf, ), I can't login in te management console. When I try to access, I have the following error "Cannot connect to the Admin Server "http://elephant.lspm.intra:9830/" The URL is not correct or the server in not running". I have checked, and my both servers are running (dirsrv and dirsrv-admin). Please can you tell me what to do to get access in the management console ? Thanks. --------------- Elie MABO Skype: mabo.elie.tic | ICQ: 466302400 | YMS: mtadjo

1 0

Windows Sync
by Diego Woitasen 13 Jan '11

13 Jan '11

Hi, I'm configuring Windows Sync between 389 DS 1.2.7.5 and AD Windows 2008. I have everything configured I think but when I start a "full sync" it fails with the error: Total update abortedSystem error. Error Code: -1 The error log (with debug enabled) has these lines: [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - Beginning total update of replica "agmt="cn=Windows Sync" (dc01:389)". [11/Jan/2011:21:44:11 -0300] - Calling dirsync search request plugin [11/Jan/2011:21:44:11 -0300] - Sending dirsync search request [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry matching AD entry [DC=bs,DC=mrec,DC=ar] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry by guid [d18a3aa5cf087c44aa2efe900e50f08a] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: problem looking for guid: -1 [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: AD entry has no username! [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: CN=Configuration,DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry matching AD entry [CN=Configuration,DC=bs,DC=mrec,DC=ar] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry by guid [f1648b22298c154c8e8034a1c76c8643] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: problem looking for guid: -1 [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: AD entry has no username! [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: CN=LostAndFound,DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry matching AD entry [CN=LostAndFound,DC=bs,DC=mrec,DC=ar] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry by guid [d8d2f55128b8e34cabd9a40bfd55c9e7] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: problem looking for guid: -1 [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: AD entry has no username! [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: CN=Deleted Objects,DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): windows_process_dirsync_entry: failed to map tombstone dn. [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: CN=Users,DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry matching AD entry [CN=Users,DC=bs,DC=mrec,DC=ar] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry by guid [e29cfe66f8a6bc4fb2839e757beb9d3e] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: problem looking for guid: -1 [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: AD entry has no username! [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - received entry from dirsync: CN=Computers,DC=bs,DC=mrec,DC=ar [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry matching AD entry [CN=Computers,DC=bs,DC=mrec,DC=ar] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: looking for local entry by guid [8fb08e3ecfdde94290f783402518225c] [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: problem looking for guid: -1 [11/Jan/2011:21:44:11 -0300] NSMMReplicationPlugin - agmt="cn=Windows Sync" (dc01:389): map_entry_dn_inbound: AD entry has no username! Config parameters from dse.ldif: dn: cn=Windows Sync,cn=replica,cn=dc\3Dblabla\2Cdc\3Dar,cn=mapping tree,cn=confi g objectClass: top objectClass: nsDSWindowsReplicationAgreement description: AD cn: Windows Sync nsds7WindowsReplicaSubtree: ou=People,dc=bs,dc=blabla,dc=ar nsds7DirectoryReplicaSubtree: ou=People, dc=blabla,dc=ar nsds7NewWinUserSyncEnabled: on nsds7NewWinGroupSyncEnabled: on nsds7WindowsDomain: bs.blabla.ar nsDS5ReplicaRoot: dc=blabla,dc=ar nsDS5ReplicaHost: dc01.bs.blabla.ar nsDS5ReplicaPort: 389 nsDS5ReplicaBindDN: CN=sync,CN=Users,Dc=bs,DC=blabla,DC=ar nsDS5ReplicaTransportInfo: TLS nsDS5ReplicaBindMethod: SIMPLE nsDS5ReplicaCredentials: {DES}XXXXXXXXXXXX Regards, Diego -- Diego Woitasen

1 2

389-admin-1.1.14: no tarballs available
by Fabio Erculiani 11 Jan '11

11 Jan '11

I see that 1.1.14 has been tagged 4 days ago, but still no tarballs at: http://directory.fedoraproject.org/sources/ Regards, -- Fabio Erculiani http://lxnay.com

2 1

CoS and language codes
by Deyan Stoykov 11 Jan '11

11 Jan '11

Hello! I'm implementing CoS for the ou attribute, but it doesn't work when a language code (RFC2596) is included. # ldapsearch -x -y /etc/ldap.secret "cospriority=CIKO Template" -LLL dn: cospriority=CIKO Template,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg ou: CIKO ou;lang-bg:: 0KbQmNCa0J4= cosPriority: CIKO Template objectClass: top objectClass: costemplate objectClass: extensibleobject Expected result: # ldapsearch -x -y /etc/ldap.secret uid=dstoykov ou -LLL dn: uid=dstoykov,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg ou: CIKO ou;lang-bg:: 0KbQmNCa0J4= Actual result: # ldapsearch -x -y /etc/ldap.secret uid=dstoykov ou -LLL dn: uid=dstoykov,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg ou: CIKO I'm running centos-ds-8.1.0-1.el5. Has anyone tried this? Seems like a bug to me. Regards, Deyan -- Deyan Stoykov, dstoykov(a)uni-ruse.bg System administrator University of Ruse

2 7

389-ds-base fails to build with db-5
by Fabio Erculiani 11 Jan '11

11 Jan '11

Hi there, downstream Gentoo here. As the subject says, 389-ds-base fails to build with newer db 5.0. Please see the respective bug (build log attached): https://bugs.gentoo.org/show_bug.cgi?id=351360 Regards, -- Fabio Erculiani http://lxnay.com

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users January 2011