Bug 1158076
Summary: | error in /etc/init.d/mongod status code | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Eduard Barrera <ebarrera> |
Component: | mongodb | Assignee: | hguemar |
Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.0 | CC: | adahms, ajeain, dmaley, ebarrera, felipe.alfaro, fpercoco, hguemar, karlthered, lhh, lyarwood, pcaruana, sgordon, tvvcox, yeylon |
Target Milestone: | z6 | Keywords: | ZStream |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | mongodb-2.4.6-8.el6ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-04-23 13:03:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eduard Barrera
2014-10-28 13:54:02 UTC
I'm amazed how these simple typos are able to sneak in :-) Hi Flavio, yes, its ops 4, i reproduced it in my test environments, i didn't tried yet on osp 5. give me 5 minuts and I will try on osp 5 As indicated OSP is working ok and the fix doesn't look complicated. /etc/init.d/mongod: line 163: [: missing `]' By the way this is also visible at https://bugzilla.redhat.com/show_bug.cgi?id=1112416#c8 @Eduard the version of the init script I have doesn't seem to match the error reported. Would you mind uploading yours? Please provide the initscript as requested by Flavio. Haïkel/Flavio - The initscript Eduard refered to is what ships in 2.4.6-5.el6ost. The problem reported here is resolved w/ the following change in the 2.4.6-8.el6ost initscript:
163c163,165
< [ -z "$a" || "$a" = "0.0.0.0" ] && a=127.0.0.1
---
> # mongodb defaults to INADDR_ANY, so use that
> # if not set in the config file
> [ -z "$a" ] && a=0.0.0.0
Basically the issue is that 2.4.6-8.el6ost isn't available in the osp-4 channels.
@Dave: thanks for your feedback, I'll ship the fix asap. Lon tagged the build from RHOS5/EL6 so it should be fixed. verified in: # rpm -qa |grep mongodb mongodb-2.4.6-8.el6ost.x86_64 libmongodb-2.4.6-8.el6ost.x86_64 mongodb-server-2.4.6-8.el6ost.x86_64 # /etc/init.d/mongod status mongod (pid 22911) is running... listening on 127.0.0.1:27017 connection test successful [root@opens-vdsb ~(keystone_admin)]# vim /etc/init.d/mongod [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod stop Stopping mongod: [ OK ] [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod start Starting mongod: [ OK ] Waiting for mongod to become available: [ OK ] [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod (pid 18023) is running... listening on 127.0.0.1:27017 connection test successful [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod (pid 18023) is running... listening on 127.0.0.1:27017 connection test successful [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod (pid 18023) is running... listening on 127.0.0.1:27017 connection test successful [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod (pid 18023) is running... listening on 127.0.0.1:27017 connection test successful [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod stop Stopping mongod: [ OK ] [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod stop [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod stop [root@opens-vdsb ~(keystone_admin)]# [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod is stopped [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod start Starting mongod: [ OK ] Waiting for mongod to become available: ^[[A [ OK ] [root@opens-vdsb ~(keystone_admin)]# /etc/init.d/mongod status mongod (pid 18192) is running... listening on 127.0.0.1:27017 connection test successful Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0885.html |