Bug 956761 - RHQ Controll - storage node process is up always (even if it's stopped)
Summary: RHQ Controll - storage node process is up always (even if it's stopped)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Installer
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 951619
TreeView+ depends on / blocked
 
Reported: 2013-04-25 14:51 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-25 15:54:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
storage_node-status.png (174.82 KB, image/png)
2013-04-25 14:51 UTC, Armine Hovsepyan
no flags Details
storage_process.png (167.46 KB, image/png)
2013-04-25 14:56 UTC, Armine Hovsepyan
no flags Details
storage-exitValue.png (164.16 KB, image/png)
2013-04-25 15:08 UTC, Armine Hovsepyan
no flags Details

Description Armine Hovsepyan 2013-04-25 14:51:35 UTC
Created attachment 739939 [details]
storage_node-status.png

Description of problem:
RHQ Controll - storage node process is up always (even if it's stopped)

Version-Release number of selected component (if applicable):
jenkins build 169

How reproducible:
always

Steps to Reproduce:
1. run ./rhqctl.sh install --storage (both storage and agent are started)
2. run ./rhqcrl.sh stop  
3. killall -9 java
4. run ./rhqctl.sh status
  
Actual results:
After step2. shows error that storage cannot be stopped
Afters tep4. storage node is still visible as up - while there is no cassandra process is running

Expected results:
After step2. both agent and storage should be stopped

Additional info:
screenshots are attached

Comment 1 Armine Hovsepyan 2013-04-25 14:56:25 UTC
Created attachment 739951 [details]
storage_process.png

Comment 2 Armine Hovsepyan 2013-04-25 15:08:25 UTC
Created attachment 739953 [details]
storage-exitValue.png

Comment 3 John Sanda 2013-04-25 15:54:21 UTC
The status command simply checks for the pid files of each service. The killall -9 is an invalid step. If I forcibly kill a process with -9, the pid file won't get deleted. You will find this behavior with the server, agent, storage node, etc. I am going to close this bug since step 3 is not valid.


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