RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 947093 - start/stop/restart dirsrv scripts should report and error if no instances
Summary: start/stop/restart dirsrv scripts should report and error if no instances
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-01 15:22 UTC by Nathan Kinder
Modified: 2020-09-13 20:26 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.1.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:51:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 640 0 None None None 2020-09-13 20:26:48 UTC

Description Nathan Kinder 2013-04-01 15:22:14 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47303

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.

Comment 1 Rich Megginson 2013-10-01 23:24:21 UTC
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.

Comment 3 Amita Sharma 2014-01-09 13:04:07 UTC
[root@dhcp201-149 export]# start-dirsrv
Starting instance "dhcp201-149"
There is an ns-slapd process already running: 16888

[root@dhcp201-149 export]# /usr/sbin/remove-ds.pl -f -i dirsrv-dhcp201-149
Instance dirsrv-dhcp201-149 removed.

[root@dhcp201-149 export]# start-dirsrv
No instances found in /etc/sysconfig

[root@dhcp201-149 export]# systemctl start dirsrv@dhcp201-149
Job for dirsrv failed. See 'systemctl status dirsrv' and 'journalctl -xn' for details.

[root@dhcp201-149 export]# systemctl status dirsrv
dirsrv - 389 Directory Server dhcp201-149.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; static)
   Active: failed (Result: resources)
Jan 09 12:21:49 dhcp201-149.englab.pnq.redhat.com systemd[1]: Starting 389 Directory Server dhcp201-149....
Jan 09 12:21:49 dhcp201-149.englab.pnq.redhat.com systemd[1]: Started 389 Directory Server dhcp201-149..
Jan 09 12:21:54 dhcp201-149.englab.pnq.redhat.com systemd[1]: Started 389 Directory Server dhcp201-149..
Jan 09 18:06:22 dhcp201-149.englab.pnq.redhat.com systemd[1]: Stopping 389 Directory Server dhcp201-149....
Jan 09 18:06:23 dhcp201-149.englab.pnq.redhat.com systemd[1]: Stopped 389 Directory Server dhcp201-149..
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Starting 389 Directory Server dhcp201-149....
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Failed to load environment files: No such file or directory
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: dirsrv failed to run 'start' task: No such file or directory
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Failed to start 389 Directory Server dhcp201-149..
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Unit dirsrv entered failed state.

[root@dhcp201-149 export]# journalctl -xn
-- Logs begin at Mon 2013-12-23 11:11:25 IST, end at Thu 2014-01-09 18:07:19 IST. --
Jan 09 18:06:37 dhcp201-149.englab.pnq.redhat.com dbus-daemon[551]: dbus[551]: avc:  received policyload notice (seqno=37)
Jan 09 18:06:37 dhcp201-149.englab.pnq.redhat.com dbus[551]: avc:  received policyload notice (seqno=37)
Jan 09 18:06:37 dhcp201-149.englab.pnq.redhat.com dbus-daemon[551]: dbus[551]: [system] Reloaded configuration
Jan 09 18:06:37 dhcp201-149.englab.pnq.redhat.com dbus[551]: [system] Reloaded configuration
Jan 09 18:06:37 dhcp201-149.englab.pnq.redhat.com systemd[1]: Reloading.
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Starting 389 Directory Server dhcp201-149....
-- Subject: Unit dirsrv has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dirsrv has begun starting up.
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Failed to load environment files: No such file or directory
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: dirsrv failed to run 'start' task: No such file or directory
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Failed to start 389 Directory Server dhcp201-149..
-- Subject: Unit dirsrv has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit dirsrv has failed.
-- 
-- The result is failed.
Jan 09 18:07:19 dhcp201-149.englab.pnq.redhat.com systemd[1]: Unit dirsrv entered failed state.


[root@dhcp201-149 export]# stop-dirsrv
No instances found in /etc/sysconfig

[root@dhcp201-149 export]# restart-dirsrv 
No instances found in /etc/sysconfig
[root@dhcp201-149 export]# 

Hence marking VERIFIED.

Comment 4 Ludek Smid 2014-06-13 12:51:42 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.