Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception "Sync API Umbrella Users and API Backends" Error: Server is required #346

Closed
brylie opened this issue Aug 12, 2015 · 7 comments
Closed

Comments

@brylie
Copy link
Contributor

brylie commented Aug 12, 2015

When starting Meteor on the develop branch, I am getting an error:

Error: Server is required
     at getErrorObject (packages/aldeed:collection2/collection2.js:369:1)
     at [object Object].doValidate (packages/aldeed:collection2/collection2.js:352:1)
     at [object Object].Mongo.Collection.(anonymous function) [as insert] (packages/aldeed:collection2/collection2.js:154:1)
     at app/server/methods/apiBackends.js:15:23
     at Array.forEach (native)
     at Function._.each._.forEach (packages/underscore/underscore.js:105:1)
    at [object Object].Meteor.methods.syncApiBackends (app/server/methods/apiBackends.js:9:9)
     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1617:1)
     at packages/ddp/livedata_server.js:1530:1
     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)

The error seems to be related to the server/methods/apiBackends.js:15:23, which is the syncApiBackends method.

SyncedCron produces the same error, when I comment out the initial Meteor.call("syncApiBackends") in startup.js:16:

Exception "Sync API Umbrella Users and API Backends" Error: Server is required
@brylie
Copy link
Contributor Author

brylie commented Aug 12, 2015

@frenchbread, can you please look into this error? I am not sure what has changed recently to regress the syncApiBackends method.

@brylie brylie added the bug label Aug 12, 2015
@brylie brylie added this to the Sprint 9 milestone Aug 12, 2015
@frenchbread
Copy link
Contributor

@brylie Had the same error. In develop branch it somehow fixed itself after couple of server launches, but in feature/api-config-import, in apiBackend Schema file I updated server and matching fields as optional. This could actually fix develop branch as well. Seems like hotfix needed.

@brylie
Copy link
Contributor Author

brylie commented Aug 12, 2015

Ah, this seems like a bug with API Umbrella then. Or at least, the REST API may not be returning all fields perhaps?

@brylie
Copy link
Contributor Author

brylie commented Aug 12, 2015

@frenchbread the keys server and matching may be invalid. API Umbrella uses servers and url_matches for those fields.

@frenchbread
Copy link
Contributor

@brylie Agree, this could be an error on API Umbrella side. Since everything worked before and suddenly started to crash.

@brylie
Copy link
Contributor Author

brylie commented Aug 12, 2015

Well, it seems to be on our side, since we recently changed the schema required fields while our schema does not match the API Umbrella Backend model.

@brylie
Copy link
Contributor Author

brylie commented Aug 12, 2015

I updated the schema in my open pull request #345. Merging this pull request should hopefully resolve this problem.

@bajiat bajiat closed this as completed Aug 17, 2015
marla-singer pushed a commit that referenced this issue Feb 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants