I just noticed that I’m receiving the following in my OpenHab log…
2017-11-03 20:43:13.330 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
How can I perform additional research to find out what is causing this error? I see HTTP so is this an issue with Jetty?
I’m running on 2.2 SNAPSHOT #1072
In looking at the logs I see a pattern…this seems to happening on the hour, every hour.
2017-11-05 04:51:09.909 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
2017-11-05 05:51:23.812 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
2017-11-05 06:51:37.892 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
2017-11-05 07:51:51.746 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
2017-11-05 08:52:06.347 [WARN ] [org.openhab.io.net.http.HttpUtil ] - Method failed: HTTP/1.1 500 Internal Server Error
Any Thoughts??
Assuming you are using the Ecobee binding, it’s a harmless Ecobee token expiration. I get the same errors.
I am using the ecobee binding…thank you!
Wish there was a way to suppress or better correlate to ecobee. When you are looking for issues it’s generic nature makes you want to explore it further.
Squid
I think it’s incorrect for org.openhab.io.net.http.HttpUtil to log anything above DEBUG level and I think it might be a regression that it now does. A utility class like HttpUtil does not know whether a 500 HTTP status code is something that warrants a log entry; rather the code using HttpUtil would be in a position to know if it should be logged, and at what level.
I agree. Actually, the ESH version of HttpUtil only logs debug messages, the warning was only left in the 1.x compatibility layer. I have created https://github.com/openhab/openhab-core/pull/227 to fix this.