Service Install Not Reading All Sensors #153
Comments
|
Perchance do you have an AMD GPU? Some have reported that their AMD GPU sensors disappear on wake. This shouldn't effect any OhmGaphite users, but if this is occurring for you, I can upload a tentative release here to see if it helps. If not, then we'll have to do some more digging, as it sounds like you're doing everything correct. Do the GPU sensors initially show up as a service and then are removed or never show up at all? If the latter, there should be a log: `OhmGraphite.log, it'll contain lines like: Compare the sensors that are logged when executing Also search the log for any "ERROR" lines. |
|
I do have an AMD GPU. It's an RX590 if that helps. Last night while I was debugging I noticed that the sensors for the GPU showed up in the logs when I ran the Right now the only way to get the GPU data into my influx server is to manually start the |
|
See attached. Try it out and see if your issue is fixed. 🤞 |
|
Sadly no dice still. :( Log when started from Powershell: |
|
Logs when started from Service: |
|
Thank you for the logs! They very clearly show the 8 missing GPU sensors when running as a service. I'm not sure why this would be. Some things that I'm curious about:
|
|
LibreHardwareMonitor shows the GPU temps correctly. I moved the I also tried running it as the same user as I am in Powershell, but it's still not pulling GPU sensors. Any thoughts on where to go from here? |
|
I talked to some people who are smarter than me and one of the suggestions is to try checking "Allow service to interact with desktop"
Seems like the root cause is that (for a yet unknown reason) windows is blocking access to the GPU from window services. Looks like plenty of people have this issue:
I do not know why GPU sensors for me and not for you (you'd think that if windows restricted GPU access from services that I wouldn't be able to see GPU sensor data either) 🤔 Let me know if this works! |
|
Sadly no dice on clicking the check box either. :( |
|
Hmm, I'm running out of ideas. What version of Windows do you happen to be running? |
|
I'm running Version 10.0.18363 Build 18363 |
|
Hmm yeah that is a recent build of windows. I'll leave this open for now, but I don't have any further steps for you. It may just boil down to the AMD's display driver being inaccessible to session 0 . |
|
I was able to get this working with a workaround. :) Slightly annoying as I have to click "okay" every time my computer starts, but it works and I don't have gaps now. Working with a powershell guru buddy of mine to try and get around the having to click "okay" every time as well. Workaround: Start a scheduled task every time my user logs in. The actual scheduled task is: And the contents of
|
|
Oh wow that's an amazing idea! I wonder if it's possible to alternatively place a Keeps us informed with whatever you discover! I'll add it to the docs so that future users don't have to struggle. |
|
Not only wrong GPU memory. This (surge) is when switching from Service to direct run-command:
I also notice that seemingly it reports correctly in service mode on another machine that has another configuration. So this error will be "fun" to identify. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
If i run the executable directly from power shell all of my sensors are picked up and log into influx and Grafana. However if i install as a service, some of the sensors like GPU activity and temp stop getting logged.
Is there a way to install the service and run it as an admin? I looked but couldn’t figure it out last night.
The text was updated successfully, but these errors were encountered: