HttpChannel warning - /system/gateway {}

Ignition
1

I’ve just started getting a lot of these errors in the wrapper.log.
I can’t work out what has changed in the project that may be causing them.
Does anyone know what they mean or where I need to look to fix them?

Using version 8.0.6

INFO   | jvm 1    | 2020/01/13 09:07:16 | W [o.e.j.s.HttpChannel           ] [22:07:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:08:46 | W [o.e.j.s.HttpChannel           ] [22:08:46]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:09:16 | W [o.e.j.s.HttpChannel           ] [22:09:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:11:16 | W [o.e.j.s.HttpChannel           ] [22:11:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:11:36 | W [o.e.j.s.HttpChannel           ] [22:11:36]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:12:56 | W [o.e.j.s.HttpChannel           ] [22:12:56]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:13:56 | W [o.e.j.s.HttpChannel           ] [22:13:56]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:14:26 | W [o.e.j.s.HttpChannel           ] [22:14:26]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:15:46 | W [o.e.j.s.HttpChannel           ] [22:15:46]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:16:16 | W [o.e.j.s.HttpChannel           ] [22:16:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:17:16 | W [o.e.j.s.HttpChannel           ] [22:17:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:21:56 | W [o.e.j.s.HttpChannel           ] [22:21:56]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:24:06 | W [o.e.j.s.HttpChannel           ] [22:24:06]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:24:16 | W [o.e.j.s.HttpChannel           ] [22:24:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:24:36 | W [o.e.j.s.HttpChannel           ] [22:24:36]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:27:16 | W [o.e.j.s.HttpChannel           ] [22:27:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:31:26 | W [o.e.j.s.HttpChannel           ] [22:31:26]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:33:46 | W [o.e.j.s.HttpChannel           ] [22:33:46]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:34:46 | W [o.e.j.s.HttpChannel           ] [22:34:46]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:36:06 | W [o.e.j.s.HttpChannel           ] [22:36:06]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:36:26 | W [o.e.j.s.HttpChannel           ] [22:36:26]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:37:16 | W [o.e.j.s.HttpChannel           ] [22:37:16]: /system/gateway {} 
INFO   | jvm 1    | 2020/01/13 09:37:36 | W [o.e.j.s.HttpChannel           ] [22:37:36]: /system/gateway {}
2

Hi David,
I have recently started receiving these errors in my gateway log. We have had our gateway running since 12/2019 on version 8.0.6 and we just started getting these. I have added a snip of our log file to see if this is the same waring you were getting and if you found the root cause. Thanks…

image
image926×169 7.41 KB

3

Hi mhicks,
Looks like the same error. Unfortunately I can’t remember how I fixed it. I’ve upgraded to a more recent version and that may have helped.

4

Thank you @DavidWisely . If you happen to remember, please let me know. FYI, we had a short period of time where we were getting those warnings but now they seem to have subsided. Crazy, Right?

5

You can try turning HttpChannel to DEBUG, which should log the stacktrace of the errors (be wary of performance implications if you do):

Maybe your IT group is running a network scanning utility periodically to look for vulnerable HTTP servers in the network?

1 Like
6

Thank you @PGriffith I will contact them. Strangely enough, I have not had that error pop up since the original post.

7

Good Morning… I wanted to add another comment to this thread in case anyone else has this same problem. I did speak with our IT department and they were running some vulnerability scans during those time frames in December. Since they completed, we have not had those errors again. Thanks for help pointing us in the right direction.

1 Like