Websockets sending bad (corrupt?) data

Sorry, to be more explicit—the Console app inside web uses web sockets:

Ah, okay. I don’t see any wonky data there. The only thing I would consider odd would be this occasional type of message:

Statistics: (kfbe7u3funw2uqnn932z56j3) Reporting active playback in state 0 of type 4 (scrobble: 0) for account 1

But I’m guess the text string inside the brackets is just a particular username scrambled up (?).

Try viewing the websocket messages using this website.

http://www.websocket.org/echo.html

The location would be

ws://127.0.0.1:32400/:/websockets/notifications?X-Plex-Token=XXXXXXXXXX

Obviously fill in XXXXXXXXXX with your token.

You don’t have to send anything in that website. The messages should just start showing up in the logs.

Successfully tested this method; I let it run for about ten minutes, and saw no missing or garbage characters in the resulting log.

But did you see garbage in Tautulli’s Plex websocket logs? It’s only a useful test if you find a difference between the two logging methods. If both don’t show garbage, then there isn’t any data to be gained.

In other words, if both show garbage, then the issue is with Plex. If only Tautulli shows garbage, then the issue is with Tautulli. If neither show garbage, then there is no issue.

Also, every message should match up in both logs. Garbage may show up in Tautulli, but the message may be completely missing from that website depending on how they handle bad messages.

I’ve only ever noticed garbage data in the Tautulli logs; I’ll take some time today after lunch to do some testing and get 1:1 log comparisons. I’ll post back later today.

So here’s what I did:

  • I quit Tautulli.
  • Started Tautulli again and “connected” on the websocket testing website.
  • Started watching a show on my remote computer; one other user was already watching a show.
  • Let it run for 10 minutes, then downloaded the logs.

Comparing the two logs is difficult, as what I get from the website contains no timestamps. That being said, I knew exactly what time I re-started Tautulli, so that wasn’t a big deal.

What I found was that after I restarted Tautulli, the ten minutes’ worth of logs were clean: no garbage characters or data. But if I looked at earlier timestamps, I found those non-standard characters in the log. I don’t know if restarting is the solution, because I’ve restarted Tautulli many times during my testing, and the garbage data always shows up again at some point. The logs from the website were also clean.

The big limitation in collecting logs from that website is that it just dumps it to a text field on the page; copying from that field only yields partial log information (about 45 lines, versus 671 generated by Tautulli). Upon further use, later Tautulli logs show more errors.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.