Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1401871

Summary: restart-dirsrv script shows instance not found
Product: Red Hat Enterprise Linux 6 Reporter: Sankar Ramalingam <sramling>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: high    
Version: 6.9CC: nkinder, rmeggins, sramling
Target Milestone: rc   
Target Release: 6.9   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-13 13:47:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sankar Ramalingam 2016-12-06 10:15:19 UTC 
Description of problem: The scripts under /usr/sbin/restart(stop/start)-dirsrv stopped working on RHEL-6.9. It was working fine till some point and then started reporting no instance(Inst1) found. 


Version-Release number of selected component (if applicable): 389-ds-base-1.2.11.15-85.el6


How reproducible: Not sure if this is consistently reproducible. I will check with few other machines and update my comments.


Steps to Reproduce:
1. Install 389-ds-base-1.2.11.15-85.el6 build on RHEL-6.9
2. Create few directory server instances
3. Use /usr/sbin/restart-dirsrv script to restart/stop/start your instances.

It works for few times. However, it will stop working after some time. Not sure how to reproduce this issue at the moment. 

Actual results: The script /usr/sbin/restart-dirsrv doesn't work.


Expected results: It should work consistently


Additional info:
[root@auto-hv-02-guest09 ~]# rpm -qa |grep -i 389-ds
389-ds-base-libs-1.2.11.15-85.el6.x86_64
389-ds-base-1.2.11.15-85.el6.x86_64

[root@auto-hv-02-guest09 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.9 Beta (Santiago)

[root@auto-hv-02-guest09 ~]# /usr/sbin/restart-dirsrv Inst1
Instance Inst1 not found.
[root@auto-hv-02-guest09 ~]# service dirsrv restart Inst1
Shutting down dirsrv: 
    Inst1...[  OK  ]
Starting dirsrv: 
    Inst1...[06/Dec/2016:04:59:54 -0500] SSL Initialization - Configured SSL version range: min: TLS1.0, max: TLS1.2
[  OK  ]
[root@auto-hv-02-guest09 ~]# ls -al /usr/sbin/restart-dirsrv
-rwxr-xr-x. 1 root root 1642 Nov  7 14:50 /usr/sbin/restart-dirsrv
Comment 3 Noriko Hosoi 2016-12-08 21:18:50 UTC 
A couple of questions...

1) Does this mean you've just created an instance with setup-ds.pl?  No further configuration, e.g., setting up SSL?
> 2. Create few directory server instances

2) You specifically mentioned "restart-dirsrv".  Does "stop-dirsrv" then "start-dirsrv" work?  Or share the same problem?
Comment 4 Sankar Ramalingam 2016-12-09 13:38:23 UTC 
(In reply to Noriko Hosoi from comment #3)
> A couple of questions...
> 
> 1) Does this mean you've just created an instance with setup-ds.pl?  No
> further configuration, e.g., setting up SSL?
I configured MMR with SSL.
> > 2. Create few directory server instances
> 
> 2) You specifically mentioned "restart-dirsrv".  Does "stop-dirsrv" then
> "start-dirsrv" work?  Or share the same problem?
stop-dirsrv and start-dirsrv also shared the same problem.
Comment 5 Noriko Hosoi 2016-12-11 07:09:05 UTC 
(In reply to Sankar Ramalingam from comment #0)
> Description of problem: The scripts under
> /usr/sbin/restart(stop/start)-dirsrv stopped working on RHEL-6.9. It was
> working fine till some point and then started reporting no instance(Inst1)
> found. 

I think we need more strict steps to reproduce the problem...  Do you have any history what you did on the system?  The error/access/audit logs?

Do you still keep the VM?  Can we access it?  Thanks.
Comment 6 Sankar Ramalingam 2016-12-13 11:41:44 UTC 
(In reply to Noriko Hosoi from comment #5)
> (In reply to Sankar Ramalingam from comment #0)
> > Description of problem: The scripts under
> > /usr/sbin/restart(stop/start)-dirsrv stopped working on RHEL-6.9. It was
> > working fine till some point and then started reporting no instance(Inst1)
> > found. 
> 
> I think we need more strict steps to reproduce the problem...  Do you have
> any history what you did on the system?  The error/access/audit logs?
> 
> Do you still keep the VM?  Can we access it?  Thanks.
Sorry, the machine returned to beaker pool :(. I will reserve another system to reproduce the issue and then share it across.
Comment 7 Sankar Ramalingam 2016-12-13 13:47:53 UTC 
I reserved a beaker machine and followed similar steps to reproduce the issue, but no luck. There is no consistent way to reproduce this. Hence, closing this bug as "INSUFFICIENT DATA".