infiniband_exporter icon indicating copy to clipboard operation
infiniband_exporter copied to clipboard

err="Unable to extract names using regexp"

Open alex0com opened this issue 1 year ago • 2 comments

Hi, We've been using the rdma/opensm for the longest time and a lot of the monitoring tools haven't worked with it. We're playing around with MOFED OpenSM and thought I'd give this one a try but I'm still getting similar errors when starting infiniband_exporter and querying the data. I'm not sure what's causing the regex to not work on these.

caller=ibnetdiscover.go:178 level=error collector=ibnetdiscover msg="Unable to parse names" err="Unable to extract names using regexp" type=SW guid=0x0002c9020040f160 line="SW 478 22 0x0002c9020040f160 4x QDR 'Infiniscale-IV Mellanox Technologies'" caller=ibnetdiscover.go:98 level=error collector=ibnetdiscover msg="Error executing ibnetdiscover" err="Unable to extract names using regexp" caller=infiniband_exporter.go:53 level=error msg="Error collecting ports with ibnetdiscover" err="Unable to extract names using regexp"

opensm-5.7.2.MLNX20201014 infiniband-diags-5.6.0.MLNX20200211

Thanks for any help!

alex0com avatar Dec 04 '23 12:12 alex0com

The error reason is that the name contains spaces, which has been resolved in v0.6.0

3th1nk avatar Dec 05 '23 12:12 3th1nk

Hi, I just tried v0.6.0 (infiniband_exporter-0.6.0.linux-amd64) but it looks to have the same error

ts=2023-12-05T17:23:30.701Z caller=ibnetdiscover.go:178 level=error collector=ibnetdiscover msg="Unable to parse names" err="Unable to extract names using regexp" type=SW guid=0x0002c9020040f160 line="SW 478 22 0x0002c9020040f160 4x QDR 'Infiniscale-IV Mellanox Technologies'" ts=2023-12-05T17:23:30.702Z caller=ibnetdiscover.go:98 level=error collector=ibnetdiscover msg="Error executing ibnetdiscover" err="Unable to extract names using regexp" ts=2023-12-05T17:23:30.702Z caller=infiniband_exporter.go:53 level=error msg="Error collecting ports with ibnetdiscover" err="Unable to extract names using regexp"

Thank you!

alex0com avatar Dec 05 '23 17:12 alex0com

This should have been solved with #18 and released with 0.7.0 but latest is 0.9.0 so should be able to run 0.9.0 and have this fix.

treydock avatar Jun 04 '24 15:06 treydock