Updated from 1.9 to 1.10.1 and am getting the following error:
/Users/Joe/.meteor/packages/meteor-tool/.1.10.1.1g3oh9r.ivug++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:313
W20200406-13:01:16.483(-4)? (STDERR) throw(ex);
W20200406-13:01:16.483(-4)? (STDERR) ^
W20200406-13:01:16.484(-4)? (STDERR)
W20200406-13:01:16.484(-4)? (STDERR) MongoError: no mongos proxy available
W20200406-13:01:16.484(-4)? (STDERR) at Timeout.<anonymous> (/Users/Joe/.meteor/packages/npm-mongo/.3.7.0.1yux8t1.vzvw++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb/lib/core/topologies/mongos.js:731:28)
W20200406-13:01:16.484(-4)? (STDERR) at listOnTimeout (internal/timers.js:549:17)
W20200406-13:01:16.485(-4)? (STDERR) at processTimers (internal/timers.js:492:7) {
W20200406-13:01:16.485(-4)? (STDERR) name: 'MongoError',
W20200406-13:01:16.485(-4)? (STDERR) [Symbol(mongoErrorContextSymbol)]: {}
W20200406-13:01:16.485(-4)? (STDERR) }
I’m connecting to an external database hosted by compose. As a test:
If I connect to the local db it works fine
Going back to 1.9.2 I’m able to launch, but it breaks at 1.9.3 or higher (1.9.3 provided a different mongo-related error. I can go back and get it if this would help troubleshooting).
So after looking through compose, was reminded that they changed the host format a while back, but was still allowing access using the old version. I guess the new mongo update in 1.9.3 added some level of strictness that no longer allowed this? In any case, works fine now that I’ve updated the host strings. Thanks for your help.
In the Compose dashboard, go into your deployment, and in the Overview tab, take a look at the “Connection Info” section. In there you’ll see how your connection string should look when connecting to the database. If the host section of that string is different than what you’re currently using, change it, and it should work.
The Connection string in the settings is similar to Connection string details from compose. The only changes are the username, password and the database. We are still getting the error MongoNetworkError: failed to connect to server [aws-us-east-1-portal.35.dblayer.com:30339] on first connect [Error: unable to verify the first certificate. Thanks for the reply.
I’d reach out to compose. My host string used to look like yours but drastically changed, no longer having “dblayer” in it, adding my company name into it, etc.
I have seen that. The issue seems to be caused by MONGO_OPLOG_URL connection. If I remove the MONGO_OPLOG_URL connection, it works fine. Thanks for the help.
I have the same issue. I migrated my mongodb and updated it to version 4.2.5. Unfortunately I get the same error. As soon as i deactivate MONGO_OPLOG_URL it works fine.
Due to my mongodb server logs the authetification of oplogger worked fine:
2020-04-07T00:25:05.549+0200 I ACCESS [conn914] Successfully authenticated as principal oplogger on admin from client xx.xx.xx.xx:xxxxx
Maybe there is somethong wrong with my oplog configuration? Although not much I had to do:
replication:
oplogSizeMB: 2048
replSetName: rs0
I use Meteor 1.10.1 with the mongo package 1.9.1. Any ideas?
I couldn’t figure out if you’re answer solved the issue without removing the oplog (since earlier in the thread, that was the solution that others settled on).
Were you able to use your solution and still use oplog?
I also have to upgrade my DB, but disabling oplog is not an option. Downgrading Meteor seems to be a workaround that won’t last for long. Any updates on whether this will be resolved in Meteor, so we can get this working on 10.1?
Thanks for the reply!