TAILMON TAILMON v1.1.0 -Jul 12, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Now available in AMTM!)

[Viktor Jaep]

Looks like for whatever reason, the newly added Tailscale status check does not like you. Might need to back that out.

 

[frazor77]

Rolled back using :

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

Then did a reboot. Will monitor.

 

[frazor77]

OK, that didn't work. It stopped emailing me failures every 5 seconds.... but still showed the memory error... So took off and nuked the whole site from orbit, only way to be sure.

After a full uninstall and reinstall of Tailmon+Tailscale all seems OK.

 

[Viktor Jaep]

OK, that didn't work. It stopped emailing me failures every 5 seconds.... but still showed the memory error... So took off and nuked the whole site from orbit, only way to be sure.

After a full uninstall and reinstall of Tailmon+Tailscale all seems OK.

So are you running the latest version again without issues now? Nice job nuking the site from orbit. Always takes care of all the vermin.

 

[frazor77]

Latest version (Tailmon 1.1.0 w/ Tailscale 1.84.0) = Yes

Without issues now = No

Its no longer in a restart loop, but its still erroring, possibly triggered by me logging in to AMTM/Tailmon:

fatal error: runtime: out of memory

runtime stack:
runtime.throw({0x77bbb8?, 0x28298?})
runtime/panic.go:1101 +0x38 fp=0x7ffc1c8610 sp=0x7ffc1c85e0 pc=0x84808
runtime.sysMapOS(0x4000000000, 0x400000)
runtime/mem_linux.go:168 +0x104 fp=0x7ffc1c8650 sp=0x7ffc1c8610 pc=0x28854
runtime.sysMap(0x4000000000, 0x400000, 0xd5af28?)
runtime/mem.go:155 +0x34 fp=0x7ffc1c8670 sp=0x7ffc1c8650 pc=0x282a4
runtime.(*mheap).grow(0xd4ace0, 0x3b038?)
runtime/mheap.go:1547 +0x274 fp=0x7ffc1c86f0 sp=0x7ffc1c8670 pc=0x3c034
runtime.(*mheap).allocSpan(0xd4ace0, 0x1, 0x0, 0x26)
runtime/mheap.go:1252 +0x164 fp=0x7ffc1c8790 sp=0x7ffc1c86f0 pc=0x3b544
runtime.(*mheap).alloc.func1()
runtime/mheap.go:970 +0x6c fp=0x7ffc1c87e0 sp=0x7ffc1c8790 pc=0x3b04c
runtime.(*mheap).alloc(0x7ffc1c8868?, 0x27a40?, 0x0?)
runtime/mheap.go:964 +0x54 fp=0x7ffc1c8830 sp=0x7ffc1c87e0 pc=0x3afb4
runtime.(*mcentral).grow(0x7ffc1c88b8?)
runtime/mcentral.go:254 +0x5c fp=0x7ffc1c8870 sp=0x7ffc1c8830 pc=0x27d1c
runtime.(*mcentral).cacheSpan(0xd5d5a8)
runtime/mcentral.go:170 +0x4ec fp=0x7ffc1c88f0 sp=0x7ffc1c8870 pc=0x27b8c
runtime.(*mcache).refill(0x7fa8954108, 0x20?)
runtime/mcache.go:183 +0x1ac fp=0x7ffc1c8940 sp=0x7ffc1c88f0 pc=0x2704c
runtime.(*mcache).nextFree(0x7fa8954108, 0x26)
runtime/malloc.go:964 +0x84 fp=0x7ffc1c8990 sp=0x7ffc1c8940 pc=0x23554
runtime.mallocgcSmallScanNoHeader(0x120, 0x660500, 0x1)
runtime/malloc.go:1366 +0x144 fp=0x7ffc1c89f0 sp=0x7ffc1c8990 pc=0x23e24
runtime.mallocgc(0x120, 0x660500, 0x1)
runtime/malloc.go:1058 +0x88 fp=0x7ffc1c8a20 sp=0x7ffc1c89f0 pc=0x82138
runtime.newobject(0x7ffc1c8fda?)
runtime/malloc.go:1714 +0x2c fp=0x7ffc1c8a50 sp=0x7ffc1c8a20 pc=0x2499c
internal/cpu.doinit()
internal/cpu/cpu_arm64.go:22 +0x24 fp=0x7ffc1c8a80 sp=0x7ffc1c8a50 pc=0x121a4
internal/cpu.Initialize({0x0, 0x0})
internal/cpu/cpu.go:153 +0x24 fp=0x7ffc1c8aa0 sp=0x7ffc1c8a80 pc=0x11c74
runtime.cpuinit(...)
runtime/proc.go:738
runtime.schedinit()
runtime/proc.go:838 +0x100 fp=0x7ffc1c8b30 sp=0x7ffc1c8aa0 pc=0x500a0
runtime.rt0_go()
runtime/asm_arm64.s:86 +0xa4 fp=0x7ffc1c8b60 sp=0x7ffc1c8b30 pc=0x8a3a4

2 Jul 14 2025 20:51:02 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Entware package installed.
3 Jul 14 2025 20:51:43 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Connection stopped.
4 Jul 14 2025 20:51:44 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Service stopped.
5 Jul 14 2025 20:51:44 RT-AX88U-5B60 TAILMON[160156] - INFO: Userspace Mode settings have been applied.
6 Jul 14 2025 20:51:45 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Service started.
7 Jul 14 2025 20:54:30 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Connection started.
8 Jul 14 2025 20:54:30 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale binary updated to latest available version.
9 Jul 14 2025 20:56:08 RT-AX88U-5B60 TAILMON[160156] - INFO: Device has been configured as Exit Node.
10 Jul 14 2025 20:56:08 RT-AX88U-5B60 TAILMON[160156] - INFO: TAILMON config has been updated.
11 Jul 14 2025 20:56:13 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Connection stopped.
12 Jul 14 2025 20:56:16 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Service stopped.
13 Jul 14 2025 20:56:17 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Service started.
14 Jul 14 2025 20:56:18 RT-AX88U-5B60 TAILMON[160156] - INFO: Tailscale Connection started.
15 Jul 14 2025 20:57:42 RT-AX88U-5B60 TAILMON[163916] - INFO: TAILMON keepalive enabled.
16 Jul 14 2025 20:57:42 RT-AX88U-5B60 TAILMON[163916] - INFO: TAILMON config has been updated.
17 Jul 14 2025 20:57:56 RT-AX88U-5B60 TAILMON[163916] - INFO: TAILMON config has been updated.
18 Jul 14 2025 20:57:56 RT-AX88U-5B60 TAILMON[163916] - INFO: AMTM Email notification configuration saved
19 Jul 14 2025 20:58:04 RT-AX88U-5B60 TAILMON[163916] - INFO: Reboot Protection Enabled
20 Jul 14 2025 20:58:04 RT-AX88U-5B60 TAILMON[163916] - INFO: TAILMON config has been updated.
21 Jul 15 2025 08:36:58 RT-AX88U-5B60 TAILMON[429749] - ERROR: Tailscale Status producing errors. Restarting services.
22 Jul 15 2025 08:37:00 RT-AX88U-5B60 TAILMON[429749] - INFO: Tailscale Connection stopped.
23 Jul 15 2025 08:37:02 RT-AX88U-5B60 TAILMON[429749] - INFO: Tailscale Service stopped.
24 Jul 15 2025 08:37:04 RT-AX88U-5B60 TAILMON[429749] - INFO: Tailscale Service started.
25 Jul 15 2025 08:37:05 RT-AX88U-5B60 TAILMON[429749] - INFO: Tailscale Connection started.
26 Jul 15 2025 08:37:08 RT-AX88U-5B60 TAILMON[429749] - INFO: Email notification was sent successfully [FAILURE: Tailscale Service Restarted]

EDIT: The above showed when I finished reinstalling at 2058 last night then logged in to check at 0837 this morning. I should add that despite this error it all seems to be working OK for the most part.

 

[Viktor Jaep]

Latest version (Tailmon 1.1.0 w/ Tailscale 1.84.0) = Yes

Without issues now = No

Its no longer in a restart loop, but its still erroring, possibly triggered by me logging in to AMTM/Tailmon:

EDIT: The above showed when I finished reinstalling at 2058 last night then logged in to check at 0837 this morning. I should add that despite this error it all seems to be working OK for the most part.

That is so strange. I can't duplicate this. I've tried launching from amtm, standalone, through screen, back & forth. I can't get any errors.

On my setup, I have it run at startup through screen... then, I will check on it every so often by using the command "tailmon -screen". I don't use amtm to run it. I just drop right to an SSH command.

What produces that runtime error you posted? How did you get that? Doesn't seem to be from the syslog?

 

[frazor77]

I'm going in via amtm, then it appears on the main tailmon screen, just not straight away (after ~20m or so)

 

[Viktor Jaep]

I'm going in via amtm, then it appears on the main tailmon screen, just not straight away (after ~20m or so)

Incredibly strange. I have TAILMON running 24x7 in a screen window, and I have yet to hit that error.

I know @jksmurf was getting it after updating the script/tailscale, and having it relaunch while coming from AMTM. But that this fix seemed to have resolved that. His previous fix was just exiting the script, and going back into it.

If it's continuing to cause issues on your end, I might just have to back it out.

 

[jksmurf]

If it's continuing to cause issues on your end, I might just have to back it out.

If there’s a beta test version still available prior to the fix you did for my errors, maybe @frazor77 could try that to test?

 

[Viktor Jaep]

I'm going in via amtm, then it appears on the main tailmon screen, just not straight away (after ~20m or so)

Can you send a screenshot of what you see? Feel free to redact anything you need... but would love to see the error and where it shows up.

 

[Viktor Jaep]

If there’s a beta test version still available prior to the fix you did for my errors, maybe @frazor77 could try that to test?

Sadly, the beta is basically v1.1.0 at this point.

 

[Dr.Rom]

I did not read all the posts in this thread but just wanted to mention this issue which is an update to an old post with my problem of not being able to update tailmon through the update option.

You can read my post (between post #415 until #431) from

TAILMON - TAILMON v1.0.20 -July 27, 2024- WireGuard-based Tailscale Installer, Configurator and Monitor (THREAD #1 CLOSED)

@Viktor Jaep is the man :cool: ! And there is no “may” as far as I’m concerned, getting past CGNAT by configuring Tailscale with a subnet router got me access to my remote device. Love it! Have to do some reading but currently running on phone and router says connected to tailnet, but stops...

www.snbforums.com

The last recommendation was to do a complete router reset and reconfiguration.

Here are what I noticed/some background:

- the router is managed remotely. No issue with local router.
- in between I had the chance to gain access to the router and did a physical reset and reconfigure. I changed the external usb device from a usb stick to a usb nvme desk.
- I kept regularly updating amtm and tailmon since then until 1.0.20.

Yesterday I tried to do an update to 1.1.0. tailmon detected the presence of an update. Downloaded and installed the update but whenever you lunch tailmon again it would still report that it is on 1.0.20. Rerunning the update will complete again but nothing would happen.

I managed then to do the following (3 things) to resolve this issue but I’m not sure which part was the main cause:

First I made sure no ”screen” was still running. I did screen -r and it connected to a screen which was on tailmon monitor screen running in the background and I exited from it. I ran screen -r again and it said that there is no more screen running.

I then went to option 7 “Custom configuration options for TAILMON”. There I had two options which I had previously set to yes and changed them to “NO”: “Keep Tailscale Service Alive” and “Keep settings on Tailscale Entware updates”

After changing those settings I was able to update to 1.1.0

I don’t know what was the change from 1.0.20 to 1.1.0 that was preventing update when those two setting were switched to yes. All other versions before 1.0.20 were updating normally except from the version I had issues before in the old post.

I just wanted to share with you my experience. Maybe it would help someone else.

 

[jksmurf]

I did screen -r and it connected to a screen which was on tailmon monitor screen running in the background and I exited from it. I ran screen -r again and it said that there is no more screen running.

I then went to option 7 “Custom configuration options for TAILMON”. There I had two options which I had previously set to yes and changed them to “NO”: “Keep Tailscale Service Alive” and “Keep settings on Tailscale Entware updates”

@Viktor Jaep just for data points I don’t normally use screen but did use it when following the instructions for beta 1.1.0 as per our discussion above.

I have “Keep Tailscale Service Alive” and “Keep settings on Tailscale Entware updates” both set to yes.

 

[Viktor Jaep]

First I made sure no ”screen” was still running. I did screen -r and it connected to a screen which was on tailmon monitor screen running in the background and I exited from it. I ran screen -r again and it said that there is no more screen running.

I then went to option 7 “Custom configuration options for TAILMON”. There I had two options which I had previously set to yes and changed them to “NO”: “Keep Tailscale Service Alive” and “Keep settings on Tailscale Entware updates”

After changing those settings I was able to update to 1.1.0

I don’t know what was the change from 1.0.20 to 1.1.0 that was preventing update when those two setting were switched to yes. All other versions before 1.0.20 were updating normally except from the version I had issues before in the old post.

I just wanted to share with you my experience. Maybe it would help someone else.

Even if you still had the script running under screen, you could still update the script to the latest version, and that latest version would be written to your /jffs/scripts folder. The TAILMON script running on the screen would still be running the old version as it's running in memory. But as soon as you kill that, and start it back up, it would be running the new version that it just read from /jffs/scripts.

Could it be that you were running the update separately, but continuing to look at the screen instance and not restarting that instance?

 

[Dr.Rom]

Even if you still had the script running under screen, you could still update the script to the latest version, and that latest version would be written to your /jffs/scripts folder. The TAILMON script running on the screen would still be running the old version as it's running in memory. But as soon as you kill that, and start it back up, it would be running the new version that it just read from /jffs/scripts.

Could it be that you were running the update separately, but continuing to look at the screen instance and not restarting that instance?

I do my remote update on my phone using Termius app and I always try to end the connection with e and exit to exit the terminal. Only when I get distracted away from the app and it disconnect that I might have left a screen running. My point is that with the app I only open one window/connection at a time.

Regarding your first part of your reply. I did try to reboot once to see if I could resolve the issue and it didn’t so I left it like that for few hours. I would assume that doing a reboot would kill any script/screen and start up fresh. Maybe after that while trying again with no luck I had this screen session not terminated properly before I later came with the idea to look into options 7.