Masterwishx Posted August 15, 2022 Share Posted August 15, 2022 i have strang behavior of node exporter in grafana : My server start in the morning in 8:30 then in 10:00 i power on my main comp and then from 13:30-16:30 and 17:15-18:45 it was switched of and this was afected somehow to node exporter ,there is no value in these times in grafana?!? but im using http://192.168.0.199:9100/metrics on server for node exporter . The only thing belong to my main comp that i have remote share on main comp that auto connected by script and not removed when main comp shut down so i have next line : Quote Link to comment
ich777 Posted August 16, 2022 Author Share Posted August 16, 2022 13 hours ago, Masterwishx said: The only thing belong to my main comp that i have remote share on main comp that auto connected by script and not removed when main comp shut down so i have next line : Is something on your PC running which maybe results in a IP conflict on your local network, that's my best guess... Quote Link to comment
Masterwishx Posted August 16, 2022 Share Posted August 16, 2022 12 hours ago, ich777 said: Is something on your PC running which maybe results in a IP conflict on your local network, that's my best guess... Thanks for answer, do you mean server or main PC ? Quote Link to comment
ich777 Posted August 16, 2022 Author Share Posted August 16, 2022 1 hour ago, Masterwishx said: Thanks for answer, do you mean server or main PC ? Maybe the main PC does something that creates a IP address conflict... But that's only a guess... 1 Quote Link to comment
Masterwishx Posted August 17, 2022 Share Posted August 17, 2022 17 hours ago, ich777 said: Maybe the main PC does something that creates a IP address conflict... But that's only a guess... i have adguard app on main comp but dont know how can affect when Main PC is off also its not enabled for 192.168.0.199 aslo founded next when PC is OFF : Quote Link to comment
ich777 Posted August 17, 2022 Author Share Posted August 17, 2022 3 minutes ago, Masterwishx said: i have adguard app on main comp but dont know how can affect when Main PC is off I really can't tell what's going on in your Network... This has to be some kind of network issue, otherwise it would work just fine. Quote Link to comment
Masterwishx Posted August 17, 2022 Share Posted August 17, 2022 8 minutes ago, ich777 said: I really can't tell what's going on in your Network... This has to be some kind of network issue, otherwise it would work just fine. Yes its worked fine befor , Thanks, i will try to find where the problem in network ... 1 Quote Link to comment
Masterwishx Posted August 17, 2022 Share Posted August 17, 2022 5 hours ago, ich777 said: This has to be some kind of network issue, otherwise it would work just fine. Fixed by increasing to scrape_timeout: 15s from default but still need to find why scrape time up to 10s when main PC is offline .. Quote Link to comment
deanosim Posted August 21, 2022 Share Posted August 21, 2022 Has anyone had this problem? I can tell if it's Nvidia Node exporter that's causing it, but I don't run anything else that runs that. and I can't kill any of them without restarting the system because they're in uninterruptible sleep D state, it seems to massively slowdown my server. Quote Link to comment
hoschy Posted August 23, 2022 Share Posted August 23, 2022 still having issues with the fritzbox-plugin when i do it like you posted in your tutorial, i only get a few metrics. not enough for grafana to output something. but when i insert: fritz_additional=-gateway-url http://192.168.0.1:49000 -gateway-luaurl http://192.168.0.1 or fritz_additional=-gateway-url="http://192.168.0.1:49000" -gateway-luaurl="http://192.168.0.1" the service cant be started anymore and, the really strange thing: everytime i try to start the service, my unraid-log gets an entry like this: Quote Aug 23 04:21:28 honas sSMTP[5552]: Creating SSL connection to host Aug 23 04:21:28 honas sSMTP[5552]: SSL connection using TLS_AES_256_GCM_SHA384 Aug 23 04:21:28 honas sSMTP[5552]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials p21-20020a170906141500b00730a234b863sm6815808ejc.77 - gsmtp) im clueless Quote Link to comment
ich777 Posted August 23, 2022 Author Share Posted August 23, 2022 3 hours ago, hoschy said: and, the really strange thing: everytime i try to start the service, my unraid-log gets an entry like this: This is something that can be ignored because the plugin runs a 'at' command every time you start the exporter, I will fix that in a upcoming release so that this message will be not displayed. This message does not harm or cause issues to the function from the exporter itself. 3 hours ago, hoschy said: still having issues with the fritzbox-plugin @sonic6 do you have any thoughts about this? Quote Link to comment
sonic6 Posted August 23, 2022 Share Posted August 23, 2022 13 hours ago, hoschy said: fritz_additional=-gateway-url http://192.168.0.1:49000 -gateway-luaurl http://192.168.0.1 or fritz_additional=-gateway-url="http://192.168.0.1:49000" -gateway-luaurl="http://192.168.0.1" the service cant be started anymore you can try a space between "fritz_additional=" and "-gateway-url="http://192.168.0.1:49000" -gateway-luaurl="http://192.168.0.1"" here is my example: @ich777 maybe you can add this to your tutorial? Quote Link to comment
luk Posted August 24, 2022 Share Posted August 24, 2022 On 7/3/2021 at 4:24 PM, ich777 said: Go to your Docker page and start the Prometheus Docker container: followed your steps, but my docker doesn't start. In Log I see this: panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffe93421eaf, 0xb}, 0x14, {0x39a4ca0, 0xc0007aac80}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:22:13.802Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:22:13.802Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:22:13.802Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:22:13.802Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:22:13.802Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:22:13.802Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:22:13.803Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc6470aeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00014fdb0}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:23:12.884Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:23:12.884Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:23:12.884Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:23:12.884Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:23:12.884Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:23:12.884Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:23:12.884Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc83ecbeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00004cd70}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df what's the issue? Quote Link to comment
ich777 Posted August 24, 2022 Author Share Posted August 24, 2022 1 minute ago, luk said: followed your steps, but my docker doesn't start. In Log I see this: This is actually a issue from the Prometheus container and I would recommend to post on their Support Thread but what I would really recommend is that you go to their Discord because they don't give Support over here on the Unraid Forums what I really don't understand and why there is even a Support Thread here, seems like a users help users thing... 3 minutes ago, luk said: what's the issue? From what I know this is a permission issue and they won't fix it for whatever reason... Nothing I can do about, sorry... 1 Quote Link to comment
JDserver Posted August 29, 2022 Share Posted August 29, 2022 On 8/24/2022 at 1:25 AM, luk said: followed your steps, but my docker doesn't start. In Log I see this: panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffe93421eaf, 0xb}, 0x14, {0x39a4ca0, 0xc0007aac80}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:22:13.802Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:22:13.802Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:22:13.802Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:22:13.802Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:22:13.802Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:22:13.802Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:22:13.803Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc6470aeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00014fdb0}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:23:12.884Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:23:12.884Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:23:12.884Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:23:12.884Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:23:12.884Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:23:12.884Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:23:12.884Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc83ecbeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00004cd70}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df what's the issue? I had the same problem my "fix" was to edit the path like this /mnt/user/appdata/prometheus1/data. just added the 1 to that and Grafana and everything started working. Still need to find the real fix. But now my problem is after changing the yml to my sever IP Prometheus only can find the Localhost:9090 and not the IP of my server in target page. I don't want to add http:// to the yml right? Quote Link to comment
slimshizn Posted September 12, 2022 Share Posted September 12, 2022 (edited) Just tried this out for pihole. Works great, but not with the original dashboard. Found this one on Grafana. https://grafana.com/grafana/dashboards/14283-pi-hole-exporter/ Works better, and has an option to select the datasource. Edit: Had to change the % ads blocked from percentage 0.0 - 1.0 to 0 - 100 Edited September 12, 2022 by slimshizn 1 Quote Link to comment
japka Posted October 11, 2022 Share Posted October 11, 2022 Hi, up until recent Fritzbox exporter plugin was working great. Now I am encountering issue. It shows no data on grafana. This is my metrics dump. Tried removing the plugin, reboot unraid and prometheus, even upgrading unraid, create new fritzbox user but the end result is the same. Quote # HELP fritzbox_exporter_collectErrors Number of collection errors. # TYPE fritzbox_exporter_collectErrors counter fritzbox_exporter_collectErrors 0 # HELP fritzbox_exporter_luaCollectErrors Number of lua collection errors. # TYPE fritzbox_exporter_luaCollectErrors counter fritzbox_exporter_luaCollectErrors 0 # HELP fritzbox_exporter_results_cached Number of results taken from cache. # TYPE fritzbox_exporter_results_cached counter fritzbox_exporter_results_cached{Cache="LUA"} 0 fritzbox_exporter_results_cached{Cache="UPNP"} 0 # HELP fritzbox_exporter_results_loaded Number of results loaded from fritzbox. # TYPE fritzbox_exporter_results_loaded counter fritzbox_exporter_results_loaded{Cache="LUA"} 0 fritzbox_exporter_results_loaded{Cache="UPNP"} 0 # 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"} 1.7308e-05 go_gc_duration_seconds{quantile="0.25"} 1.8979e-05 go_gc_duration_seconds{quantile="0.5"} 2.5063e-05 go_gc_duration_seconds{quantile="0.75"} 3.137e-05 go_gc_duration_seconds{quantile="1"} 8.1214e-05 go_gc_duration_seconds_sum 0.000982348 go_gc_duration_seconds_count 31 # HELP go_goroutines Number of goroutines that currently exist. # TYPE go_goroutines gauge go_goroutines 12 # HELP go_info Information about the Go environment. # TYPE go_info gauge go_info{version="go1.16.3"} 1 # HELP go_memstats_alloc_bytes Number of bytes allocated and still in use. # TYPE go_memstats_alloc_bytes gauge go_memstats_alloc_bytes 6.08772e+06 # 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 8.441024e+07 # 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 1.454808e+06 # HELP go_memstats_frees_total Total number of frees. # TYPE go_memstats_frees_total counter go_memstats_frees_total 184622 # HELP go_memstats_gc_cpu_fraction The fraction of this program's available CPU time used by the GC since the program started. # TYPE go_memstats_gc_cpu_fraction gauge go_memstats_gc_cpu_fraction 1.1457694356162242e-06 # 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 4.931848e+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 6.08772e+06 # 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 5.9392e+07 # 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 6.9632e+06 # HELP go_memstats_heap_objects Number of allocated objects. # TYPE go_memstats_heap_objects gauge go_memstats_heap_objects 10750 # 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 5.9056128e+07 # 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 6.63552e+07 # 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 1.6655119393072672e+09 # 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 195372 # 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 9600 # 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 16384 # 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 133960 # 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 147456 # 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 7.834448e+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.65892e+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 753664 # 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 753664 # HELP go_memstats_sys_bytes Number of bytes obtained from system. # TYPE go_memstats_sys_bytes gauge go_memstats_sys_bytes 7.531828e+07 # HELP go_threads Number of OS threads created. # TYPE go_threads gauge go_threads 13 # 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.36 # HELP process_max_fds Maximum number of open file descriptors. # TYPE process_max_fds gauge process_max_fds 40960 # HELP process_open_fds Number of open file descriptors. # TYPE process_open_fds gauge process_open_fds 11 # HELP process_resident_memory_bytes Resident memory size in bytes. # TYPE process_resident_memory_bytes gauge process_resident_memory_bytes 1.9427328e+07 # 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.66550893858e+09 # HELP process_virtual_memory_bytes Virtual memory size in bytes. # TYPE process_virtual_memory_bytes gauge process_virtual_memory_bytes 1.495437312e+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"} 218 promhttp_metric_handler_requests_total{code="500"} 0 promhttp_metric_handler_requests_total{code="503"} 0 Quote Link to comment
ich777 Posted October 12, 2022 Author Share Posted October 12, 2022 13 hours ago, japka said: up until recent Fritzbox exporter plugin was working great. Did you change something? I got another report from a user which is on Unraid 6.11.1 and uses the latest version from the exporter that it works just fine: 1 Quote Link to comment
japka Posted October 12, 2022 Share Posted October 12, 2022 I have managed to solve it. It was DNS issue. I didn't have fritzbox as my DNS server in unraid. 1 Quote Link to comment
Daxter Posted October 29, 2022 Share Posted October 29, 2022 On 8/24/2022 at 2:25 AM, luk said: followed your steps, but my docker doesn't start. In Log I see this: panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffe93421eaf, 0xb}, 0x14, {0x39a4ca0, 0xc0007aac80}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:22:13.802Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:22:13.802Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:22:13.802Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:22:13.802Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:22:13.802Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:22:13.802Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:22:13.803Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc6470aeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00014fdb0}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df ts=2022-08-24T06:23:12.884Z caller=main.go:495 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-08-24T06:23:12.884Z caller=main.go:539 level=info msg="Starting Prometheus Server" mode=server version="(version=2.38.0, branch=HEAD, revision=818d6e60888b2a3ea363aee8a9828c7bafd73699)" ts=2022-08-24T06:23:12.884Z caller=main.go:544 level=info build_context="(go=go1.18.5, user=root@e6b781f65453, date=20220816-13:23:14)" ts=2022-08-24T06:23:12.884Z caller=main.go:545 level=info host_details="(Linux 5.18.16-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 3 09:41:36 PDT 2022 x86_64 1bc36d8a6aaf (none))" ts=2022-08-24T06:23:12.884Z caller=main.go:546 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-08-24T06:23:12.884Z caller=main.go:547 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-08-24T06:23:12.884Z caller=query_logger.go:90 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffc83ecbeaf, 0xb}, 0x14, {0x39a4ca0, 0xc00004cd70}) /app/promql/query_logger.go:120 +0x3d5 main.main() /app/cmd/prometheus/main.go:601 +0x64df what's the issue? I had this issue, and found the resolution here: You need to change the data directory mapping to this: /prometheus/data <-> /mnt/user/appdata/prometheus/data 1 Quote Link to comment
demechman Posted November 13, 2022 Share Posted November 13, 2022 ts=2022-11-11T13:37:00.687Z caller=main.go:512 level=info msg="No time or size retention was set so using the default time retention" duration=15d ts=2022-11-11T13:37:00.687Z caller=main.go:556 level=info msg="Starting Prometheus Server" mode=server version="(version=2.40.1, branch=HEAD, revision=965274259f993801d63f553639d248588287120b)" ts=2022-11-11T13:37:00.687Z caller=main.go:561 level=info build_context="(go=go1.19.3, user=root@d020f7085e1e, date=20221109-14:30:50)" ts=2022-11-11T13:37:00.687Z caller=main.go:562 level=info host_details="(Linux 5.19.14-Unraid #1 SMP PREEMPT_DYNAMIC Thu Oct 6 09:15:00 PDT 2022 x86_64 81e7b388a98f (none))" ts=2022-11-11T13:37:00.687Z caller=main.go:563 level=info fd_limits="(soft=40960, hard=40960)" ts=2022-11-11T13:37:00.687Z caller=main.go:564 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-11-11T13:37:00.687Z caller=query_logger.go:91 level=error component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied" panic: Unable to create mmap-ed active query log goroutine 1 [running]: github.com/prometheus/prometheus/promql.NewActiveQueryTracker({0x7ffce3958eab, 0xb}, 0x14, {0x3b92b80, 0xc000051590}) /app/promql/query_logger.go:121 +0x3cd main.main() /app/cmd/prometheus/main.go:618 +0x6973 ts=2022-11-11T13:39:13.128Z caller=main.go:468 level=error msg="Error loading config (--config.file=/etc/prometheus/prometheus.yml)" file=/etc/prometheus/prometheus.yml err="parsing YAML file /etc/prometheus/prometheus.yml: \"http://192.168.0.129:9100\" is not a valid hostname" I just attempted to install Grafana/Prometheus using the guide on the blog/forum and I am unable to start the docker for Prometheus which is the first step. Looks like some kind of permission error? What specifically needs done to make this work? Running 6.11.1 Quote Link to comment
ich777 Posted November 14, 2022 Author Share Posted November 14, 2022 6 hours ago, demechman said: I just attempted to install Grafana/Prometheus using the guide on the blog/forum and I am unable to start the docker for Prometheus which is the first step. Looks like some kind of permission error? What specifically needs done to make this work? Running 6.11.1 I would recommend that you ask that question on the Prometheus Support Thread because I‘m not the maintainer from that container. Quote Link to comment
Masterwishx Posted November 27, 2022 Share Posted November 27, 2022 (edited) @ich777 can i use Afterburner exporter for more than 1 PC (IP)? Edited November 27, 2022 by Masterwishx Quote Link to comment
ich777 Posted November 27, 2022 Author Share Posted November 27, 2022 2 hours ago, Masterwishx said: @ich777 can i use Afterburner exporter for more than 1 PC (IP)? Nope, only one PC is supported. 1 Quote Link to comment
Masterwishx Posted November 28, 2022 Share Posted November 28, 2022 19 hours ago, ich777 said: Nope, only one PC is supported. OK, got it. 1 Quote Link to comment
Recommended Posts
Posted by SpencerJ,
1 reaction
Go to this post
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.