-
Notifications
You must be signed in to change notification settings - Fork 8
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
Exporter suddenly stop working. #159
Comments
I only glanced over it. Can you possibly paste the entire journal? Or share your targets so I can try to reproduce? I'll look again when I am in front of my computer. |
@kozicpetar I looked again, I am assuming there is a lot more prior to this? Please paste the entire log and please format it with backticks for readability if you do. :) |
Hi @till
|
@kozicpetar Ok, this is helpful. The error messages in the log:
What are they about? Or is msg really empty? Otherwise, can you share the |
|
That looks like:
|
@kozicpetar Thank you! I'll take a look later. That should give us a hint as to why. Probably missed something when I replaced logrus. |
Thank you very much @till Keep waiting on update to implement this exporter. Great job ! |
Display the actual error message returned from the collector. Test for the correct (lower level) error before using it. For: #159
@kozicpetar I made #160 to display the actual error message. Check out the branch and use I am still not sure why that would lead to a crash though, but maybe it helps us get further. |
And maybe add |
@till I can't build from that branch.
I have a lot of errors if I trying to install goreleaser. |
I don't know what lots of errors are. Just install a binary from their repository? You can also look at the config in this repo to see the flags. |
I solved some errors but I get this now:
EDIT:
Do I need to update go locally to 1.20? |
@kozicpetar Yeah, check the go.mod. If you can't update, maybe build in a container? |
@till thank you very much on help. |
Exporter stop wokring again, this is log:
|
@kozicpetar thanks, I'll take a look later. I think this is something in the response of the DNS server that I am not handling correctly. |
@till any chance to solve this soon? Thank you. |
@kozicpetar Tomorrow/Saturday. |
@kozicpetar hey, I wasn't able to replicate the error but I used the opportunity to make additional changes and to add test cases. I think the DNS lookup fails somewhere, but I think I may have covered it now. If you want to try again. Otherwise, if it still fails. Maybe let's get in touch on Twitter or Mastodon so you can give me more config and I'll have a look again? My links are on my profile. |
@till thank you very much. I will test again today. |
Unfortunately, same again. This is error:
Unbound service is ok. Dig works as expected:
|
@kozicpetar I responded on Friday or so, lmk |
I am trying to clean-up the code a little and I am letting it run locally with |
@till Thank you on update. |
I'll keep it open for a bit, can you let me know next week if it continues to work? |
HI @till sure I let you know. For now, working as expected. |
@till Exporter working without problems last 5 days. Thank you ! |
Hi @till |
I can try to do that some time this week or next. |
Display the actual error message returned from the collector. Test for the correct (lower level) error before using it. For: #159
@kozicpetar I merged to |
It’s Petar’s wife,he died on october the 2.Sent from my iPhoneOn 14. 11. 2023., at 15:21, Till! ***@***.***> wrote:
@kozicpetar I merged to main finally. Do you want to rebuild and test again before I cut a release? I am trying to get some docs in before anyway. I think ideally, within November.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@kozicpetar I am sorry to hear this, and my condolences to you. Just in case you are not aware, your response ended up on a public forum/platform. Just in case there's similar email coming through. Till |
I have installed latest release from git.
I set exporter to work as systemd service. This is systemd file:
OS is:
VERSION="22.04.2 LTS (Jammy Jellyfish)"
Service working some time, sometimes several hours, sometimes days or two and suddenly stop working with error:
The text was updated successfully, but these errors were encountered: