Bug 782803

Summary: service stop may fail to stop cimservermain process
Product: Red Hat Enterprise Linux 5 Reporter: Karel Volný <kvolny>
Component: tog-pegasusAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 5.8CC: azelinka, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-16 14:26:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 807971    

Description Karel Volný 2012-01-18 14:45:58 UTC
Description of problem:
Running the test /CoreOS/tog-pegasus/Regression/bz326281-wrong-init-script-return-codes fails with the new version, while it passed using the old one.

The problem seems to be that 'service tog-pegasus stop' leaves a stale process 'cimservermain' which prevents the service to be started again.

Version-Release number of selected component (if applicable):
tog-pegasus-2.11.0-3.el5

How reproducible:
always

Steps to Reproduce:
1. run the test /CoreOS/tog-pegasus/Regression/bz326281-wrong-init-script-return-codes
  
Actual results:
fail

in particular the error message is:

Spouštím CIM server: cimserver not started: Bind failed: Failed to bind socket on port 5989: Address already in use (error code 98).


Expected results:
pass, no such error, no stale 'cimservermain' process running


Additional info:
compare old version:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/01/1815/181556/382136/4279562/TESTOUT.log

and new version:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/01/1815/181556/382132/4279542/TESTOUT.log

Comment 1 Vitezslav Crhonek 2012-01-18 15:05:13 UTC
Probably same issue as in https://bugzilla.redhat.com/show_bug.cgi?id=735014
Adding SELinux keyword.

Comment 3 Vitezslav Crhonek 2012-01-19 07:23:03 UTC
Is libvirt-cim installed? I saw another similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=736932

cimservermain process is killed by cimserver process. Workaround - kill cimservermain manually. Easy fix, but I don't think that it's correct to do it - kill cimservermain in init script after cimserver.

Comment 4 Karel Volný 2012-01-19 15:49:40 UTC
(In reply to comment #3)
> Is libvirt-cim installed?

nope

.qa.[root@ppcp-5s-m1 tps]# rpm -q libvirt-cim
package libvirt-cim is not installed

and it also cannot be found within the installed set of the failing job:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/01/1815/181556/382132/4279540/23137481/test_log--distribution-install.log

(note also there is no sblim-sfcb ...)

> cimservermain process is killed by cimserver process. Workaround - kill
> cimservermain manually. Easy fix, but I don't think that it's correct to do it
> - kill cimservermain in init script after cimserver.

well, I do not think that making sure there are no stale processes would be that much to ask from the initscript stop action ...