Yellow Triangle on recording - No conflicts, no indication of the issue

I see the randomly: A yellow triangle with an ! on it present on a recording. No information anywhere about what that means and to date, the recording does not happen. So, where do I find out the issue, and fix it?

Search the Plex Media Server log file.

Johnm - this is the same problem that I was having, that w your help I temporarily solved by going back to version 1.6.1…

It doesn’t say anything if you click on the triangle?

I’ve certainly had the triangles in the past where you can’t click on them to get any more info

The Plex Media Server log should give some explanation of what happened to the recording.

I am experiencing the same issue as the creator of this post. I have noticed that only 1 channel will record. All others will produce the yellow triangle and not record the show. When I hover over the yellow triangle it says “There was a transcoder error”. What should I look for in the Plex Media Server log to try to figure out what is going on?

Look for anything dealing with the show.

I tried to get the system to record an Episode of Doctor Phil as a test. It is at the end of the file I have attached. I see it generating errors, but can’t determine the issue.

You having any network issues?

Jul 18, 2017 17:21:18.151 [0x7f6a287ff700] ERROR - Error parsing allowedNetworks ‘192.168.1.x’: Invalid argument
Jul 18, 2017 17:21:18.607 [0x7f6a27ffe700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.

Brian - What version of Plex are you using? Is it later than 1.6.1…?

Not that I am aware of. When things were working my HDHomeruns gave me access to 7 channels. Now I can record 1 specific channel reliably. The other 6 channels give me the same transcoder error. For that reason it seems funny that this may be caused by a network error.

@1dermutt This line is repeated all throughout your logs:
ERROR - Error parsing allowedNetworks ‘192.168.1.x’: Invalid argument

According to Notepad++ when I search for 192.168.1.x in the log you submitted it is found 3,614 times.

You have something not setup correctly in your Plex Server settings would be my guess. Did you add 192.168.1.x somewhere in the settings, perhaps under the Network settings? Might not be related to your recording issue but you should not be seeing that many errors in the log file.

I found what was causing the error you found, but after correcting the issue you found and retesting, I still have the original transcoder issue.

I did try to record another program and found this in the log file:

ERROR - [Transcoder] [mpeg2video @ 0x23dd1c0] Invalid frame dimensions 0x0.

Any thoughts on what might be causing this?

That’s not unusual to see as recordings tune in and start. If there’s a transcoder error, which you reproduce, the best thing to do is provide a raw sample from the HDHR, along with logs from when you attempted the recording.

Getting samples for DVR issues

 Steps:

1. Restart your server, and allow the EPG to load (if it's been ~18 hours since a server restart)

2. If you had the EPG reload, then restart your server again (this keeps the logs clean, as there won't be the EPG refresh this time) - otherwise you can skip this step

3. Start a direct .ts sample from the tuner. You can do this by using a command such as:
 curl http://tunerip:port/auto/channel > /users/outputpath/plexSamples/samplefile.ts
        (You can copy the tuner URL bit from your logs, if it helps)
 
4. Start a recording in PMS of a problematic channel

5. Cancel the recording after a minute or so

6. Stop the direct capture from the tuner

7. Download the complete logs from the server

8. Zip up the logs, the direct sample from the tuner, and the recording from PMS, and post them here

I can’t include a PMS recording due to it failing, but I did make a direct .ts sample and I grabbed the Plex Media Server log file and attached them here.

They’re general steps, but as long as everything is done in that order (mainly starting the raw capture first from the affected channel, then replicating the issue in PMS) then it should be okay. I’ll have a little bit of a look at it later, and pass it on :smile:

@1dermutt Can you recreate that issue, except when there is nothing else going on on the server? I’m seeing things in Now Playing, and the EPG refreshing going on at the same time, which makes the logs rather hard to follow.

@DaveBinM I made another sample. There should have been nothing else going on with the PMS when I made the sample file.

@1dermutt Thanks, I’ll take a look at it soon :smile: