Bug 1125122 - one mongod process is left after installing openshift-origin-cartridge-mongodb
Summary: one mongod process is left after installing openshift-origin-cartridge-mongodb
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Rory Thrasher
QA Contact: libra bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-31 05:44 UTC by Johnny Liu
Modified: 2017-01-13 22:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-01-13 22:18:16 UTC

Attachments (Terms of Use)

Description Johnny Liu 2014-07-31 05:44:17 UTC
Description of problem:
When installing mongo cartridge, a mongod process is left, it should be terminated after installation.
# yum install openshift-origin-cartridge-mongodb
  Installing : openshift-origin-cartridge-mongodb-                                                                                                            1/1 
/usr/libexec/openshift/cartridges/mongodb/bin/mkjournal: line 57: 33425 Terminated              scl enable mongodb24 "mongod     --dbpath ${tmpdir}     --journal     --noprealloc     --smallfiles     --bind_ip     --port 27017     -f ${tmpdir}/mongodb.conf" 2>&1 > ${tmpdir}/mongodb.log
MongoDB starting journal saved: /usr/libexec/openshift/cartridges/mongodb/usr/journal-cache/journal.tar.gz
  Verifying  : openshift-origin-cartridge-mongodb-                                                                                                            1/1 

  openshift-origin-cartridge-mongodb.noarch 0:                                                                                                                           


# ps -ef|grep mongo
root     33437 33429  2 01:04 pts/0    00:00:00 mongod --dbpath /tmp/tmp.4ItopnO2bm --journal --noprealloc --smallfiles --bind_ip --port 27017 -f /tmp/tmp.4ItopnO2bm/mongodb.conf

Firstly, install mongo cartridge should not leave a useless mongod process
Secondly, if user want to run mongo server as openshift datastore, that would be blocked.

Kill existing mongod process and its parent process, or reboot this system.

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

How reproducible:

Steps to Reproduce:
1.Using openshift.sh to install node+datastore.
2.After installation, found mongod service could not be started.
# /etc/init.d/mongod status
mongod dead but pid file exists
Seen from mongod log file, it is saying 27017 is in use.
3.Check mongo process running in system.
# ps -ef|grep 11843
root     11843     1  0 20:53 pts/0    00:00:00 /bin/bash /var/tmp/sclqqu04A
root     11854 11843  0 20:53 pts/0    00:00:42 mongod --dbpath /tmp/tmp.V7pSVRGb6m --journal --noprealloc --smallfiles --bind_ip --port 27017 -f /tmp/tmp.V7pSVRGb6m/mongodb.conf
4.Check openshift-origin-cartridge-mongodb rpm post scripts.
# rpm -q --scripts openshift-origin-cartridge-mongodb
postinstall scriptlet (using /bin/sh):
/usr/libexec/openshift/cartridges/mongodb/bin/mkjournal /usr/libexec/openshift/cartridges/mongodb/usr/journal-cache/journal.tar.gz
preuninstall scriptlet (using /bin/sh):
if [ $1 -eq 0 ]; then
  /bin/rm -f /usr/libexec/openshift/cartridges/mongodb/usr/journal-cache/journal.tar.gz

Actual results:
After install mongo cartridge on a system, one mongo process is left.

Expected results:
mongo process should be terminated.

Additional info:

Comment 1 Rory Thrasher 2017-01-13 22:18:16 UTC
OpenShift Enterprise v2 has officially reached EoL.  This product is no longer supported and bugs will be closed.

Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3.  https://www.openshift.com/container-platform/

More information can be found here: https://access.redhat.com/support/policy/updates/openshift/

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