Getting exception on running sh.status() command on MongoDB sharded cluster










0















I am running sh.status() command on my mongos instance of sharded Mongo cluster and I am getting below exception.



mongos> sh.status()
assert: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1

2018-11-14T05:38:55.904+0000 E QUERY [thread1] Error: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1


I am running Mongo 3.2 on ubuntu 16.04 platform. It is working fine on MongoDB version 3.0 on ubuntu 14.04 platform. I have reinstalled everything and tried this on new machines too, everything is working fine except sh.status() command.



Thanks.










share|improve this question
























  • This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

    – Neil Lunn
    Nov 15 '18 at 6:33











  • Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

    – Neil Lunn
    Nov 15 '18 at 6:35















0















I am running sh.status() command on my mongos instance of sharded Mongo cluster and I am getting below exception.



mongos> sh.status()
assert: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1

2018-11-14T05:38:55.904+0000 E QUERY [thread1] Error: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1


I am running Mongo 3.2 on ubuntu 16.04 platform. It is working fine on MongoDB version 3.0 on ubuntu 14.04 platform. I have reinstalled everything and tried this on new machines too, everything is working fine except sh.status() command.



Thanks.










share|improve this question
























  • This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

    – Neil Lunn
    Nov 15 '18 at 6:33











  • Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

    – Neil Lunn
    Nov 15 '18 at 6:35













0












0








0








I am running sh.status() command on my mongos instance of sharded Mongo cluster and I am getting below exception.



mongos> sh.status()
assert: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1

2018-11-14T05:38:55.904+0000 E QUERY [thread1] Error: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1


I am running Mongo 3.2 on ubuntu 16.04 platform. It is working fine on MongoDB version 3.0 on ubuntu 14.04 platform. I have reinstalled everything and tried this on new machines too, everything is working fine except sh.status() command.



Thanks.










share|improve this question
















I am running sh.status() command on my mongos instance of sharded Mongo cluster and I am getting below exception.



mongos> sh.status()
assert: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1

2018-11-14T05:38:55.904+0000 E QUERY [thread1] Error: command failed:
"ok" : 0,
"errmsg" : "error processing query: ns=config.mongosTree: ping $gt new Date(1542173873192)nSort: nProj: n No query solutions",
"code" : 2
: aggregate failed :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
doassert@src/mongo/shell/assert.js:16:14
assert.commandWorked@src/mongo/shell/assert.js:290:5
DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1312:5
printShardingStatus@src/mongo/shell/utils_sh.js:611:13
sh.status@src/mongo/shell/utils_sh.js:78:5
@(shell):1:1


I am running Mongo 3.2 on ubuntu 16.04 platform. It is working fine on MongoDB version 3.0 on ubuntu 14.04 platform. I have reinstalled everything and tried this on new machines too, everything is working fine except sh.status() command.



Thanks.







mongodb sharding






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 '18 at 6:33









Neil Lunn

101k23179187




101k23179187










asked Nov 15 '18 at 6:26









Vikas SainiVikas Saini

3332417




3332417












  • This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

    – Neil Lunn
    Nov 15 '18 at 6:33











  • Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

    – Neil Lunn
    Nov 15 '18 at 6:35

















  • This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

    – Neil Lunn
    Nov 15 '18 at 6:33











  • Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

    – Neil Lunn
    Nov 15 '18 at 6:35
















This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

– Neil Lunn
Nov 15 '18 at 6:33





This question really belongs on dba.stackexchange.com which is the site to use for database administration and configuration questions. StackOverflow is for programming topics only, of which this question is not. Please move your question to the correct site by deleting and reposting.

– Neil Lunn
Nov 15 '18 at 6:33













Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

– Neil Lunn
Nov 15 '18 at 6:35





Also Please also don't "spam tags". Tags on questions are for what the "question is about", and not the "full stack in use for your project". The fortunate thing is most of those tags simply don't exist on dba.stackexchange.com

– Neil Lunn
Nov 15 '18 at 6:35












1 Answer
1






active

oldest

votes


















0














It was becuase notablescan property enabled in my mongo config servers. After disable notablescan, command is working fine. you can check status of notablescan by running this command.



db.adminCommand( getParameter: 1, notablescan: 1 )


Output would be like below if notablescan is enabled.




"notablescan": true,
"ok": 1






share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53313597%2fgetting-exception-on-running-sh-status-command-on-mongodb-sharded-cluster%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














    It was becuase notablescan property enabled in my mongo config servers. After disable notablescan, command is working fine. you can check status of notablescan by running this command.



    db.adminCommand( getParameter: 1, notablescan: 1 )


    Output would be like below if notablescan is enabled.




    "notablescan": true,
    "ok": 1






    share|improve this answer





























      0














      It was becuase notablescan property enabled in my mongo config servers. After disable notablescan, command is working fine. you can check status of notablescan by running this command.



      db.adminCommand( getParameter: 1, notablescan: 1 )


      Output would be like below if notablescan is enabled.




      "notablescan": true,
      "ok": 1






      share|improve this answer



























        0












        0








        0







        It was becuase notablescan property enabled in my mongo config servers. After disable notablescan, command is working fine. you can check status of notablescan by running this command.



        db.adminCommand( getParameter: 1, notablescan: 1 )


        Output would be like below if notablescan is enabled.




        "notablescan": true,
        "ok": 1






        share|improve this answer















        It was becuase notablescan property enabled in my mongo config servers. After disable notablescan, command is working fine. you can check status of notablescan by running this command.



        db.adminCommand( getParameter: 1, notablescan: 1 )


        Output would be like below if notablescan is enabled.




        "notablescan": true,
        "ok": 1







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 22 '18 at 8:21

























        answered Nov 22 '18 at 7:44









        Vikas SainiVikas Saini

        3332417




        3332417





























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f53313597%2fgetting-exception-on-running-sh-status-command-on-mongodb-sharded-cluster%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

            How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

            Darth Vader #20

            Ondo