Reporting Error "Running Jobs" under "Logs"

[sdachen]

Hi Hubitat Community / Staff,

I believe I ran into a possible bug in reporting of "Running Jobs" under "Logs."

As I was investigating for a Hub Load Severe issue (which seems to also have some reporting issues, but it hasn't been isolated yet...) I found that a job to be reported to have run for 27 days

The hub reports the job to have run for 2409050s ~= 27 days but my uptime is only about 5 days due to the need to constantly reboot.

Another odd thing I found was that

The cpuPct is at ~300% which is above 100%. Is this normal?

[ritchierich]

@sdachen

Another odd thing I found was that

@sdachen

The cpuPct is at ~300% which is above 100%.

tagging @thebearmay for the hub information driver state issue

[sdachen]

FWIW, the app displayed changes from one refresh to another

This time I got a different App, but within the uptime of my hub.

Also, both of these apps and functions seems to be some network call. Could there be a bug in how AsyncHttp calls were called at the Hubitat hub level? Ecobee Suite Manager seems to be one of the Apps that'd cause my hub to get to 100% but on the App Stats page, the numbers seems to be pretty normal... There seemed to be some thing happening in the Hubitat JVM not captured at the App Stats page either.

[thebearmay]

Numbers over 100% are possible but it means that you have a number of threads that are awaiting some type of response. Generally where I’ve seen these they tend to be processes that are waiting on a response from an HTTP call.

[sdachen]

Thank you! This seems very consistent with all other findings!