Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): katello-0.1.51-1.git.7.67cd65f.fc14.noarch How reproducible: Intermittent Steps to Reproduce: 1. service katello start 2. service katello stop 3. Actual results: [ FAILED ] Expected results: [ OK ] Additional info: Katello does actually stop even though the service script fails. Running stop again always seems to work, it detects that the service is not running.
Taking
[root@dhcp77-194 ~]# service katello status katello is not running. [root@dhcp77-194 ~]# service katello start Starting katello (via systemctl): [ OK ] [root@dhcp77-194 ~]# service katello status katello is running. [root@dhcp77-194 ~]# [root@dhcp77-194 ~]# service katello stop Stopping katello (via systemctl): [ OK ] [root@dhcp77-194 ~]# service katello status katello is not running. Works for me. # rpm -q katello katello-0.1.54-1.git.83.24aaa54.fc15.noarch The bug is most likely gone. Start/stop has been modified to use nohup as a workaround. We will use some 3rd party web server eventually.
MODIFIED means there was a fix.