-
Notifications
You must be signed in to change notification settings - Fork 51
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
Getting messages "was collected before with the same name and label values" #135
Comments
@Zubrania Do you have any information about your cluster configuration? Is this happening on all nodes, or just some of them? Also, what version of Lustre are you using? Older versions are pretty tied to the 1.0.0 release that we have. |
@joehandzik The cluster consists of of 2 mgs/mds servers and 4 oss servers |
I'm also seeing this with lustre_version 2.10.4 RHEL 7.5.
And from an mdt.
I'm running the exporter with the following command. It was built today from git source today in the golang:1.9-stretch docker image. (Docker was only used for building) |
I have noticed that the metric label is |
I'm also seeing this with lustre_version 2.12.0 RHEL 7.5.But it was seen in MDS node,the OSS node is normal |
@wutzx Have you solved this problem? |
@ldd91 Your clone https://github.com/wutzx/lustre_exporter with my PR, and build it. |
@wutzx I clone your PR,and build it ,but met an error
To request an update for a vendored linter file an issue at: WARNING: deadline exceeded by linter vetshadow (try increasing --deadline) |
Your can execute `make build` to skip linter checking.
ldd91 <notifications@github.com> 于2019年3月21日周四 下午6:00写道:
… @wutzx <https://github.com/wutzx> I clone your PR,and exec make ,but met
an error
***@***.*** lustre_exporter]# make
formatting code
linting code
WARNING: Linters are now vendored by default, --update ignored. The
original
behaviour can be re-enabled with --no-vendored-linters.
To request an update for a vendored linter file an issue at:
https://github.com/alecthomas/gometalinter/issues/new
WARNING: deadline exceeded by linter vetshadow (try increasing --deadline)
WARNING: deadline exceeded by linter varcheck (try increasing --deadline)
WARNING: deadline exceeded by linter interfacer (try increasing --deadline)
make: *** [gometalinter] Error 2
***@***.*** lustre_exporter]# ll
total 388
-rw-r--r-- 1 root root 18526 Mar 21 17:51 CHANGELOG.md
-rw-r--r-- 1 root root 2428 Mar 21 17:51 Gopkg.lock
-rw-r--r-- 1 root root 731 Mar 21 17:51 Gopkg.toml
-rw-r--r-- 1 root root 11357 Mar 21 17:51 LICENSE
-rw-r--r-- 1 root root 6488 Mar 21 17:51 lustre_exporter.go
-rw-r--r-- 1 root root 312818 Mar 21 17:51 lustre_exporter_test.go
-rw-r--r-- 1 root root 2051 Mar 21 17:51 Makefile
drwxr-xr-x 4 root root 4096 Mar 21 17:51 proc
-rw-r--r-- 1 root root 2896 Mar 21 17:51 README.md
drwxr-xr-x 2 root root 4096 Mar 21 17:51 sources
drwxr-xr-x 3 root root 4096 Mar 21 17:51 sys
drwxr-xr-x 2 root root 4096 Mar 21 17:51 systemd
drwxr-xr-x 5 root root 4096 Mar 21 17:51 vendor
-rw-r--r-- 1 root root 6 Mar 21 17:51 VERSION
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJBTwVVix7866OiLH5LMfTFDcDBwq8h0ks5vY1gigaJpZM4TTTh7>
.
|
@wutzx Thank you,i tried and it works |
Hi, I still have this problem using commit 6177537, running 2.10.5 on CentOS 7.5. Is there any fix for this problem? Thanks, |
@lszentannai You can try my fork https://github.com/wutz/lustre_exporter |
@wutz thanks for quick reply. I did try your fork too, with the same result. |
You can execute |
it looks like it's not matching the last jobid I get the same messages again, like:
|
Situation has been improved for jobstats that do not have any UID set...
|
Hello
Getting the messages like "was collected before with the same name and label values" in /var/log/messages and the file is constantly growing
[root]# lustre_exporter --version
lustre_exporter, version 2.0.0 (branch: HEAD, revision: 6177537)
build user: prometheus@rc-lustre-oss-2.dev.net
build date: 20171205-22:27:17
go version: go1.8.3
The text was updated successfully, but these errors were encountered: