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

Metrics stop being updated after VM's Runtime error #56

Closed
AlexRRR opened this issue Mar 1, 2017 · 2 comments
Closed

Metrics stop being updated after VM's Runtime error #56

AlexRRR opened this issue Mar 1, 2017 · 2 comments
Assignees

Comments

@AlexRRR
Copy link

AlexRRR commented Mar 1, 2017

Hello,

We are currently having problems similar #50 where mtails remains unresponsive, if we check out commit 39de9dd things fail but still mtail is able to keep working.

My questions is why:

Am I missing something? The latest commit still fails for me making mtail unusable as it will run for only a minute or so and then die.

Cheers

@jaqx0r
Copy link
Contributor

jaqx0r commented Jun 26, 2017

I got confused as to what the flag is for, and why the fix fixed, that's why I reverted it. I'm reapplyiung the fix, with a comment explaining it to msyelf.

@jaqx0r jaqx0r self-assigned this Jun 26, 2017
jaqx0r added a commit that referenced this issue Jun 26, 2017
subsequent lines can be handled.  This is not a mechanism for aborting a
program due to internal error, so comment the field as so.

Issue: #50, #66, #56
@jaqx0r
Copy link
Contributor

jaqx0r commented Jun 26, 2017

Please try again now I've reverted the reversion.

I think the triggering event you are seeing is that the matching program is unable to parse the line of text, so please read the info logs (--logtostderr flag to enable to stderr) to see why your program is failing.

@jaqx0r jaqx0r closed this as completed Jun 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants