Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76221 - [tailscale] 1.32.0-1 crashes as soon as the machine is authorized

Attached to Project: Community Packages
Opened by Stefan Zwanenburg (psYchotic) - Sunday, 16 October 2022, 19:13 GMT
Last edited by Morten Linderud (Foxboron) - Thursday, 11 May 2023, 21:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Morten Linderud (Foxboron)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: As soon as the private key is authorized with Headscale (I haven't tried reproducing with Tailscale's backend itself), tailscaled crashes with the following backtrace:

RAW-STDERR: ***
RAW-STDERR: *** Lines prefixed with RAW-STDERR below bypassed logtail and probably come from a previous run of the program
RAW-STDERR: ***
RAW-STDERR:
RAW-STDERR: panic: invalid argument to Intn
RAW-STDERR:
RAW-STDERR: goroutine 167 [running]:
RAW-STDERR: math/rand.(*Rand).Intn(0xc000079ef4?, 0xc00063c1a0?)
RAW-STDERR: math/rand/rand.go:168 +0x65
RAW-STDERR: math/rand.Intn(...)
RAW-STDERR: math/rand/rand.go:337
RAW-STDERR: tailscale.com/net/netcheck.(*Client).checkCaptivePortal(0x100000100000001?, {0x55bb28167cf8, 0xc00078d180}, 0xc000179a10, 0x0)
RAW-STDERR: tailscale.com/net/netcheck/netcheck.go:1108 +0x51f
RAW-STDERR: tailscale.com/net/netcheck.(*Client).GetReport.func4()
RAW-STDERR: tailscale.com/net/netcheck/netcheck.go:934 +0x7a
RAW-STDERR: created by time.goFunc
RAW-STDERR: time/sleep.go:176 +0x32


Steps to reproduce:

1. Start tailscaled
2. If you hadn't done this yet, run tailscale up, and authorize your machine's key. As soon as you do, you should see the above crash.


The tailscale maintainers are aware of the crash, and apparently, a version 1.32.1 is incoming.
This task depends upon

Closed by  Morten Linderud (Foxboron)
Thursday, 11 May 2023, 21:00 GMT
Reason for closing:  Fixed
Comment by Stefan Zwanenburg (psYchotic) - Sunday, 16 October 2022, 19:26 GMT
I just tried reproducing with Tailscale's own backend, and AFAICT, the bug doesn't occur with it.
Comment by Toolybird (Toolybird) - Sunday, 16 October 2022, 19:31 GMT
> The tailscale maintainers are aware of the crash

Link?
Comment by Stefan Zwanenburg (psYchotic) - Sunday, 16 October 2022, 19:34 GMT
> > The tailscale maintainers are aware of the crash
>
> Link?

Sorry, no link, reporting and acknowledgment happened over IRC, and I can't find an archive of the channel (#tailscale on Libera.Chat).

Here's a transcript:

2022-10-13 21:08+02:00 <psYchotic> tailscaled (as installed from a bunch of repositories, Ubuntu, Debian, Fedora) keeps crashing on me :(
2022-10-13 21:29+02:00 <+Xe> psYchotic: what is your docker run command and the error you get?
2022-10-13 21:31+02:00 <psYchotic> I can't reproduce the error in a container. This only seems to happen when running directly
2022-10-13 21:31+02:00 <+Xe> running it via systemd?
2022-10-13 21:32+02:00 <psYchotic> Yes. Give me a second to re-reproduce it :)
2022-10-13 21:37+02:00 <psYchotic> https://0bin.net/paste/IGwyLYYx#i-qWHj7tE4JgtTC1oDwaYMBCBsDu1RQA6LWuw5JHeeM
2022-10-13 21:40+02:00 <psYchotic> tailscaled's version: 1.32.0; tailscale commit: c729f53f8786675f8b32cc1026b990dafed6bb24; other commit: 2240b50035b36798992a70441b3d1ab3c5b8c7f2; go version: go1.19.2-ts3fd24dee31
2022-10-13 21:44+02:00 <psYchotic> That looks like it's a bit newer than whatever's in the official docker images.
2022-10-13 21:48+02:00 <+Xe> psYchotic: what distro are you running this on?
2022-10-13 21:49+02:00 <psYchotic> I tested on Ubuntu 22.04, 20.04, Debian 11 and Fedora 36
2022-10-13 21:49+02:00 <psYchotic> All with tailscale's own repos
2022-10-13 21:50+02:00 <psYchotic> I found out 1.30.2 is available in the Ubuntu repo, so when I install that, everything seems to work fine.
2022-10-13 21:50+02:00 <+Xe> psYchotic: I am escalating that
2022-10-13 21:51+02:00 <psYchotic> Please do. I couldn't find an issue on Github, and considered creating one, but didn't know if it maybe had something to do with me using headscale
2022-10-13 21:52+02:00 <+Xe> psYchotic: does that happen after you connect to headscale or instantly when systemd starts tailscaled?
2022-10-13 21:54+02:00 <psYchotic> Only after authorizing the key in headscale.
2022-10-13 21:54+02:00 <psYchotic> I could provide a reproducer in the form of a docker-compose.yaml?
2022-10-13 21:59+02:00 <+Xe> psYchotic: we found a probable cause, use the old version for now until we can release 1.32.1 next week

Loading...