Is this normal for Logs/CPU Usage

[Rustybolt]

New feeder to Planefinder. Using a Raspberry Pi 3B+ Debian I've fed (and still feed) to Flightaware for years and am using their dump1090-fa. Also feed to Opensky. Since starting feed to Planefinder, I note CPU usage hovers around 12%, which seems ok, but looking for a sanity check. I also checked the log files and see the following:
2021-09-09 11:23:28.393987 [-] TCP connection established: 192.168.1.146:30005
2021-09-09 11:23:28.393605 [-] Client restarted successfully
2021-09-09 11:23:28.393579 [-] Closed TCP connection: 192.168.1.146:30005
2021-09-09 10:59:08.750478 [-] TCP connection established: 192.168.1.146:30005
2021-09-09 10:59:08.749971 [-] Client restarted successfully
2021-09-09 10:59:08.749921 [-] Closed TCP connection: 192.168.1.146:30005
2021-09-09 10:58:58.744258 [-] TCP connection established: 192.168.1.146:30005
2021-09-09 10:58:58.743771 [-] Client restarted successfully2021-09-09 10:58:58.743721 [-] Closed TCP connection: 192.168.1.146:30005
2021-09-09 10:58:33.845315 [-] TCP connection established: 192.168.1.146:30005
2021-09-09 10:58:33.844813 [-] Client restarted successfully
2021-09-09 10:58:33.844761 [-] Closed TCP connection: 192.168.1.146:30005

And on and on, TCP connection closing, client restarting, reestablishing TCP connection repeatedly every few minutes. Display and feed seems about same as what I feed to Flightaware. Is this normal? If not, what is going on and how do I fix?

 

[Lee Armstrong]

That is more CPU than I would expect in normal operation. That said it looks like it is not connecting to the data feed correctly. That may have a slight increase as it opens and closes the socket.

Check that the IP and port are correct. If this is on the same Pi I would use the loopback address of 127.0.0.1

 

[Rustybolt]

That is more CPU than I would expect in normal operation. That said it looks like it is not connecting to the data feed correctly. That may have a slight increase as it opens and closes the socket.

Check that the IP and port are correct. If this is on the same Pi I would use the loopback address of 127.0.0.1

Thanks. Using the loopback fixed the constant TCP closing and reconnecting issue. CPU dropped a couple percent too. I'm good!