389-users January 2012

389-users@lists.fedoraproject.org

20 participants
24 discussions

Wiki/FireFox 9.0 problem
by Ivanov Andrey (M.) 04 Jan '12

04 Jan '12

Hi, looks like the current wiki code has a problem with FireFox 9.0, the menu is displayed under the main content div. It seems ( http://support.mozilla.org/en-US/questions/906789#answer-290813 or http://forums.mozillazine.org/viewtopic.php?f=25&t=2392487) like a browser sniffing problem in wiki javascript code: This is caused by browser sniffing that has been broken in Firefox 9. The property navigator.taintEnabled is no longer supported so the wrong css file gets loaded which sets the margin-left of the div column-content to zero. As a result there is less room for the navigation div which is pushed down. Don't know whether FireFox devs will get back the navigator.taintEnabled property or the wiki code base should be patched... The same problem appears on a lot of other wiki sites (including, for example, http://k5wiki.kerberos.org) @+

2 2

Announcing 389 bugzilla is moving to 389 trac
by Rich Megginson 04 Jan '12

04 Jan '12

The 389 team will be switching to trac for keeping track of bugs/enhancement requests/issues instead of Red Hat Bugzilla. * Why? We needed a clear separation between "upstream" 389 development and "downstream" Red Hat product/process. It was getting too confusing using bugzilla for both upstream and downstream. We needed an issue tracking tool that was focused only on the upstream 389. Most of the other related groups such as freeipa, sssd, dogtag, and others have already moved to use trac. * What happens to 389 bugs in bugzilla? Nothing. They are still there. You can continue to use bugzilla. All of the open issues have been copied to trac. You can still use bugzilla to refer to the older issues. We have an internal tool we use that links bugzilla bugs to trac so we can find "unlinked" bugs/tickets and create links, copy bugs, etc. * What if I find an issue with a particular Fedora/EPEL release? Go ahead and file the bug in bugzilla against Product: Fedora or Fedora EPEL and Component: 389-ds-base (or whatever component). The 389 development team will triage the bug. If it affects upstream, we will copy it into a trac ticket. When we fix the bug and push out a package containing the fix, we will update the bugzilla bug, so if you don't care about what happens in the upstream, you don't have to worry about it. You can just pay attention to the bugzilla Fedora/EPEL bug and find out when a package containing the fix is released. * Where is the new trac? https://fedorahosted.org/389 * How do I see the tickets? https://fedorahosted.org/389/report - there are various reports to see tickets * How do I file a new ticket, or add myself to the CC list of an existing ticket? You must first have a Fedora Account - see https://admin.fedoraproject.org/accounts/ Once you login, you should see a link for New Ticket, and you should be able to modify/add comments to existing tickets.

1 0

bak2db restore got stuck in infinite loop
by Groten, Ryan 04 Jan '12

04 Jan '12

Hi everyone, In my environment I have a total of 4 directory servers, 2 multi-masters in production (ServerA, ServerB) and 2 multi-masters to test with (ServerC, ServerD). Basically here's what I did: 1. Took a backup of one of the production directory servers, ServerA 2. Copied ServerA's backup to ServerC (test). 3. Deleted the replication agreement on ServerC to ServerD (but not the agreement from ServerD to ServerC) 4. Ran /usr/lib64/dirsrv/slapd-ServerC/bak2db 2011_12_29_15_27_35 The restore started, and never stopped running. I eventually killed it and tried again, this time capturing the output: # /usr/lib64/dirsrv/slapd-ServerC/bak2db 2011_12_29_15_27_35 [03/Jan/2012:15:06:43 -0700] 389-Directory/1.2.9.9 - debug level: backend (524288) [03/Jan/2012:15:06:43 -0700] - Deleting log file: (/var/lib/dirsrv/slapd-ServerC/db/log.0000000021) [03/Jan/2012:15:06:43 -0700] - Restoring file 1 (/var/lib/dirsrv/slapd-ServerC/db/DBVERSION) [03/Jan/2012:15:06:43 -0700] - Copying /var/lib/dirsrv/slapd-ServerC/bak/2011_12_29_15_27_35/DBVERSION to /var/lib/dirsrv/slapd-ServerC/db/DBVERSION [03/Jan/2012:15:06:43 -0700] - Restoring file 2 (/var/lib/dirsrv/slapd-ServerC/db/log.0000000021) [03/Jan/2012:15:06:43 -0700] - Copying /var/lib/dirsrv/slapd-ServerC/bak/2011_12_29_15_27_35/log.0000000021 to /var/lib/dirsrv/slapd-ServerC/db/log.0000000021 [ lines removed to reduce size ] [03/Jan/2012:15:06:43 -0700] - Restoring file 33 (/var/lib/dirsrv/slapd-ServerC/db/userRoot/uid.db4) [03/Jan/2012:15:06:43 -0700] - Copying /var/lib/dirsrv/slapd-ServerC/bak/2011_12_29_15_27_35/userRoot/uid.db4 to /var/lib/dirsrv/slapd-ServerC/db/userRoot/uid.db4 [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=aci,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=aci,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=entryrdn,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=entryrdn,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nscpEntryDN,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nscpEntryDN,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsds5ReplConflict,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsds5ReplConflict,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsuniqueid,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsuniqueid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=numsubordinates,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=numsubordinates,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=objectclass,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=parentid,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=parentid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=aci,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=aci,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=entryrdn,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=entryrdn,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nscpEntryDN,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nscpEntryDN,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsds5ReplConflict,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsds5ReplConflict,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsuniqueid,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=nsuniqueid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=numsubordinates,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=numsubordinates,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=objectclass,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=parentid,cn=index,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config [03/Jan/2012:15:06:43 -0700] - Del Index Config Entry cn=parentid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config ... The output just continues to display those same "Del Index Config Entry" lines until I stop it. After that I tried deleting the replication agreement on ServerD to ServerC, then tried restoring one of my original ServerC backups but it did the same thing. I have had this problem before trying to do restores of backups from the same server and I thought it had something to do with having replication enabled so I would disable it before doing restores (like above)...thought that fixed it but seems like it hasn't. Does anyone know what I'm doing wrong? Thanks for the help ________________________________ This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.

3 6

setup-ds.pl hangs with "Server failed to start !!! Please check errors log for problems"
by 馬小布 03 Jan '12

03 Jan '12

Hi, All: When I run "yum install 389-ds" on Fedora 15 x64 and then run this command to setup it , it displays the following error message: root@test ~: setup-ds-admin.pl xxxx 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. Administration port [9830]: ============================================================================== The interactive phase is complete. The script will now set up your servers. Enter No or go Back if you want to change something. Are you ready to set up your servers? [yes]: Creating directory server . . . Server failed to start !!! Please check errors log for problems /var/log/dirsvr/slapd-ldap/errors just shows [31/Dec/2011:15:00:46 +0800] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database [31/Dec/2011:15:00:46 +0800] - check_and_set_import_cache: pagesize: 4096, pages: 255648, procpages: 50503 [31/Dec/2011:15:00:46 +0800] - WARNING: After allocating import cache 409036KB, the available memory is 613556KB, which is less than the soft limit 1048576KB. You may want to decrease the import cache size and rerun import. [31/Dec/2011:15:00:46 +0800] - Import allocates 409036KB import cache. [31/Dec/2011:15:00:46 +0800] - import userRoot: Beginning import job... [31/Dec/2011:15:00:46 +0800] - import userRoot: Index buffering enabled with bucket size 100 [31/Dec/2011:15:00:46 +0800] - import userRoot: Processing file "/tmp/ldifHPkSVg.ldif" [31/Dec/2011:15:00:46 +0800] - import userRoot: Finished scanning file "/tmp/ldifHPkSVg.ldif" (9 entries) [31/Dec/2011:15:00:47 +0800] - import userRoot: Workers finished; cleaning up... [31/Dec/2011:15:00:47 +0800] - import userRoot: Workers cleaned up. [31/Dec/2011:15:00:47 +0800] - import userRoot: Cleaning up producer thread... [31/Dec/2011:15:00:47 +0800] - import userRoot: Indexing complete. Post-processing... [31/Dec/2011:15:00:47 +0800] - import userRoot: Flushing caches... [31/Dec/2011:15:00:47 +0800] - import userRoot: Closing files... [31/Dec/2011:15:00:47 +0800] - All database threads now stopped [31/Dec/2011:15:00:47 +0800] - import userRoot: Import complete. Processed 9 entries in 1 seconds. (9.00 entries/sec) [31/Dec/2011:15:00:56 +0800] - Shutting down due to possible conflicts with other slapd processes the log file in /tmp doesn't seem to be any help either. I've already uninstalled, and did this command : root@test ~: rm -fr /etc/dirsrv /var/lock/dirsrv /var/run/dirsrv /var/log/dirsrv reinstalled -- same issue. I'm really lost on this. Could someone can give some help to me ? Thanks.....

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 2012