Bug 692161

Summary: /etc/init.d/solr status returns rake info.. should return status
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Richard Su <rwsu>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.3.1CC: akarol, deltacloud-maint, morazi, rwsu
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: 2011-12-08 13:47:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 684278    

Description wes hayutin 2011-03-30 15:24:35 UTC
Description of problem:



[root@dhcp231-29 log]# /etc/init.d/solr status
rake is stopped

[root@dhcp231-29 log]# rpm -qa | grep aeolus
aeolus-conductor-0.0.3-0.fc14.20110330133246git37c7457.x86_64
aeolus-configure-2.0.0-5.fc14.2011033093316gitecf8f95.noarch
aeolus-conductor-daemons-0.0.3-0.fc14.20110330133246git37c7457.x86_64
aeolus-conductor-doc-0.0.3-0.fc14.20110330133246git37c7457.x86_64

Comment 1 Mike Orazi 2011-04-01 20:56:13 UTC
The init script in puppet checks status on the wrong thing.

The script will require a bigger change because it is possible to have multiple instances of solr running, so we need to distinguish between them.

Comment 2 Richard Su 2011-04-13 22:04:34 UTC
fixed on commit 031813d68451a64e9f173d8cf08ed68cba8b714d

Comment 3 Aziza Karol 2011-06-21 09:13:40 UTC
/etc/init.d/solr status still returns rake info.
It should return solr status.

verification details:
[root@nec-em19 ~]# /etc/init.d/solr  status
rake (pid  6925) is running...

verified on:
[root@nec-em19 ~]# rpm -qa  | grep aeolus
rubygem-aeolus-cli-0.0.1-1.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-doc-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-daemons-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-all-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-configure-2.0.1-0.fc14.20110602110128git5cb9257.noarch

Comment 4 Richard Su 2011-06-21 15:21:09 UTC
I think this is just a misunderstanding. If you look at /etc/init.d/solr, you'll see that solr is actually a rake process. The PROG is /usr/bin/rake. rake is used to start, stop, and check status of solr.

If you do a ps -ef | grep solr, you'll see that the process id matches the id displayed by "service solr status".

Comment 5 wes hayutin 2011-06-21 15:27:01 UTC
<weshay> rwsu, morazi there is a diff between doing the right thing / wrong thing and whats obvious to a new user.. agreed its doing the right thing, but its not obvious
<weshay> honestly I would just remove "rake" from that line

Comment 6 Richard Su 2011-06-22 18:49:38 UTC
Status should now be reported as "solr" instead of "rake".

aeolus-configure-2.0.1-0.fc14.20110622123902gitdf4ae05.noarch.rpm

Comment 7 wes hayutin 2011-06-23 21:47:43 UTC
[root@ibm-x3950m2-01 noarch]# /etc/init.d/solr status
solr (pid  22403) is running...
[root@ibm-x3950m2-01 noarch]# 



[root@ibm-x3950m2-01 noarch]# rpm -qa | grep aeolus
aeolus-conductor-0.3.0-0.el6.20110623205403git551632a.noarch
aeolus-configure-2.0.1-0.el6.20110622123902gitdf4ae05.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110623205403git551632a.noarch
aeolus-all-0.3.0-0.el6.20110623205403git551632a.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110623205403git551632a.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110623205403git551632a.noarch
aeolus-conductor-devel-0.3.0-0.el6.20110623205403git551632a.noarch

Comment 8 wes hayutin 2011-08-01 19:53:39 UTC
release pending...

Comment 9 wes hayutin 2011-08-01 19:55:49 UTC
release pending...

Comment 11 wes hayutin 2011-12-08 13:47:44 UTC
perm close