Error No Dirsrv Instances Configured
years ago Last modified 4 years ago start/stop/restart dirsrv scripts should report and error if no instances Reported by: rmeggins Owned by: rmeggins Priority: major Milestone: 1.3.1 Component: Command Line Utilities Version: 1.2.11 Keywords: Cc: Blocked By: Blocking: Review: ack Ticket origin: QE Red Hat Bugzilla: 947093 Description If there are no instances, and you run e.g. start-dirsrv, you get a very strange output: Starting instance "*" Instance admin-serv not found. or Instance bin or some other strangeness. It should just detect if no instances exist, report so, and exit with an error code. Attachments 0003-Ticket-47303-start-stop-restart-dirsrv-scripts-shoul.patch (2.6 KB) - added by rmeggins 4 years ago. 0003-Ticket-47303-start-stop-restart-dirsrv-scripts-shoul.patch Change History Changed 4 years ago by rmeggins Attachment 0003-Ticket-47303-start-stop-restart-dirsrv-scripts-shoul.patch added 0003-Ticket-47303-start-stop-restart-dirsrv-scripts-shoul.patch comment:1 Changed 4 years ago by rmeggins Owner set to rmeggins Status changed from new to accepted Review set to review? Milestone changed from 0.0 NEEDS_TRIAGE to 1.3.1 comment:2 Changed 4 years ago by mreynolds When I run start-dirsrv(without your fix) from a random directory, it looks for all the files in the current directory. Its seems to be very broken. [root@localhost BUILD]# start-dirsrv Starting instance "*" Instance config.h not found. [root@localhost ds]# start-dirsrv Starting instance "*" Instance 0001-Ticket-332-Fix-usage-in-scripts.patch not found. [root@localhost ds]# ls 0001-Ticket-332-Fix-usage-in-scripts.patch ... ... With your fix: [root@localhost BUILD]# start-dirsrv No instances found in /root/.dirsrv comment:3 Changed 4 years ago by rmeggins Yep, looks like this is broken, if you do a su to root (not su - root): > su Password: # sh -x sbin/start-dirsrv + '[' rich = root ']' + initconfig_dir=/root/.dirsrv # echo $USER rich # echo $HOME /root # id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon
-XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug668862 - init scripts return wrong error code Summary: init scripts return wrong error code Status: CLOSED CURRENTRELEASE Aliases: None Product: 389 Classification: Community Component: Directory Server (Show other bugs) Sub Component: --- Version: 1.2.7 Hardware: Unspecified Unspecified Priority high Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Nathan Kinder QA Contact: Viktor Ashirov Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: 639035 389_1.2.8 Show dependency tree /graph Reported: 2011-01-11 15:34 EST https://fedorahosted.org/389/ticket/47303 by Simo Sorce Modified: 2015-12-07 12:16 EST (History) CC List: 3 users (show) amsharma jgalipea rmeggins See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2015-12-07 12:16:47 EST Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Flags: ssorce: needinfo+ Attachments (Terms https://bugzilla.redhat.com/show_bug.cgi?id=668862 of Use) Patch (3.62 KB, patch) 2011-02-01 18:02 EST, Nathan Kinder nhosoi: review+ Details | Diff Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Simo Sorce 2011-01-11 15:34:49 EST If you do not pass an instance name, or you pass a wrong instance name, or there are no instances available the init scripts will warn on stdout but will still return 0 to the shell. An error number should be returned instead. Comment 1 Nathan Kinder 2011-02-01 18:02:27 EST Created attachment 476498 [details] Patch Comment 2 Nathan Kinder 2011-02-01 18:29:33 EST Pushed to master. Thanks to Noriko for her review! Counting objects: 9, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 1.18 KiB, done. Total 5 (delta 4), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git b5bee52..5a41728 master -> master Comment 3 Jenny Galipeau 2011-05-16 13:35:00 EDT Which init scripts, can you please be more specific and adds steps to reproduce the issue? Thanks Comment 4 Rich Megginson 2011-05-16 13:43:39 EDT (In reply to comment #3) > Which init scripts, can you please be more specific and adds steps to reproduce > the issue? Thanks step 1 - after a yum instal
2014, 12:53 PMHi! I've just installed 389 Directory Server using this guide: http://suresh-chandra.blogspot.ru/2013/10/configure-389-ds-with-tlsssl-on-rhel-6x.html The problem is STEP 5. I want to restart my 389-ds after successful installation. I try to use this command: "service http://forums.fedoraforum.org/archive/index.php/t-301716.html dirsrv restart" and get this: "Failed to issue method call: Unit dirsrv.service failed to load: No such file or directory". :( What's wrong? William Haller1st December 2014, 04:46 PMI'm not sure what they messed up, but http://www.ibm.com/support/docview.wss?uid=nas2SE52008 try start-dirsrv (along with stop-dirsrv and restart-dirsrv). They seem to work for me. I think it has to do with the systemd trying to make a separate dirsrv start script for each server instance and error no not doing it right, but that's just a guess. zhdanoff3rd December 2014, 09:53 AMWilliam Haller, thanks a lot! These commands work for me! You are the first one, who really helped me to solve this issue. zhdanoff3rd December 2014, 11:58 AMHere is one more thing. I've done everything that was discribed here: http://suresh-chandra.blogspot.ru/2013/10/configure-389-ds-with-tlsssl-on-rhel-6x.html. I've installed CA and server certificates. The next issue for me is that I try to restart directory error no dirsrv server using "restart-dirsrv" command after applying "Enable SSL for this server", but get this: Server failed to start !!! Please check errors log for problems. Here is what system log say: "Enter PIN for Internal (software) Token: - The security password entered is incorrect", and all of this's happend automaticly, without any prompt to enter password needed. After restarting directory server I need to type "Manage Certificates" password. But there is no way to type it here. Terminal just doesn't let me do this. And I really don't know what to do :( William Haller3rd December 2014, 03:51 PMNot sure if we're on the same page for which password is missing, but did you make a file in /etc/dirsrv/slapd-servername called pin.txt? Put your password there in the following format... Internal (Software) Token:your pass phrase here I'm still not happy with the whole cert process. It's messy to say the least. I've got our client directory servers trusting the master, but it wasn't a pretty process. zhdanoff4th December 2014, 08:27 AMYes, William Haller! That's exactly what I'm talking about :) I'm very glad that you understand what I mean. Yes, I made this file, but there is no effect at all. Nothing. Errors are the same :( It's a little strange, isn't
INSTANCE IS CONFIGURED. DoNotDisplayThisDocInPortal nas2147018220560552008 Subscribe to this APAR By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product. Notify me when this APAR changes. Notify me when an APAR for this component changes. APAR (Authorized Program Analysis Report) Abstract OSP-DIRSRV EIM CONFIGURATION FAILS WHEN NO DIRECTORY SERVER INSTANCE IS CONFIGURED. Error Description When there are no directory server instances configured, the EIM configuration wizard fails with error like "GLD0245: Configuration library QUSRDIRCF already exists". Problem Summary The EIM configuration wizard fails with error "GLD0245: Configuration library QUSRDIRCF already exists" when there are no directory server instances configured. Problem Conclusion The error has been fixed. Temporary Fix Comments Circumvention PTFs Available R710 SI46847 2279 Affected Modules Affected Publications Summary Information Status............................................ CLOSED PER HIPER........................................... No Component.................................. 5770SS102 Failing Module.......................... RCHMGR Reported Release................... R710 Duplicate Of.............................. System i Support IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 IBM Corporation. Any trademarks and product or brand names referenced in this document are