mongod: unrecognized service , mongod.service is present already

Question

other services like apache2, etc are working fine.
But when I type sudo service mongod start I get this error:

mongod: unrecognized service

I have this file:

/lib/systemd/system/mongod.service

It says this:

[Unit]

Description=High-performance, schema-free document-oriented database

After=network.target

Documentation=https://docs.mongodb.org/manual



[Service]

User=mongodb

Group=mongodb

ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf

# file size

LimitFSIZE=infinity

# cpu time

LimitCPU=infinity

# virtual memory size

LimitAS=infinity

# open files

LimitNOFILE=64000

# processes/threads

LimitNPROC=64000

# total threads (user+kernel)

TasksMax=infinity

TasksAccounting=false



# Recommended limits for for mongod as specified in

# http://docs.mongodb.org/manual/reference/ulimit/#recommended-settings



[Install]

WantedBy=multi-user.target

Did you resolve this? I have the same problem.

– Brandon

Mar 1 '17 at 2:40 — Mar 1 '17 at 2:40
@Brandon Its related to upstart and systemd.

– user1735921

May 16 '17 at 7:57 — May 16 '17 at 7:57

derHugo 2,32321531 · Accepted Answer · 2017-11-16 14:58:35Z

I had the same problem after pulling the ubuntu:17:04 docker image and installing mongodb-org

It looks like Mongodb created a systemd startup file which was already replaced by upstart.

As a workaround:

Create a new file /etc/init/mongod.conf (requires sudo rights). You can use: sudo gedit /etc/init/mongod.conf

Paste the following contents into the newly created upstart file:

# Ubuntu upstart file at /etc/init/mongod.conf



# Recommended ulimit values for mongod or mongos

# See http://docs.mongodb.org/manual/reference/ulimit/#recommended-settings

#

limit fsize unlimited unlimited

limit cpu unlimited unlimited

limit as unlimited unlimited

limit nofile 64000 64000

limit rss unlimited unlimited

limit nproc 64000 64000



kill timeout 300 # wait 300s between SIGTERM and SIGKILL.



pre-start script

  DAEMONUSER=${DAEMONUSER:-mongodb}

  if [ ! -d /var/lib/mongodb ]; then

    mkdir -p /var/lib/mongodb && chown mongodb:mongodb /var/lib/mongodb

  fi

  if [ ! -d /var/log/mongodb ]; then

    mkdir -p /var/log/mongodb && chown mongodb:mongodb /var/log/mongodb

  fi

  touch /var/run/mongodb.pid

  chown $DAEMONUSER /var/run/mongodb.pid

end script



start on runlevel [2345]

stop on runlevel [06]



script

  ENABLE_MONGOD="yes"

  CONF=/etc/mongod.conf

  DAEMON=/usr/bin/mongod

  DAEMONUSER=${DAEMONUSER:-mongodb}

  DAEMONGROUP=${DAEMONGROUP:-mongodb}



  if [ -f /etc/default/mongod ]; then . /etc/default/mongod; fi



  # Handle NUMA access to CPUs (SERVER-3574)

  # This verifies the existence of numactl as well as testing that the command works

  NUMACTL_ARGS="--interleave=all"

  if which numactl >/dev/null 2>/dev/null && numactl $NUMACTL_ARGS ls / >/dev/null 2>/dev/null

  then

    NUMACTL="$(which numactl) -- $NUMACTL_ARGS"

    DAEMON_OPTS=${DAEMON_OPTS:-"--config $CONF"}

  else

    NUMACTL=""

    DAEMON_OPTS="-- "${DAEMON_OPTS:-"--config $CONF"}

  fi



  if [ "x$ENABLE_MONGOD" = "xyes" ]

  then

    exec start-stop-daemon --start 

        --chuid $DAEMONUSER:$DAEMONGROUP 

        --pidfile /var/run/mongodb.pid 

        --make-pidfile 

        --exec $NUMACTL $DAEMON $DAEMON_OPTS

  fi

end script

Now, you can use the following commands:

sudo service mongod start

sudo service mongod stop

sudo service mongod status

reference:
https://github.com/mongodb/mongo/blob/master/debian/mongod.upstart

thankyou so much... upstart was the issue, i didn't have upstart, so I had do sudo mongod & everytime, but thanks the upstart script you mentioned, things will be lot more easier. — Jun 15 '17 at 6:52

user909945user909945 111 · Accepted Answer · 2019-01-03 06:23:01Z

I kept getting the same error when trying to start the mongo service. mongod worked, but then I need to keep one terminal window open to use mongo in another. nothing else worked for me except this:

'mongod --fork --logpath /var/log/mongodb.log'

Above command starts the mongo daemon if you don't already have it started and then you can just type 'mongo' in command line and mongo works

(from here: https://docs.mongodb.com/manual/tutorial/manage-mongodb-processes/)

Thanks, I know about this already, because I was using it until I found the right upstart script, I wanted to have preconfigured commands, rather than typing such long commands every time with logpath and other configurations, so an upstart script is the best solution. — Jan 4 at 7:23

RifaideenRifaideen 17113 · Accepted Answer · 2019-03-18 11:12:47Z

0

I removed mongo lock file first

sudo rm /var/lib/mongodb/mongod.lock

then started the mongod using the following command

sudo mongod --fork -f /etc/mongod.conf

answered 20 mins ago

Rifaideen

17113

add a comment |

derHugo 2,32321531 · Accepted Answer · 2017-11-16 14:58:35Z

I had the same problem after pulling the ubuntu:17:04 docker image and installing mongodb-org

It looks like Mongodb created a systemd startup file which was already replaced by upstart.

As a workaround:

Create a new file /etc/init/mongod.conf (requires sudo rights). You can use: sudo gedit /etc/init/mongod.conf

Paste the following contents into the newly created upstart file:

# Ubuntu upstart file at /etc/init/mongod.conf



# Recommended ulimit values for mongod or mongos

# See http://docs.mongodb.org/manual/reference/ulimit/#recommended-settings

#

limit fsize unlimited unlimited

limit cpu unlimited unlimited

limit as unlimited unlimited

limit nofile 64000 64000

limit rss unlimited unlimited

limit nproc 64000 64000



kill timeout 300 # wait 300s between SIGTERM and SIGKILL.



pre-start script

  DAEMONUSER=${DAEMONUSER:-mongodb}

  if [ ! -d /var/lib/mongodb ]; then

    mkdir -p /var/lib/mongodb && chown mongodb:mongodb /var/lib/mongodb

  fi

  if [ ! -d /var/log/mongodb ]; then

    mkdir -p /var/log/mongodb && chown mongodb:mongodb /var/log/mongodb

  fi

  touch /var/run/mongodb.pid

  chown $DAEMONUSER /var/run/mongodb.pid

end script



start on runlevel [2345]

stop on runlevel [06]



script

  ENABLE_MONGOD="yes"

  CONF=/etc/mongod.conf

  DAEMON=/usr/bin/mongod

  DAEMONUSER=${DAEMONUSER:-mongodb}

  DAEMONGROUP=${DAEMONGROUP:-mongodb}



  if [ -f /etc/default/mongod ]; then . /etc/default/mongod; fi



  # Handle NUMA access to CPUs (SERVER-3574)

  # This verifies the existence of numactl as well as testing that the command works

  NUMACTL_ARGS="--interleave=all"

  if which numactl >/dev/null 2>/dev/null && numactl $NUMACTL_ARGS ls / >/dev/null 2>/dev/null

  then

    NUMACTL="$(which numactl) -- $NUMACTL_ARGS"

    DAEMON_OPTS=${DAEMON_OPTS:-"--config $CONF"}

  else

    NUMACTL=""

    DAEMON_OPTS="-- "${DAEMON_OPTS:-"--config $CONF"}

  fi



  if [ "x$ENABLE_MONGOD" = "xyes" ]

  then

    exec start-stop-daemon --start 

        --chuid $DAEMONUSER:$DAEMONGROUP 

        --pidfile /var/run/mongodb.pid 

        --make-pidfile 

        --exec $NUMACTL $DAEMON $DAEMON_OPTS

  fi

end script

Now, you can use the following commands:

sudo service mongod start

sudo service mongod stop

sudo service mongod status

reference:
https://github.com/mongodb/mongo/blob/master/debian/mongod.upstart

thankyou so much... upstart was the issue, i didn't have upstart, so I had do sudo mongod & everytime, but thanks the upstart script you mentioned, things will be lot more easier. — Jun 15 '17 at 6:52

user909945user909945 111 · Accepted Answer · 2019-01-03 06:23:01Z

I kept getting the same error when trying to start the mongo service. mongod worked, but then I need to keep one terminal window open to use mongo in another. nothing else worked for me except this:

'mongod --fork --logpath /var/log/mongodb.log'

Above command starts the mongo daemon if you don't already have it started and then you can just type 'mongo' in command line and mongo works

(from here: https://docs.mongodb.com/manual/tutorial/manage-mongodb-processes/)

Thanks, I know about this already, because I was using it until I found the right upstart script, I wanted to have preconfigured commands, rather than typing such long commands every time with logpath and other configurations, so an upstart script is the best solution. — Jan 4 at 7:23

RifaideenRifaideen 17113 · Accepted Answer · 2019-03-18 11:12:47Z

0

I removed mongo lock file first

sudo rm /var/lib/mongodb/mongod.lock

then started the mongod using the following command

sudo mongod --fork -f /etc/mongod.conf

answered 20 mins ago

Rifaideen

17113

add a comment |

Label

Cari Blog Ini

Arsip Blog

Laporkan Penyalahgunaan

Mengenai Saya

Senin, 18 Maret 2019

mongod: unrecognized service , mongod.service is present already

3 Answers

3

Your Answer

Post as a guest

3 Answers

3

3 Answers

3

Post as a guest

0 komentar:

Posting Komentar

Categories

Popular Posts

Label

Cari Blog Ini

Arsip Blog

Laporkan Penyalahgunaan

Mengenai Saya

Senin, 18 Maret 2019

mongod: unrecognized service , mongod.service is present already

3 Answers 3

Your Answer

Sign up or log in

Post as a guest

Post as a guest

3 Answers 3

3 Answers 3

Sign up or log in

Post as a guest

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

0 komentar:

Posting Komentar

Categories

Popular Posts

3 Answers

3

3 Answers

3

3 Answers

3