tmo-monitor
tmo-monitor copied to clipboard
highvolt-dev
Dockerized version
FYI, I created a Docker container version of your tool at https://github.com/hugoh/docker-tmo-monitor. The image is published at https://hub.docker.com/r/hugohh/tmo-monitor.
It's been working fine for me. I'm happy to provide a pull request. It will entail Docker Hub and GitHub Actions to perform the automated builds.
Thank you for your tool.
Nice work, @hugoh
Thank you for sharing. I'm happy to integrate your work into the project. For some users, docker will be an easier way to use the script, while others can run it natively on the platform of their choice.
I'm running the docker version on my Truenas NAS without issue. It's simplified things for me as the pi I was using gets rebooted from time to time due to the other tasks I've given it.
Thank you @highvolt-dev for the awesome software and @hugoh for the helpful Docker image :)
@highvolt-dev Are you still thinking about incorporating the Dockerfile and entrypoint script into this repo, or would you add a link to https://github.com/hugoh/docker-tmo-monitor in the README file? Hopefully more people can decide if they want to use Docker to run this :)
My Dockerized version is out-of-date at this point as I am running the tool in a non-Dockerized environment. So, merging an up-to-date version in this upstream repo makes the most sense.
@jiehanzheng @hugoh I am still interested in integrating this work into the project so it can be maintained
@famewolf I just setup docker on my raspberry pi last weekend, hoping to work on containerizing it soon
Great news! I'm running @hugoh's one which is about a year out of date and I'm occasionally running into issues where I THINK it's rebooting the router multiple times because it's not back up in time for the next check. I've had to manually pull the plug on gateway a few times on a fairly regular basis recently....I could just be having bad internet connections with t-mobile though.
Here's an updated version of hugo's Dockerfile which will work with the latest version of your monitor. All that was needed was copying the tmo-monitor.py from the bin directory up to /tmo-monitor so it could be found. I built the image, saved it to a tar file, copied the tar file to my truenas server and loaded the image into docker then modified my docker app to use the local copy instead of hugo's.
< 2023-05-04 05:26:00.544670+00:00Script configuration: 2023-05-04 05:26:00.544747+00:00Gateway model: NOK5G21 2023-05-04 05:26:00.544760+00:00Connectivity check: 2023-05-04 05:26:00.544769+00:00Mode: ping 2023-05-04 05:26:00.544800+00:00Http check: 2023-05-04 05:26:00.544812+00:00Target: https://google.com/generate_204 2023-05-04 05:26:00.544820+00:00Status Code: 204 2023-05-04 05:26:00.544827+00:00Ping configuration: 2023-05-04 05:26:00.544833+00:00Host: google.com 2023-05-04 05:26:00.544841+00:00Count: 3 2023-05-04 05:26:00.544856+00:00Interval: 1 2023-05-04 05:26:00.544864+00:00Protocol: IPv4 2023-05-04 05:26:00.544871+00:00Connection configuration: 2023-05-04 05:26:00.544879+00:00Primary band: ['B66'] 2023-05-04 05:26:00.544886+00:00Secondary band: ['n71'] 2023-05-04 05:26:00.544899+00:00Reboot settings: 2023-05-04 05:26:00.544908+00:00Reboot now: False 2023-05-04 05:26:00.544916+00:00Skip reboot: False 2023-05-04 05:26:00.544924+00:00Min uptime: 90 2023-05-04 05:26:00.544931+00:00Reboot on: ping 2023-05-04 05:26:00.544939+00:00General settings: 2023-05-04 05:26:00.544954+00:00Log file: 2023-05-04 05:26:00.544965+00:00Log all: False 2023-05-04 05:26:00.544974+00:00Log delta: False 2023-05-04 05:26:00.544982+00:00Log to syslog: False 2023-05-04 05:26:00.544991+00:002023-05-04T05:26:00.544991037Z 2023-05-04 05:26:00.544999+00:00PING google.com (142.251.167.100) 56(84) bytes of data. 2023-05-04 05:26:00.545032+00:0064 bytes from ww-in-f100.1e100.net (142.251.167.100): icmp_seq=1 ttl=48 time=68.7 ms 2023-05-04 05:26:00.545049+00:002023-05-04T05:26:00.545049401Z 2023-05-04 05:26:00.545058+00:00--- google.com ping statistics --- 2023-05-04 05:26:00.545066+00:001 packets transmitted, 1 received, 0% packet loss, time 0ms 2023-05-04 05:26:00.545083+00:00rtt min/avg/max/mdev = 68.708/68.708/68.708/0.000 ms 2023-05-04 05:26:00.545094+00:002023-05-04T05:26:00.545094797Z 2023-05-04 05:26:00.545104+00:00No reboot necessary. 2023-05-04 05:28:00.536216+00:00Script configuration: 2023-05-04 05:28:00.536291+00:00Gateway model: NOK5G21 2023-05-04 05:28:00.536299+00:00Connectivity check: 2023-05-04 05:28:00.536314+00:00Mode: ping 2023-05-04 05:28:00.536319+00:00Http check: 2023-05-04 05:28:00.536331+00:00Target: https://google.com/generate_204 2023-05-04 05:28:00.536341+00:00Status Code: 204 2023-05-04 05:28:00.536354+00:00Ping configuration: 2023-05-04 05:28:00.536364+00:00Host: google.com 2023-05-04 05:28:00.536369+00:00Count: 3 2023-05-04 05:28:00.536373+00:00Interval: 1 2023-05-04 05:28:00.536378+00:00Protocol: IPv4 2023-05-04 05:28:00.536382+00:00Connection configuration: 2023-05-04 05:28:00.536387+00:00Primary band: ['B66'] 2023-05-04 05:28:00.536394+00:00Secondary band: ['n71'] 2023-05-04 05:28:00.536399+00:00Reboot settings: 2023-05-04 05:28:00.536404+00:00Reboot now: False 2023-05-04 05:28:00.536408+00:00Skip reboot: False 2023-05-04 05:28:00.536413+00:00Min uptime: 90 2023-05-04 05:28:00.536421+00:00Reboot on: ping 2023-05-04 05:28:00.536425+00:00General settings: 2023-05-04 05:28:00.536430+00:00Log file: 2023-05-04 05:28:00.536434+00:00Log all: False 2023-05-04 05:28:00.536439+00:00Log delta: False 2023-05-04 05:28:00.536443+00:00Log to syslog: False 2023-05-04 05:28:00.536450+00:002023-05-04T05:28:00.536450979Z 2023-05-04 05:28:00.536455+00:00PING google.com (142.250.217.238) 56(84) bytes of data. 2023-05-04 05:28:00.536460+00:0064 bytes from mia07s62-in-f14.1e100.net (142.250.217.238): icmp_seq=1 ttl=111 time=126 ms 2023-05-04 05:28:00.536464+00:002023-05-04T05:28:00.536464725Z 2023-05-04 05:28:00.536469+00:00--- google.com ping statistics --- 2023-05-04 05:28:00.536476+00:001 packets transmitted, 1 received, 0% packet loss, time 0ms 2023-05-04 05:28:00.536488+00:00rtt min/avg/max/mdev = 126.100/126.100/126.100/0.000 ms 2023-05-04 05:28:00.536494+00:002023-05-04T05:28:00.536494225Z 2023-05-04 05:28:00.536498+00:00No reboot necessary.