deploy docker success, but no pbs metrics in http://192.168.31.158:9111/metrics, what's wrong? #74

xinmans · 2024-11-23T14:26:58Z

xinmans
Nov 23, 2024

# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 0
go_gc_duration_seconds{quantile="0.25"} 0
go_gc_duration_seconds{quantile="0.5"} 0
go_gc_duration_seconds{quantile="0.75"} 0
go_gc_duration_seconds{quantile="1"} 0
go_gc_duration_seconds_sum 0
go_gc_duration_seconds_count 0
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 6
# HELP go_info Information about the Go environment.
# TYPE go_info gauge
go_info{version="go1.22.9"} 1
# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
# TYPE go_memstats_alloc_bytes gauge
go_memstats_alloc_bytes 218496
# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
# TYPE go_memstats_alloc_bytes_total counter
go_memstats_alloc_bytes_total 218496
# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
# TYPE go_memstats_buck_hash_sys_bytes gauge
go_memstats_buck_hash_sys_bytes 7695
# HELP go_memstats_frees_total Total number of frees.
# TYPE go_memstats_frees_total counter
go_memstats_frees_total 0
# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
# TYPE go_memstats_gc_sys_bytes gauge
go_memstats_gc_sys_bytes 1.40032e+06
# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use.
# TYPE go_memstats_heap_alloc_bytes gauge
go_memstats_heap_alloc_bytes 218496
# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
# TYPE go_memstats_heap_idle_bytes gauge
go_memstats_heap_idle_bytes 2.12992e+06
# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use.
# TYPE go_memstats_heap_inuse_bytes gauge
go_memstats_heap_inuse_bytes 1.507328e+06
# HELP go_memstats_heap_objects Number of allocated objects.
# TYPE go_memstats_heap_objects gauge
go_memstats_heap_objects 484
# HELP go_memstats_heap_released_bytes Number of heap bytes released to OS.
# TYPE go_memstats_heap_released_bytes gauge
go_memstats_heap_released_bytes 2.12992e+06
# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system.
# TYPE go_memstats_heap_sys_bytes gauge
go_memstats_heap_sys_bytes 3.637248e+06
# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection.
# TYPE go_memstats_last_gc_time_seconds gauge
go_memstats_last_gc_time_seconds 0
# HELP go_memstats_lookups_total Total number of pointer lookups.
# TYPE go_memstats_lookups_total counter
go_memstats_lookups_total 0
# HELP go_memstats_mallocs_total Total number of mallocs.
# TYPE go_memstats_mallocs_total counter
go_memstats_mallocs_total 484
# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures.
# TYPE go_memstats_mcache_inuse_bytes gauge
go_memstats_mcache_inuse_bytes 12000
# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system.
# TYPE go_memstats_mcache_sys_bytes gauge
go_memstats_mcache_sys_bytes 15600
# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures.
# TYPE go_memstats_mspan_inuse_bytes gauge
go_memstats_mspan_inuse_bytes 54080
# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system.
# TYPE go_memstats_mspan_sys_bytes gauge
go_memstats_mspan_sys_bytes 65280
# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place.
# TYPE go_memstats_next_gc_bytes gauge
go_memstats_next_gc_bytes 4.194304e+06
# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations.
# TYPE go_memstats_other_sys_bytes gauge
go_memstats_other_sys_bytes 1.221649e+06
# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator.
# TYPE go_memstats_stack_inuse_bytes gauge
go_memstats_stack_inuse_bytes 557056
# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator.
# TYPE go_memstats_stack_sys_bytes gauge
go_memstats_stack_sys_bytes 557056
# HELP go_memstats_sys_bytes Number of bytes obtained from system.
# TYPE go_memstats_sys_bytes gauge
go_memstats_sys_bytes 6.904848e+06
# HELP go_threads Number of OS threads created.
# TYPE go_threads gauge
go_threads 6
# HELP pbs_up Was the last query of PBS successful.
# TYPE pbs_up gauge
pbs_up 0
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 0.05
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 10
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 7.68e+06
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.73237180894e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 1.261826048e+09
# HELP process_virtual_memory_max_bytes Maximum amount of virtual memory available in bytes.
# TYPE process_virtual_memory_max_bytes gauge
process_virtual_memory_max_bytes 1.8446744073709552e+19
# HELP promhttp_metric_handler_requests_in_flight Current number of scrapes being served.
# TYPE promhttp_metric_handler_requests_in_flight gauge
promhttp_metric_handler_requests_in_flight 1
# HELP promhttp_metric_handler_requests_total Total number of scrapes by HTTP status code.
# TYPE promhttp_metric_handler_requests_total counter
promhttp_metric_handler_requests_total{code="200"} 0
promhttp_metric_handler_requests_total{code="500"} 0
promhttp_metric_handler_requests_total{code="503"} 0

therus000 · 2024-12-03T06:27:28Z

therus000
Dec 3, 2024

i got same issue!
any fix?

0 replies

janfuhrer · 2024-12-27T15:51:16Z

janfuhrer
Dec 27, 2024
Maintainer

Hi @xinmans, can you provide more information?
Have you already enabled debug logs and looked at them?

0 replies

xinmans · 2024-12-29T01:35:17Z

xinmans
Dec 29, 2024
Author

Hi @xinmans, can you provide more information?

Have you already enabled debug logs and looked at them?

how to enable debug logs？

0 replies

janfuhrer · 2025-01-02T14:39:53Z

janfuhrer
Jan 2, 2025
Maintainer

Please read the README.md carefully.
You can either set the flag -pbs.loglevel=debug or the environment variable PBS_LOGLEVEL=debug.

5 replies

xinmans Jan 3, 2025
Author

pbs-exporter | 2025/01/03 05:58:49 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 05:58:49 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 05:58:49 Get "https://192.168.31.64:8007/api2/json/status/datastore-usage": tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, not 192.168.31.64

xinmans Jan 3, 2025
Author

after set PBS_INSECURE=true

pbs-exporter | 2025/01/03 06:04:23 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:23 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:26 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:26 ERROR: duplicate metrics collector registration attempted
pbs-exporter | 2025/01/03 06:04:26 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:27 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:29 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:29 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:29 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:30 ERROR: duplicate metrics collector registration attempted
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:30 ERROR: duplicate metrics collector registration attempted
pbs-exporter | 2025/01/03 06:04:30 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:31 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:31 ERROR: duplicate metrics collector registration attempted
pbs-exporter | 2025/01/03 06:04:31 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:04:32 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:33 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:33 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:33 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:04:34 ERROR: Status code 401 returned from endpoint: https://192.168.31.64:8007

xinmans Jan 3, 2025
Author

ERROR: duplicate metrics collector registration attempted

coz deploy 2 docker instance， stop one and watch the logs。。。。

xinmans Jan 3, 2025
Author

pbs-exporter | 2025/01/03 06:17:31 INFO: Metrics path: /metrics
pbs-exporter | 2025/01/03 06:19:15 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:15 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:19:15 DEBUG: Status code 200 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:15 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/nodes/localhost/status
pbs-exporter | 2025/01/03 06:19:15 ERROR: Status code 403 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:46 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:46 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:19:46 DEBUG: Status code 200 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:46 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/nodes/localhost/status
pbs-exporter | 2025/01/03 06:19:46 ERROR: Status code 403 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:47 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:47 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:19:47 DEBUG: Status code 200 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:47 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/nodes/localhost/status
pbs-exporter | 2025/01/03 06:19:47 ERROR: Status code 403 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:48 DEBUG: Using connection endpoint https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:48 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/status/datastore-usage
pbs-exporter | 2025/01/03 06:19:48 DEBUG: Status code 200 returned from endpoint: https://192.168.31.64:8007
pbs-exporter | 2025/01/03 06:19:48 DEBUG: Request URL: https://192.168.31.64:8007/api2/json/nodes/localhost/status
pbs-exporter | 2025/01/03 06:19:48 ERROR: Status code 403 returned from endpoint: https://192.168.31.64:8007

how to fix？

xinmans Jan 3, 2025
Author

add the privilege for the account， status normal。thanks。

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

deploy docker success, but no pbs metrics in http://192.168.31.158:9111/metrics, what's wrong? #74

{{title}}

Replies: 4 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

deploy docker success, but no pbs metrics in http://192.168.31.158:9111/metrics, what's wrong? #74

xinmans Nov 23, 2024

Replies: 4 comments · 5 replies

therus000 Dec 3, 2024

janfuhrer Dec 27, 2024 Maintainer

xinmans Dec 29, 2024 Author

janfuhrer Jan 2, 2025 Maintainer

xinmans Jan 3, 2025 Author

xinmans Jan 3, 2025 Author

xinmans Jan 3, 2025 Author

xinmans Jan 3, 2025 Author

xinmans Jan 3, 2025 Author

xinmans
Nov 23, 2024

Replies: 4 comments 5 replies

therus000
Dec 3, 2024

janfuhrer
Dec 27, 2024
Maintainer

xinmans
Dec 29, 2024
Author

janfuhrer
Jan 2, 2025
Maintainer

xinmans Jan 3, 2025
Author

xinmans Jan 3, 2025
Author

xinmans Jan 3, 2025
Author

xinmans Jan 3, 2025
Author

xinmans Jan 3, 2025
Author