How to run mongod from the commandline?Switching from 2 large collections to multiple small ones in MongoDB...

Is it logically or scientifically possible to artificially send energy to the body?

GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?

What does the expression "A Mann!" means

Should I tell management that I intend to leave due to bad software development practices?

How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?

Can a virus destroy the BIOS of a modern computer?

Size of subfigure fitting its content (tikzpicture)

Do scales need to be in alphabetical order?

Why is this clock signal connected to a capacitor to gnd?

Can I run a new neutral wire to repair a broken circuit?

Ambiguity in the definition of entropy

A category-like structure without composition?

How dangerous is XSS?

Intersection Puzzle

Why didn't Miles's spider sense work before?

Why didn't Boeing produce its own regional jet?

What's the in-universe reasoning behind sorcerers needing material components?

What historical events would have to change in order to make 19th century "steampunk" technology possible?

How much of data wrangling is a data scientist's job?

Is it acceptable for a professor to tell male students to not think that they are smarter than female students?

How do I deal with an unproductive colleague in a small company?

What do you call someone who asks many questions?

Why doesn't using multiple commands with a || or && conditional work?

How can saying a song's name be a copyright violation?



How to run mongod from the commandline?


Switching from 2 large collections to multiple small ones in MongoDB 3.4Service mongod fails after adding security.keyFile in config filewhy my mongodb balancer doesn't run against all shards server?service mongod cant start, permission denied mongod.lock when changing dbpathCould we recover Mongo records from the data files only without namespace files?139 : Failed with error 'aborted', from rs4 to rs1How to add `--sslAllowInvalidCertificates` on mongodb uri?Mongodb 3.4 keyFile Not workinghow to set Mongod config set multiple bindIp addressesHow to install specific mongo version from the PPA?













0















How do you manually run mongod from the commandline, so it outputs all logging directly in your terminal?



I'm trying to diagnose a crashing Mongo 3.4.11 database on Ubuntu 16. When I try and start it via sudo service mongodb start it says:



Job for mongodb.service failed because the control process exited with error code. See "systemctl status mongodb.service" and "journalctl -xe" for details.


However, systemctl status mongodb.service gives me an equally useless message:



● mongodb.service - LSB: An object/document-oriented database
Loaded: loaded (/etc/init.d/mongodb; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-02-07 20:32:17 UTC; 26s ago
Docs: man:systemd-sysv-generator(8)
Process: 2392 ExecStop=/etc/init.d/mongodb stop (code=exited, status=0/SUCCESS)
Process: 2913 ExecStart=/etc/init.d/mongodb start (code=exited, status=1/FAILURE)

Feb 07 20:32:16 proddb1 systemd[1]: Starting LSB: An object/document-oriented database...
Feb 07 20:32:16 proddb1 mongodb[2913]: * Starting database mongodb
Feb 07 20:32:17 proddb1 mongodb[2913]: ...fail!
Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Control process exited, code=exited status=1
Feb 07 20:32:17 proddb1 systemd[1]: Failed to start LSB: An object/document-oriented database.
Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Unit entered failed state.
Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Failed with result 'exit-code'.


Nothing's written to the log at /var/log/mongodb/mongodb.log.



I tried manually launching the daemon via:



sudo -u mongodb /usr/bin/mongod --config /etc/mongod.conf


but after a few seconds, this simply returned with:



Aborted (core dumped)









share|improve this question














bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    How do you manually run mongod from the commandline, so it outputs all logging directly in your terminal?



    I'm trying to diagnose a crashing Mongo 3.4.11 database on Ubuntu 16. When I try and start it via sudo service mongodb start it says:



    Job for mongodb.service failed because the control process exited with error code. See "systemctl status mongodb.service" and "journalctl -xe" for details.


    However, systemctl status mongodb.service gives me an equally useless message:



    ● mongodb.service - LSB: An object/document-oriented database
    Loaded: loaded (/etc/init.d/mongodb; bad; vendor preset: enabled)
    Active: failed (Result: exit-code) since Wed 2018-02-07 20:32:17 UTC; 26s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 2392 ExecStop=/etc/init.d/mongodb stop (code=exited, status=0/SUCCESS)
    Process: 2913 ExecStart=/etc/init.d/mongodb start (code=exited, status=1/FAILURE)

    Feb 07 20:32:16 proddb1 systemd[1]: Starting LSB: An object/document-oriented database...
    Feb 07 20:32:16 proddb1 mongodb[2913]: * Starting database mongodb
    Feb 07 20:32:17 proddb1 mongodb[2913]: ...fail!
    Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Control process exited, code=exited status=1
    Feb 07 20:32:17 proddb1 systemd[1]: Failed to start LSB: An object/document-oriented database.
    Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Unit entered failed state.
    Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Failed with result 'exit-code'.


    Nothing's written to the log at /var/log/mongodb/mongodb.log.



    I tried manually launching the daemon via:



    sudo -u mongodb /usr/bin/mongod --config /etc/mongod.conf


    but after a few seconds, this simply returned with:



    Aborted (core dumped)









    share|improve this question














    bumped to the homepage by Community 9 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      How do you manually run mongod from the commandline, so it outputs all logging directly in your terminal?



      I'm trying to diagnose a crashing Mongo 3.4.11 database on Ubuntu 16. When I try and start it via sudo service mongodb start it says:



      Job for mongodb.service failed because the control process exited with error code. See "systemctl status mongodb.service" and "journalctl -xe" for details.


      However, systemctl status mongodb.service gives me an equally useless message:



      ● mongodb.service - LSB: An object/document-oriented database
      Loaded: loaded (/etc/init.d/mongodb; bad; vendor preset: enabled)
      Active: failed (Result: exit-code) since Wed 2018-02-07 20:32:17 UTC; 26s ago
      Docs: man:systemd-sysv-generator(8)
      Process: 2392 ExecStop=/etc/init.d/mongodb stop (code=exited, status=0/SUCCESS)
      Process: 2913 ExecStart=/etc/init.d/mongodb start (code=exited, status=1/FAILURE)

      Feb 07 20:32:16 proddb1 systemd[1]: Starting LSB: An object/document-oriented database...
      Feb 07 20:32:16 proddb1 mongodb[2913]: * Starting database mongodb
      Feb 07 20:32:17 proddb1 mongodb[2913]: ...fail!
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Control process exited, code=exited status=1
      Feb 07 20:32:17 proddb1 systemd[1]: Failed to start LSB: An object/document-oriented database.
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Unit entered failed state.
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Failed with result 'exit-code'.


      Nothing's written to the log at /var/log/mongodb/mongodb.log.



      I tried manually launching the daemon via:



      sudo -u mongodb /usr/bin/mongod --config /etc/mongod.conf


      but after a few seconds, this simply returned with:



      Aborted (core dumped)









      share|improve this question














      How do you manually run mongod from the commandline, so it outputs all logging directly in your terminal?



      I'm trying to diagnose a crashing Mongo 3.4.11 database on Ubuntu 16. When I try and start it via sudo service mongodb start it says:



      Job for mongodb.service failed because the control process exited with error code. See "systemctl status mongodb.service" and "journalctl -xe" for details.


      However, systemctl status mongodb.service gives me an equally useless message:



      ● mongodb.service - LSB: An object/document-oriented database
      Loaded: loaded (/etc/init.d/mongodb; bad; vendor preset: enabled)
      Active: failed (Result: exit-code) since Wed 2018-02-07 20:32:17 UTC; 26s ago
      Docs: man:systemd-sysv-generator(8)
      Process: 2392 ExecStop=/etc/init.d/mongodb stop (code=exited, status=0/SUCCESS)
      Process: 2913 ExecStart=/etc/init.d/mongodb start (code=exited, status=1/FAILURE)

      Feb 07 20:32:16 proddb1 systemd[1]: Starting LSB: An object/document-oriented database...
      Feb 07 20:32:16 proddb1 mongodb[2913]: * Starting database mongodb
      Feb 07 20:32:17 proddb1 mongodb[2913]: ...fail!
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Control process exited, code=exited status=1
      Feb 07 20:32:17 proddb1 systemd[1]: Failed to start LSB: An object/document-oriented database.
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Unit entered failed state.
      Feb 07 20:32:17 proddb1 systemd[1]: mongodb.service: Failed with result 'exit-code'.


      Nothing's written to the log at /var/log/mongodb/mongodb.log.



      I tried manually launching the daemon via:



      sudo -u mongodb /usr/bin/mongod --config /etc/mongod.conf


      but after a few seconds, this simply returned with:



      Aborted (core dumped)






      mongodb-3.4






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 7 '18 at 21:00









      CerinCerin

      3452522




      3452522





      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Because nothing is written to log file, the first (and only) problem is (probably) ownership of log file. Usermongodb don't have access to that file. sudo chown -R mongodb: /var/log/mongodb should fix that.



          What comes to the original question of how to run mongod at the command line and see what is happening, you have two choices. First is comment out (from config file) line what orders mongod to fork itself to background. Second possibility is check from config file, what parameters you need (like dbPath) and then replace that --config with those command line parameters. You can see list of command line parameters with mongod --help command






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f197335%2fhow-to-run-mongod-from-the-commandline%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Because nothing is written to log file, the first (and only) problem is (probably) ownership of log file. Usermongodb don't have access to that file. sudo chown -R mongodb: /var/log/mongodb should fix that.



            What comes to the original question of how to run mongod at the command line and see what is happening, you have two choices. First is comment out (from config file) line what orders mongod to fork itself to background. Second possibility is check from config file, what parameters you need (like dbPath) and then replace that --config with those command line parameters. You can see list of command line parameters with mongod --help command






            share|improve this answer




























              0














              Because nothing is written to log file, the first (and only) problem is (probably) ownership of log file. Usermongodb don't have access to that file. sudo chown -R mongodb: /var/log/mongodb should fix that.



              What comes to the original question of how to run mongod at the command line and see what is happening, you have two choices. First is comment out (from config file) line what orders mongod to fork itself to background. Second possibility is check from config file, what parameters you need (like dbPath) and then replace that --config with those command line parameters. You can see list of command line parameters with mongod --help command






              share|improve this answer


























                0












                0








                0







                Because nothing is written to log file, the first (and only) problem is (probably) ownership of log file. Usermongodb don't have access to that file. sudo chown -R mongodb: /var/log/mongodb should fix that.



                What comes to the original question of how to run mongod at the command line and see what is happening, you have two choices. First is comment out (from config file) line what orders mongod to fork itself to background. Second possibility is check from config file, what parameters you need (like dbPath) and then replace that --config with those command line parameters. You can see list of command line parameters with mongod --help command






                share|improve this answer













                Because nothing is written to log file, the first (and only) problem is (probably) ownership of log file. Usermongodb don't have access to that file. sudo chown -R mongodb: /var/log/mongodb should fix that.



                What comes to the original question of how to run mongod at the command line and see what is happening, you have two choices. First is comment out (from config file) line what orders mongod to fork itself to background. Second possibility is check from config file, what parameters you need (like dbPath) and then replace that --config with those command line parameters. You can see list of command line parameters with mongod --help command







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 8 '18 at 6:00









                JJussiJJussi

                3,1591515




                3,1591515






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f197335%2fhow-to-run-mongod-from-the-commandline%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...