Bug 692591 - aeolus-conductor deamon status is not working correctly
Summary: aeolus-conductor deamon status is not working correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Mo Morsi
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: ce-beta
TreeView+ depends on / blocked
 
Reported: 2011-03-31 16:02 UTC by wes hayutin
Modified: 2012-01-26 12:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-31 20:54:22 UTC
Embargoed:


Attachments (Terms of Use)

Description wes hayutin 2011-03-31 16:02:28 UTC
Description of problem:
[root@dhcp231-29 ~]# rpm -qa | grep aeolus
aeolus-conductor-daemons-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64
aeolus-configure-2.0.0-5.fc14.20110330155142gitecf8f95.noarch
aeolus-conductor-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64
aeolus-conductor-doc-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64
[root@dhcp231-29 ~]# 



[root@dhcp231-29 ~]# ps -ef | grep conductor
root      8173  1775  0 08:00 pts/0    00:00:00 grep --color=auto conductor
[root@dhcp231-29 ~]# /etc/init.d/aeolus-conductor start
Starting aeolus-conductor:                                 [  OK  ]
[root@dhcp231-29 ~]# ps -ef | grep conductor
root      8205  1775  0 08:00 pts/0    00:00:00 grep --color=auto conductor
[root@dhcp231-29 ~]# /etc/init.d/aeolus-conductor status
 (pid  8182) is running...
[root@dhcp231-29 ~]#

Comment 2 wes hayutin 2011-04-01 01:54:13 UTC
There has not been a release of CE, you cant close the bug.  Moving back to verified.

Comment 3 Shveta 2011-04-01 11:36:36 UTC
 ps -ef | grep conductor
root     10846     1  0 03:48 ?        00:00:11 java -Djetty.port=8983 -Dsolr.data.dir=/usr/share/aeolus-conductor/solr/data/production -Dsolr.solr.home=/usr/share/aeolus-conductor/solr -Djava.util.logging.config.file=/tmp/logging.properties20110401-10846-jlqh8x-0 -jar start.jar
postgres 10925 15933  0 03:48 ?        00:00:00 postgres: aeolus conductor 127.0.0.1(55136) idle  
aeolus   10968     1  0 03:48 ?        00:00:00 ruby /usr/share/aeolus-conductor/condor_refreshd/condor_refreshd
postgres 10969 15933  0 03:48 ?        00:00:00 postgres: aeolus conductor 127.0.0.1(55139) idle  
postgres 11076 15933  0 03:48 ?        00:00:00 postgres: aeolus conductor 127.0.0.1(55164) idle  
aeolus   11118     1  0 03:48 ?        00:00:00 /usr/bin/ruby /usr/share/aeolus-conductor/warehouse_sync/warehouse_sync-server
postgres 11119 15933  0 03:48 ?        00:00:00 postgres: aeolus conductor 127.0.0.1(55166) idle  
aeolus   11687     1  0 03:49 ?        00:00:00 /usr/bin/ruby /usr/share/aeolus-conductor/dbomatic/dbomatic
root     15175  9511  0 07:35 pts/5    00:00:00 grep --color=auto conductor
[root@dhcp193-9 ~]# /etc/init.d/aeolus-conductor start
Starting aeolus-conductor:                                 [FAILED]
Thin is already running
[root@dhcp193-9 ~]# /etc/init.d/aeolus-conductor status
 (pid  10914) is running...

Comment 4 wes hayutin 2011-08-01 19:56:08 UTC
release pending...

Comment 5 wes hayutin 2011-08-01 19:57:46 UTC
release pending...

Comment 7 wes hayutin 2011-12-08 13:54:30 UTC
closing out old bugs

Comment 8 wes hayutin 2011-12-08 14:07:46 UTC
perm close


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