TAILMON TAILMON v1.0.20 -Jul 27, 2024- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)

[jksmurf]

That is weird. Mine will actually stop and start the service when I encounter that error. Does that error message never resolve and just stays? Like you never see your device list?

Yup pretty much. Although when I exit then return it shows the device list just fine.

This is the Dev branch. I will get you back on the main

Thx

Check the Tailmon logs. I don't write anything to the syslogs. The messaging functionality does somewhat.

k.

 

[Viktor Jaep]

Yup pretty much. Although when I exit then return it shows the device list just fine.

Thanks for letting me know. I'll see if I can trap that bad behavior and force a service reset.

 

[jksmurf]

Thanks for letting me know. I'll see if I can trap that bad behavior and force a service reset.

Thanks Viktor . Let me know if there’s anything I can do or provide to reproduce it and help debug, if I can.

 

[Viktor Jaep]

Thanks Viktor . Let me know if there’s anything I can do or provide to reproduce it and help debug, if I can.

I've made some changes to catch that weird status error you've been seeing, @jksmurf ... please give this version a shot, and see if that helps resolve things? Now, when TAILMON determines that the status is giving an error, it will restart services. Let's see if it recovers after that?

Here's the updated script:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/develop/tailmon-1.1.0.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"

 

[jksmurf]

I've made some changes to catch that weird status error you've been seeing, @jksmurf ... please give this version a shot, and see if that helps resolve things? Now, when TAILMON determines that the status is giving an error, it will restart services. Let's see if it recovers after that?

Here's the updated script:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/develop/tailmon-1.1.0.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"

Hi Viktor! Thank you

OK so I followed your steps here again, for consistency.

• On step 3 after starting TM (before I get to the second SSH Window for the Update), I see two error messages (see picture 03a attached). The first 'failed to connect to local tailscaled' is the one I saw before; the second (error fetching current status:') I might not have noticed before. No idea about these, maybe a daemon startup timing mismatch or something?
• Also in step 3, AFTER it restarts TS (and says it sent a FAILURE email) it then shows (see 3b, v1.1.0) a running 'alive' TS service.
• After the second SSH window (step 4) is run, it correctly udpates TM v1.1.0 to v1.1.1, then correctly updates TS v1.82 to v1.84, but in the process, gives (the same) 'error fetching current status:' message shown in the scond part of 3a, then restarts TS, which seems to be OK, and says AU was completed successfully.

So again, it all seems to work OK, just gives those 3 errors (2 the same, at different stages of the update).

HTH

k.