[Bug]: Stream not showing up in Tracearr

[alexandzors]

Tracearr Version

1.4.18-beta.2

Deployment Method

Docker - Standard (separate containers)

Host System

Unraid 7.2.3

Connected Media Servers

• Plex
• Jellyfin
• Emby
• None configured yet

Media Server Version(s)

Plex 1.43.0.10467

Affected Area

Web Dashboard

Bug Description

I have a user's stream that does not appear on the Tracearr dashboard. Shows up in other apps and the built in Plex dash. This is the second time I noticed it and figured it was actually a bug. In the screenshot below the Seal Team episode is not showing up in Tracearr.

Steps to Reproduce

Not entirely sure how to reproduce this one.

Docker Compose / Run Command

#...
  tracearr:
    image: ghcr.io/connorgallopo/tracearr:next
    container_name: media_tracearr
    shm_size: 4gb
    environment:
      - NODE_ENV=production
      - PORT=3000
      - HOST=0.0.0.0
      - TZ=America/New_York
      - DATABASE_URL=postgres://tracearr:<redacted>@postgres:5432/tracearr
      - REDIS_URL=redis://valkey:6379
      - JWT_SECRET=<redacted>
      - COOKIE_SECRET=<redacted>
      - CORS_ORIGIN=*
      - LOG_LEVEL=Info
    depends_on:
      - postgres
      - valkey
    volumes:
      - /mnt/user/appdata/media/tracearr:/data/tracearr
    restart: unless-stopped
    networks:
      - media-db
      - media-intra
      - caddy

  valkey:
    image: valkey/valkey:8-alpine
    container_name: media_valkey
    shm_size: 4gb
    command: valkey-server --appendonly yes
    volumes:
      - /mnt/user/appdata/media/valkey:/data
    healthcheck:
      test: ["CMD", "valkey-server", "ping"]
      interval: 10s
      timeout: 5s
      retries: 5
    restart: unless-stopped
    networks:
      - media-db

  postgres:
    container_name: media_postgres
    shm_size: 2gb
    command: postgres -c timescaledb.max_tuples_decompressed_per_dml_transaction=0 -c max_locks_per_transaction=4096
    networks:
      - media-db
    image: timescale/timescaledb-ha:pg17
    environment:
      - POSTGRES_PASSWORD=<redacted>
    ports:
      - 4000:5432
    volumes:
      - /mnt/user/appdata/media/postgres:/home/postgres/pgdata/data

Relevant Logs

https://gist.github.com/alexandzors/e621da21b296c51a1feac64a4f21d916

Was this working before?

Yes, it stopped working without any changes

Additional Context

As far as I can tell this started happening recently.

Checklist

• This isn't a duplicate of an existing issue
• Version number filled in above
• Docker compose/run command included (if applicable)

[lcasale]

I just upgraded to 1.4.18 from 1.4.12 and Tracearr is showing zero streams while Plex and Tautulli are showing 4. I thought maybe Tracearr is watching for when a stream starts if they're in progress while Tracearr starts they get ignored?

[alexandzors]

I just upgraded to 1.4.18 from 1.4.12 and Tracearr is showing zero streams while Plex and Tautulli are showing 4. I thought maybe Tracearr is watching for when a stream starts if they're in progress while Tracearr starts they get ignored?

That is a possibility. However, my instance was already running when it occurred.

[connorgallopo]

@alexandzors I made some tweaks in latest beta around sse. lmk if you see an improvement

[alexandzors]

@alexandzors I made some tweaks in latest beta around sse. lmk if you see an improvement

Will do. I also have Debug logging enabled and I've been trying to replicate it after talking with Durzo this morning.

[connorgallopo]

Debug logging is just gonna be noise - Most things of value related to this issue will show up in standard logging

[pblue3]

I've observed something similar when multiple streams are launched from the same browser (different tabs, same user). Only one stream appears instead of all of them.

[connorgallopo]

@pblue3 I would expect this behavior in this case. They are keyed for uniqueness by content, device, and user.

I see no reason one user would be watching many things on the same device at the same time. So unless it's a legitimate use case, support for that does not need to exist.

[pblue3]

Yes, that makes sense.
I had opened several tabs to test the rules, but it's true that this isn't an expected use case in real-world scenarios.

[connorgallopo]

@alexandzors Im going to close this as im gonna bank on "no news is good news" lol.

But i have notifications on so if you message here I will see it!