Tinode Immediately Crashes on New Message

[Colin Masters]

Hey everyone, this is a really weird issue we're facing trying to run the latest tinode:postgres container.

I am using Tinode + Coturn in a standard docker setup, everything starts correctly and I access the web interface and am able to create two accounts, upload profile pic etc. The moment I hit the new message button, the  tinode container crashes instantly, no logging whatsoever;

1d69ab47e22e:/opt/tinode# tail -f /var/log/tinode.log
I2025/06/30 18:20:19 ws: session started V6VmwAZni8w 172.18.0.1:62072 3
I2025/06/30 18:20:19 in: '{"login":{"id":"74184","scheme":"token","secret":"WjikUyoStX4ySnVoFAABAAEAc3e7E+rjFncF685wMr/6VQZoerYnV75eu4r9yngWEXE="}}' sid='KEHqtTM7I_E' uid=''
I2025/06/30 18:20:19 in: '{"login":{"id":"78554","scheme":"token","secret":"2MwQtHEL4eXKSXVoFAABAAEALjRhwOeZFGY76dL4qayh4oNi2h4BaYdDEAqg5imgBUg="}}' sid='LobtWZKRWYg' uid=''
I2025/06/30 18:20:19 in: '{"hi":{"id":"68434","ver":"0.24.0","ua":"TinodeWeb/0.24.0 (Firefox/140.0; MacIntel); tinodejs/0.24.0","lang":"en-CA","platf":"web"}}' sid='V6VmwAZni8w' uid=''
I2025/06/30 18:20:19 in: '{"login":{"id":"68435","scheme":"token","secret":"2MwQtHEL4eVzSXVoFAABAAEAzLOgYIS3biF7puLk7ZSfxEK9hNd9dccZTHIVtasFKfU="}}' sid='V6VmwAZni8w' uid=''
I2025/06/30 18:20:19 in: '{"sub":{"id":"74185","topic":"me","get":{"what":"sub desc tags cred"}}}' sid='KEHqtTM7I_E' uid='WjikUyoStX4'
I2025/06/30 18:20:19 in: '{"sub":{"id":"68436","topic":"me","get":{"what":"sub desc tags cred"}}}' sid='V6VmwAZni8w' uid='2MwQtHEL4eU'
I2025/06/30 18:20:19 in: '{"sub":{"id":"78555","topic":"me","get":{"what":"sub desc tags cred"}}}' sid='LobtWZKRWYg' uid='2MwQtHEL4eU'
I2025/06/30 18:20:19 media serve: OK, uid= 2MwQtHEL4eU
I2025/06/30 18:20:19 media serve: OK, uid= 2MwQtHEL4eU

Anyone ever seen anything like this? Is there a way to get access to the stack trace or something? More logging?

Thanks in advance
Colin

[Gene]

Take a look at the docker logs

https://docs.docker.com/reference/cli/docker/container/logs/

[Colin Masters]

There’s no logs in docker, no logs in Tinode when I jump into the container.

I’m in the middle of writing a script to try and catch stderr/out - it’s so strange!

Kicker; it’s working on our cloud side but not locally 😝

--
You received this message because you are subscribed to the Google Groups "Tinode General" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tinode+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tinode/b5f6b6a0-ad24-4505-ba19-9f871ba2de69n%40googlegroups.com.