ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    App Crashing Error

    SodiumSuite
    2
    10
    1.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      WLS-ITGuy
      last edited by

      Went to check my assets and got this:

      
      
      /opt/.meteor/packages/meteor-tool/.1.5.4.12u8t06++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:313
      						throw(ex);
      						^
      MongoError: failed to connect to server [localhost:27017] on first connect [MongoError: connect ECONNREFUSED 127.0.0.1:27017]
          at Object.Future.wait (/opt/.meteor/packages/meteor-tool/.1.5.4.12u8t06++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:449:15)
          at new MongoConnection (packages/mongo/mongo_driver.js:210:27)
          at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
          at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:10)
          at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
          at new Mongo.Collection (packages/mongo/collection.js:99:40)
          at AccountsServer.AccountsCommon (packages/accounts-base/accounts_common.js:23:18)
          at new AccountsServer (packages/accounts-base/accounts_server.js:18:5)
          at meteorInstall.node_modules.meteor.accounts-base.server_main.js (packages/accounts-base/server_main.js:9:12)
          at fileEvaluate (packages/modules-runtime.js:333:9)
          - - - - -
          at [object Object].<anonymous> (/opt/.meteor/packages/npm-mongo/.2.2.30.114py23++os+web.browser+web.cordova/npm/node_modules/mongodb-core/lib/topologies/server.js:329:35)
          at emitOne (events.js:77:13)
          at [object Object].emit (events.js:169:7)
          at [object Object].<anonymous> (/opt/.meteor/packages/npm-mongo/.2.2.30.114py23++os+web.browser+web.cordova/npm/node_modules/mongodb-core/lib/connection/pool.js:280:12)
          at [object Object].g (events.js:260:16)
          at emitTwo (events.js:87:13)
          at [object Object].emit (events.js:172:7)
          at Socket.<anonymous> (/opt/.meteor/packages/npm-mongo/.2.2.30.114py23++os+web.browser+web.cordova/npm/node_modules/mongodb-core/lib/connection/connection.js:187:49)
          at Socket.g (events.js:260:16)
          at emitOne (events.js:77:13)
      Exited with code: 1
      Your application is crashing. Waiting for file change.
      
      1 Reply Last reply Reply Quote 1
      • S
        scottalanmiller
        last edited by

        Yes, sorry just saw this, there was a database crash earlier in the day. It's fine now (and has been for most of the day.) The DB just went down but the app stayed up giving that error message.

        1 Reply Last reply Reply Quote 1
        • W
          WLS-ITGuy
          last edited by

          I'm seeing a lot more of machines that aren't mine.

          S 1 Reply Last reply Reply Quote 0
          • S
            scottalanmiller @WLS-ITGuy
            last edited by

            @wls-itguy said in App Crashing Error:

            I'm seeing a lot more of machines that aren't mine.

            that would explain why we suddenly saw so many pages of data... oh boy, lol.

            @QuixoticJeremy

            He built a new subscriptions model last night to handle the volume. I'm guessing something got missed.

            1 Reply Last reply Reply Quote 0
            • S
              scottalanmiller
              last edited by

              @QuixoticJeremy has seen it and is on the case.

              1 Reply Last reply Reply Quote 0
              • S
                scottalanmiller
                last edited by

                Check now, should be all good.

                W 1 Reply Last reply Reply Quote 0
                • W
                  WLS-ITGuy @scottalanmiller
                  last edited by

                  @scottalanmiller said in App Crashing Error:

                  Check now, should be all good.

                  Looks good now.

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    scottalanmiller @WLS-ITGuy
                    last edited by

                    @wls-itguy said in App Crashing Error:

                    @scottalanmiller said in App Crashing Error:

                    Check now, should be all good.

                    Looks good now.

                    Sweet 🙂

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      WLS-ITGuy @scottalanmiller
                      last edited by

                      @scottalanmiller said in App Crashing Error:

                      @wls-itguy said in App Crashing Error:

                      @scottalanmiller said in App Crashing Error:

                      Check now, should be all good.

                      Looks good now.

                      Sweet 🙂

                      Although, none of my machines have checked in since May 30.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        scottalanmiller @WLS-ITGuy
                        last edited by

                        @wls-itguy said in App Crashing Error:

                        @scottalanmiller said in App Crashing Error:

                        @wls-itguy said in App Crashing Error:

                        @scottalanmiller said in App Crashing Error:

                        Check now, should be all good.

                        Looks good now.

                        Sweet 🙂

                        Although, none of my machines have checked in since May 30.

                        Yeah, I have a thread about that. That's not Sodium proper, it's the underlying SaltMaster isn't working. They've got a bug in the 1803 release that is causing issues.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post