In RHEL6, within lib389 - Directory Server Start and Stop scripts does not work as the path //sbin/stop-dirsrv is not correct.
Error --
(Pdb) s
/usr/lib/python2.6/site-packages/lib389-1.0.1-py2.6.egg/lib389/tools.py(283)stop() -> if not self.isLocal and hasattr(self, 'asport'): (Pdb) s /usr/lib/python2.6/site-packages/lib389-1.0.1-py2.6.egg/lib389/tools.py(295)stop() -> return DirSrvTools.serverCmd(self, 'stop', verbose, timeout) (Pdb) s WARNING:lib389.tools:unbinding before stop INFO:lib389.tools:Setup error log WARNING:lib389.tools:Running command: '//sbin/stop-dirsrv master_1' sh: //sbin/stop-dirsrv: No such file or directory ERROR:lib389.tools:Error: could not stop server /usr/lib64/dirsrv master_1: 32512 1 (Pdb)
Cause -- In RHEL7, The /bin, /sbin, /lib and /lib64 directories are moved under the /usr directory, and the symlinks are created :: lrwxrwxrwx. 1 root root 8 Aug 24 13:13 sbin -> usr/sbin
But in RHEL6, we don't have symlinks and sbin is a separate directory under root.
So, for example /usr/lib/python2.6/site-packages/lib389-1.0.1-py2.6.egg/lib389/tools.py -- line 192 --> sbinDir = os.path.join(self.prefix + '/sbin') which leads to //sbin/stop-dirsrv master_1, which does not exists in RHEL6.
Fix proposal - A patch is required which can detect running OS (RHEL6, RHEL7, Fedora, CentOS) and adjust sbinDir path accordingly.
attachment 0001-Ticket-48382-Fix-serverCmd-to-get-sbin-dir-properly.patch
This patch would help to get sbin dir properly. That would result the successful tests execution on RHEL 6.
To ssh://git.fedorahosted.org/git/389/lib389.git
Pushed to master: d4259ee..8e7893d master -> master commit 8e7893d315ee93be28bdb66321d55eb9b180179c Author: Simon Pichugin spichugi@redhat.com Date: Wed Jul 27 22:29:46 2016 +0200
Metadata Update from @spichugi: - Issue assigned to spichugi - Issue set to the milestone: lib389 1.0.3
Metadata Update from @mreynolds: - Issue close_status updated to: None (was: Fixed) - Issue set to the milestone: None (was: lib389 1.0.3)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1713
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix
Login to comment on this ticket.