no tuner access

[crawfofd]

I am running unraid 6.3.4 and am trying to get sagetv docker to work. It loads great and I can connect with the placeshifter software. I can see all my hdhr's and can assign them to the epg with no problems. The only thing the is not working is accessing the tuners. I can see them but when I try to preview the channel it acts like it can not connect to the tuner. I also tried accessing through the guide and the same thing happens.
It looks like it would work great if I could get it to connect to the tuners.

I am using Hdhomeruns and they work fine in hdhomerun view.

PS any help would be greatly appreciated and thanks in advance.

UPDATE: Okay installed openDCT and tried to access tuners. I can now get tuner to play, but only for a few seconds.

[crawfofd]

Is there no one out there that can give me some direction.

I have made some progress,
I have openDCT docker up and running and finding my HDHRs.
I have sageTV docker up and running, finding my HDHRs and EPG is working.

The only problem I have now is when I select a channel to watch the video plays for about 1 second and then hangs.

Any help would be greatly appreciated.

Thanks,

[Fuzzy]

need logs to have any idea where to go next. opendct.log and sagetv_0.txt as a minimum. For simplicity, probably best to stop both dockers, start opendct, start sagetv, then try to watch something on your client, let it fail, then stop both and zip up and attach the logfiles. opendct.log will be in appdata/opendct/log/ and sagetv_0.txt will be in appdata/sagetv/server.

[crawfofd]

Fuzzy, Thanks for you reply and sorry for the delay.
Attached are the two log files.

I did some research with the little knowledge I have and I found an error in opedDCT that mentioned a format error, not sure what it means.

Anyway thanks for any assistance.

[Fuzzy]

What firmware do you have on the HDHR? Download the latest drivers and install them on your windows machine, and in it's setup, it should automatically update the HDHR to the newest firmware. It looks like it doesn't know how to respond to the requests openDCT is sending it.

[crawfofd]

I have the latest firmware on all my HDhomeruns.

Connect is Ver 201704beta1
Dual is Ver 2016117

I pretty much keep up with it.

[crawfofd]

okay just checked and there was another firmware upgrade. Ill install and try again. will let you know what happens

[crawfofd]

So that did not do anything.
Have updated firmware on hdhomeruns and I'm running the newest openDCT and SageTV dockers. Uninstalled and reinstalled numerous times.

It comes in great for 1 second. Could it be some kind of permissions problem?
When I installed the dockers I used the defaults

[EnterNoEscape]

Did you try tuning a channel in outside of the preview screen? Sometimes you can end up with different results. However I suspect the issue is the media server consumer. The brief playback you're describing could just be old data in the mpgbuf file. The one time there is an exception is when a channel number that could not possibly be ATSC is attempted to be tuned (2). I believe that's what Fuzzy was referring to and I would expect the HDHomeRun to be confused about that request.

I can't really use the SageTV log because it looks like it was restarted right after this testing. The times all of the tuning was happening in OpenDCT pre-dates the earliest time in the SageTV log. sage_1.txt might have was we are looking for.

[alfi33]

You don't need openDTC for the HDHR Dual, do you?

I'm not an openDTC user so I may not know what I'm talking about...but if you take openDTC out of the equation and you're having the issue with the Dual, I'd guess that the problem has something to do with the recording directory itself (no space, permissions, etc).

[MacDaddy]

While there is native support for the HDHRs, to take advantage of pooling you would need OpenDCT. For the Prime then OpenDCT is the only game in town.

I got bit a couple of times when I had Sage started before OpenDCT. You might want to try stopping both dockers. Deliberately start OpenDCT first before starting Sage.

[crawfofd]

Thanks everyone for the feedback.
I have tried selecting different channels, tried rebooting the hdhomeruns, tried launching from the epg and from the channel lineup, all fail. I have uninstalled in reinstalled both openDCT and sagetv.
I tried just using the hdhomerun without openDCT but it will not even bring up a channel. I can watch saved video no problem
Will it help if I try sending another set of logs??

[EnterNoEscape]

If it's the media server consumer at fault, this suggestion should work a lot better:

1. Stop the OpenDCT docker.

2. Edit opendct.properties and make the following changes:
consumer.ffmpeg.upload_id_enabled=true
consumer.raw.upload_id_enabled=true

Do this for all of the capture devices:
sagetv.device.<unique_id>.consumer=opendct.consumer.FFmpegTransSageTVConsumerImpl

3. Start the OpenDCT docker.

[crawfofd]

EnterNoEscape, Thanks for your reply. I have not tried your solution yet, but will this morning. I am curious if you know the answer to this.
When I look at the sagetv log I see a lot of chown from root:root to sagetv:sagetv but I do not have a user sagetv, could this be the problem?
Also when I look at the permissions to my sagetv server directory all ownership is nobody:users with 755 access.

I was thinking that the openDCT is the problem, but I should be able to set up my hdhomeruns without it and I can not do that. If I set up a sagetv server on another pc (not raid) I can get it setup and it works.

[EnterNoEscape]

Originally Posted by crawfofd

EnterNoEscape, Thanks for your reply. I have not tried your solution yet, but will this morning. I am curious if you know the answer to this.
When I look at the sagetv log I see a lot of chown from root:root to sagetv:sagetv but I do not have a user sagetv, could this be the problem?
Also when I look at the permissions to my sagetv server directory all ownership is nobody:users with 755 access.

I was thinking that the openDCT is the problem, but I should be able to set up my hdhomeruns without it and I can not do that. If I set up a sagetv server on another pc (not raid) I can get it setup and it works.

sagetv is a valid user account and group within the Docker container. It was created for you within the Docker container. sagetv correlated with the same uid as the nobody account on the unRAID side of things which is what you are seeing. There is more detail as to why of this, but the easy answer is that this is the safest way to set it up.

One reason you wouldn't be able to use the tuners "natively" or through OpenDCT has a common thread. They both are configured by default to use the SageTV remuxer. If the remuxer can't figure out what's going on with the stream, you'll get no output in either situation. My suggestion would have you using FFmpeg instead.

There is one more possibility, but probably unlikely that somehow the directory is using to record into isn't accessible.

[crawfofd]

EnterNoEscape, I have made the changes that you requested but did not change anything.

I am going to have to put this off till later tonight.

Thanks again for all the help. For now I have a standalone sagetv working on a non raid system. I will get back to the unraid tonight.

[crawfofd]

Okay worked on this for quite awhile last night and here is what I came up with.

I've been trying to install the latest version to my unraid pc (sagetv 9.1.1.651) which would only show 1 second of video. So I went to a open pc and tried to install the same version on that pc (non unraid). It installed fine, but when I tried to access a live channel it would crash. I knew I had sagetv v 9.0.14.568 working on that same pc so I reloaded that one. It worked fine. Light bulb!
I loaded sagetv v9.0.14.568 on my unraid pc and now it works perfectly.
So something in the latest version (with my setup) will not run properly.

Don't know what has changed but that was definately my problem...
Unless there is any reason to change I will stay with the version that works.
If anyone wants me to help troubleshoot why its not working on the newest version, I will gladly help.

Sagetv has been the only system that I can say meets most of my requirements as a dvr and it is the most wife friendly.

I want to thank all the original developers and the new ones for all the hard work for a great product

Thanks.

[EnterNoEscape]

If you post a SageTV log file when the issue happens, that should help greatly isolate what the problem is. The last log had no tuning information in it.

Edit: Your observation is especially interesting because I don't recall anything significant happening involving capture devices. An interface was shimmed into many classes around there, but the actual underlying classes did not change at all. I feel like a lot more people would be observing a similar issue if there was a serious break, but maybe something more subtle is happening. Are you running Java 8? I know we made a few garbage collection changes if you're running Java 8.

[stuckless]

I would post the sagetv_0.txt log files after a crash. That might help narrow down where this is happening.

[crawfofd]

okay, I will reload the failing version and capture both logs and post them.

Also I am using java 8