389-users September 2008

389-users@lists.fedoraproject.org

39 participants
43 discussions

[Fedora-directory-users] setup-ds-admin.pl issue?
by Jerome Yanga 23 Sep '08

23 Sep '08

Thank you, Thomas and Rich, for the quick response. Changing the ownership of /var/run/dirsrv worked like a charm. Regards, Jerome -----Original Message----- From: Jerome Yanga Sent: Monday, September 22, 2008 12:27 PM To: 'fedora-directory-users(a)redhat.com' Subject: setup-ds-admin.pl issue? Fedora Directory Server 1.1.2 seems to have a broken setup-ds-admin.pl. Is anybody else getting the same error below? I have tried Express, Typical and Custom setup types and all of them give me this error. I have even rebuilt the server and started from scratch. The console gives me the following messages... "Creating directory server . . . Server failed to start !!! Please check errors log for problems Possible timeout starting server: timeout=1222110628 now=1222110629 Could not start the directory server using command '/usr/lib/dirsrv/slapd-basis/start-slapd'. The last line from the error log was '[22/Sep/2008:12:00:29 -0700] - Fedora-Directory/1.1.2 B2008.248.1448 starting up '. Error: Unknown error 256 Error: Could not create directory server instance 'instance_name'. Exiting . . ." The setup log shows the following... "[08/09/22:12:10:29] - [Setup] Info Could not start the directory server using command '/usr/lib/dirs rv/slapd-basis/start-slapd'. The last line from the error log was '[22/Sep/2008:12:00:29 -0700] - F edora-Directory/1.1.2 B2008.248.1448 starting up '. Error: Unknown error 256 [08/09/22:12:10:29] - [Setup] Fatal Error: Could not create directory server instance 'instance_name'. [08/09/22:12:10:29] - [Setup] Fatal Exiting . . ." FYI, I followed the same procedure and setup answers with Fedora Directory Server 1.1.1 a few weeks ago and it worked. Help. Regards, Jerome

1 0

[Fedora-directory-users] setup-ds-admin.pl issue?
by Jerome Yanga 22 Sep '08

22 Sep '08

Fedora Directory Server 1.1.2 seems to have a broken setup-ds-admin.pl. Is anybody else getting the same error below? I have tried Express, Typical and Custom setup types and all of them give me this error. I have even rebuilt the server and started from scratch. The console gives me the following messages... "Creating directory server . . . Server failed to start !!! Please check errors log for problems Possible timeout starting server: timeout=1222110628 now=1222110629 Could not start the directory server using command '/usr/lib/dirsrv/slapd-basis/start-slapd'. The last line from the error log was '[22/Sep/2008:12:00:29 -0700] - Fedora-Directory/1.1.2 B2008.248.1448 starting up '. Error: Unknown error 256 Error: Could not create directory server instance 'instance_name'. Exiting . . ." The setup log shows the following... "[08/09/22:12:10:29] - [Setup] Info Could not start the directory server using command '/usr/lib/dirs rv/slapd-basis/start-slapd'. The last line from the error log was '[22/Sep/2008:12:00:29 -0700] - F edora-Directory/1.1.2 B2008.248.1448 starting up '. Error: Unknown error 256 [08/09/22:12:10:29] - [Setup] Fatal Error: Could not create directory server instance 'instance_name'. [08/09/22:12:10:29] - [Setup] Fatal Exiting . . ." FYI, I followed the same procedure and setup answers with Fedora Directory Server 1.1.1 a few weeks ago and it worked. Help. Regards, Jerome

3 2

[Fedora-directory-users] add sudorole cause idm-console to crash/hang
by Jan-Frode Myklebust 22 Sep '08

22 Sep '08

I've added the ldif from the sudo source, created an ou=SUDOers, and when I try to add a "sudorole" using the idm-console it causes the console to just hang or crash. fedora-idm-console-1.1.1-1.fc6 just gives me a spinning cursor that never finish, while centos-idm-console-1.0.0-17.el5.centos.4 gives the following traceback. Adding sudorole's using ldapadd works fine. Any ideas what's up with the consoles ? I have no problem adding other kinds of objects. [janfrode@sim2 ~]$ centos-idm-console Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.netscape.admin.dirserv.propedit.DSEntryPanel.createActionPanel(Unknown Source) at com.netscape.admin.dirserv.propedit.DSEntryPanel.<init>(Unknown Source) at com.netscape.admin.dirserv.EntryEditor.doGenericDialog(Unknown Source) at com.netscape.admin.dirserv.EntryEditor.addGeneric(Unknown Source) at com.netscape.admin.dirserv.EntryEditor.createObject(Unknown Source) at com.netscape.admin.dirserv.DSContentPage.actionNewObject(Unknown Source) at com.netscape.admin.dirserv.DSContentPage.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2012) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2335) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:404) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) at javax.swing.AbstractButton.doClick(AbstractButton.java:374) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1688) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1732) at java.awt.Component.processMouseEvent(Component.java:6101) at javax.swing.JComponent.processMouseEvent(JComponent.java:3276) at java.awt.Component.processEvent(Component.java:5866) at java.awt.Container.processEvent(Container.java:2105) at java.awt.Component.dispatchEventImpl(Component.java:4462) at java.awt.Container.dispatchEventImpl(Container.java:2163) at java.awt.Component.dispatchEvent(Component.java:4288) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4461) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4125) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4055) at java.awt.Container.dispatchEventImpl(Container.java:2149) at java.awt.Window.dispatchEventImpl(Window.java:2478) at java.awt.Component.dispatchEvent(Component.java:4288) at java.awt.EventQueue.dispatchEvent(EventQueue.java:604) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177) at java.awt.EventDispatchThread.run(EventDispatchThread.java:138) -jf

3 7

[Fedora-directory-users] fds 1.1 Performance tuning
by Andreas Kekkou 22 Sep '08

22 Sep '08

Hi all, I have recently upgraded one my fds servers from 1.0.4 to 1.1. The new server has been fine tuned using the performance tuning guide <http://directory.fedoraproject.org/wiki/Performance_Tuning>. At the bottom of the page is mentioning how to change the number of maximum descriptors from 1024 to 8192. There is a note there that this is only valid for 1.0.4 installations and when I tried to change this on 1.1 the server refused to start. The problem is that fds 1.1 stops unexpectedly at irregular intervals with nothing on the logs that can help resolve the problem. I remember a similar problem on my 1.0.4 installation was solved by changing nss-descriptors from 1024 to 8192. Is there any way to increase this number on 1.1? Andreas

2 2

[Fedora-directory-users] Warning with vlvindex....
by Reinhard Nappert 19 Sep '08

19 Sep '08

Hi, I built FDS 1.1.2 from scratch and installed and configured it. I get the following warning, when I run a vlvindex. This used to run in any 1.0.x and 1.1.0 release. [18/Sep/2008:12:20:18 -0400] - warning: ancestorid not indexed on 1 [18/Sep/2008:12:20:18 -0400] - userRoot: WARNING: Failed to fetch subtree lists: (-30990) DB_NOTFOUND: No matching key/data pair found [18/Sep/2008:12:20:18 -0400] - userRoot: Possibly the entrydn or ancestorid index is corrupted or does not exist. [18/Sep/2008:12:20:18 -0400] - userRoot: Attempting brute-force method instead. [18/Sep/2008:12:20:18 -0400] - userRoot: Finished indexing. Dows anybody has an idea? Thanks, -Reinhard

2 7

[Fedora-directory-users] Problems installing on FC9
by David Carter 18 Sep '08

18 Sep '08

When I run either setup-ds.pl or setup-ds-admin.pl, I go through all the prompts and get an error saying it's unable to start the server and that I should check the error logs. Here's the contents of the error log: [18/Sep/2008:11:46:35 -021800] - dblayer_instance_start: pagesize: 4096, pages: 128743, procpages: 7693 [18/Sep/2008:11:46:36 -021800] - cache autosizing: import cache: 204800k [18/Sep/2008:11:46:36 -021800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096 [18/Sep/2008:11:46:36 -021800] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database [18/Sep/2008:11:46:36 -021800] - dblayer_instance_start: pagesize: 4096, pages: 128743, procpages: 7693 [18/Sep/2008:11:46:36 -021800] - cache autosizing: import cache: 204800k [18/Sep/2008:11:46:36 -021800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096 [18/Sep/2008:11:46:36 -021800] - import userRoot: Beginning import job... [18/Sep/2008:11:46:36 -021800] - import userRoot: Index buffering enabled with bucket size 100 [18/Sep/2008:11:46:36 -021800] - import userRoot: Processing file "/ tmp/ldif20a8Hl.ldif" [18/Sep/2008:11:46:36 -021800] - import userRoot: Finished scanning file "/tmp/ldif20a8Hl.ldif" (9 entries) [18/Sep/2008:11:46:37 -021800] - import userRoot: Workers finished; cleaning up... [18/Sep/2008:11:46:37 -021800] - import userRoot: Workers cleaned up. [18/Sep/2008:11:46:37 -021800] - import userRoot: Cleaning up producer thread... [18/Sep/2008:11:46:37 -021800] - import userRoot: Indexing complete. Post-processing... [18/Sep/2008:11:46:37 -021800] - import userRoot: Flushing caches... [18/Sep/2008:11:46:37 -021800] - import userRoot: Closing files... [18/Sep/2008:11:46:37 -021800] - All database threads now stopped [18/Sep/2008:11:46:37 -021800] - import userRoot: Import complete. Processed 9 entries in 1 seconds. (9.00 entries/sec) [18/Sep/2008:11:46:38 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up [18/Sep/2008:11:48:06 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up [18/Sep/2008:11:52:46 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up [18/Sep/2008:11:53:31 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up [18/Sep/2008:12:06:02 -021800] - dblayer_instance_start: pagesize: 4096, pages: 128743, procpages: 7693 [18/Sep/2008:12:06:02 -021800] - cache autosizing: import cache: 204800k [18/Sep/2008:12:06:02 -021800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096 [18/Sep/2008:12:06:02 -021800] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database [18/Sep/2008:12:06:02 -021800] - dblayer_instance_start: pagesize: 4096, pages: 128743, procpages: 7693 [18/Sep/2008:12:06:02 -021800] - cache autosizing: import cache: 204800k [18/Sep/2008:12:06:02 -021800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096 [18/Sep/2008:12:06:03 -021800] - import userRoot: Beginning import job... [18/Sep/2008:12:06:03 -021800] - import userRoot: Index buffering enabled with bucket size 100 [18/Sep/2008:12:06:03 -021800] - import userRoot: Processing file "/ tmp/ldif8U2ox1.ldif" [18/Sep/2008:12:06:03 -021800] - import userRoot: Finished scanning file "/tmp/ldif8U2ox1.ldif" (9 entries) [18/Sep/2008:12:06:04 -021800] - import userRoot: Workers finished; cleaning up... [18/Sep/2008:12:06:04 -021800] - import userRoot: Workers cleaned up. [18/Sep/2008:12:06:04 -021800] - import userRoot: Cleaning up producer thread... [18/Sep/2008:12:06:04 -021800] - import userRoot: Indexing complete. Post-processing... [18/Sep/2008:12:06:04 -021800] - import userRoot: Flushing caches... [18/Sep/2008:12:06:04 -021800] - import userRoot: Closing files... [18/Sep/2008:12:06:04 -021800] - All database threads now stopped [18/Sep/2008:12:06:04 -021800] - import userRoot: Import complete. Processed 9 entries in 1 seconds. (9.00 entries/sec) [18/Sep/2008:12:06:04 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up It seems to think we've started. Not a lot of help. So I run 'sevice dirsrv start', which fails. The only new line in the error log is: [18/Sep/2008:13:20:57 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up Again, not much help. So I changed the debug level by modifying the startup script and adding a -d option to the ns-slapd command. When I try to start from the command line, I get this: Starting dirsrv: ldap...[18/Sep/2008:13:57:33 -021800] Fedora-Directory/1.1.2 - debug level: accesscontrol (128) [18/Sep/2008:13:57:33 -021800] - Fedora-Directory/1.1.2 B2008.248.1443 starting up Failed to open stats file (/var/run/dirsrv/slapd-ldap.stats) (error 1). [FAILED] *** Warning: 1 instance(s) failed to start Finally, something helpful! First, why isn't this going to the error log? Second, and most importantly, what do I do about it? I don't know if it's trying to read the file, write the file, do it as root, or as nobody. I turned selinux off just to be sure that isn't the issue, but I'd prefer to run with it on. It's a fresh FC9 install, with all patches applied. TIA, Dave

4 3

[Fedora-directory-users] Synchronization
by Groot, Mathijs de (IDT Competence Java) 18 Sep '08

18 Sep '08

Hi All, I have a synchronization set up between a Red Hat Directory Server 8 and a test Windows 2003 server with Active Directory. Is it possible to test up a one-way synchronization from Active Directory to Red Hat DS? If changes are made on the Red Hat Directory Server they must never be synchronized back to the Windows Active Directory. It will be no problem if those changes made in the RedHat DS are overwritten with the next sync from Windows AD. The Red Hat Directory Server is not a exact copy of the Windows Active Directory, the Windows AD just syncs with a sub tree in the RedHat DS, other sub trees will contain other entries or will be set up with other synchronizations. Thanks, Mathijs de Groot 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.

1 0

[Fedora-directory-users] Group based access control
by Kwan Lowe 17 Sep '08

17 Sep '08

Hello All: I am in the process of migrating from OpenLDAP to Fedora Directory Server. Actually most of my testing has been with the RH/CentOS spins, but it appears to be very similar. So far I've gotten the main things working: 1) Host based access via AuthorizedHost 2) Service based access via AuthorizedService 3) AIX/Linux <-> LDAP 4) PosixGroup support The one thing I would like is to have group based host access control. E.g., I would like to define a new LDAP group (say, DBA-Production) that includes a bunch of host entries. When needed, I could add a user to the DBA-Production group and automatically give him/her access to the list of defined hosts. Anyone have suggestions on how to approach this? Thanks, Kwan

2 2

[Fedora-directory-users] Upgrade MMR from 1.0.4 to 1.1.0
by Reinhard Nappert 17 Sep '08

17 Sep '08

Hi all, I have an MMR setup, working fine with 1.0.4. When I upgrade (migrate) both servers to 1.1.0, the replica entry and the agreement object within dse.ldif still look fine, but I get the following messages in errors: [17/Sep/2008:11:45:11 -0400] NSMMReplicationPlugin - agmt="cn=srv12srv2" (srv2:389): Incremental update failed and requires administrator action [17/Sep/2008:11:46:05 -0400] NSMMReplicationPlugin - conn=96 op=3 replica="o=UMC ": Unable to acquire replica: error: duplicate replica ID detected On both servers. Again, the ReplicaId are different on both boxes: nsDS5ReplicaId: 1 nsDS5ReplicaId: 2 To make matters worse, just disabling replication on both boxes and enabling it afterwards does not fix the issue. It looks like that only exporting the db, getting rid of the directory instances on both boxes, setup the instance from scratch and importing the data and setting up replication agreement makes it work again. Did anybody encounter this issue? If so, is there a possibility to fix it without reloading the data from scratch. Thanks, -Reinhard

2 4

[Fedora-directory-users] CVS commits mailing list
by Andrey Ivanov 17 Sep '08

17 Sep '08

Hi, the mailing list of the fds cvs commits (fedora-directory-commits(a)redhat.com) does not seem to have any commits to cvs since ~ one month. Does it mean that this list is no longer supported or there was really absolutely no changes in the cvs of FDS during the last month?? Andrey Ivanov tel +33-(0)1-69-33-99-24 fax +33-(0)1-69-33-99-55 Direction des Systèmes d'Information Ecole Polytechnique 91128 Palaiseau CEDEX France

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users September 2008