Reputation: 12285
I know about console.log, but does meteor keep a separate internal log for various errors?
I don't see any useful response from the check()
function.
to the client, it will appear only as Meteor.Error(400, "Match Failed"); the failure details will be written to the server logs but not revealed to the client.
which is what i get but no error in the server log, that i can see. perhaps just when the app is deployed to a production env the logging behavior changes? on an osx machine are there any other system level logs? I don't see anything in /var/log/
Thanks!
Upvotes: 2
Views: 731
Reputation: 64312
The documentation is incorrect. In v0.8.3, check
does not log failures anywhere. This is being fixed in the next version of meteor as seen here:
When a call to match fails in a method or subscription, log the failure on the server. (This matches the behavior described in our docs)
Upvotes: 1
Reputation: 5273
Logs are not stored locally, they are printed to stdout
or stderr
.
You can store those logs using command:
meteor > logs.txt
and then also have live-preview using:
tail -f logs.txt
If you want to do that in one line, then:
meteor > logs.txt | tail -f logs.txt
Upvotes: 3