Unofficial HDHomeRun DVR repository for DEB based systems

Downloads & Instructions
gtb
Expert
Posts: 3316
Joined: Thu Oct 06, 2011 1:00 pm
Location: Sunnyvale, CA USA

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby gtb » Sat Mar 10, 2018 7:05 pm

Any ideas?
Check the DVR engine logs (same folder as the specified location for recording). They may tell you something (if there are no logs a common issue is the permission of the folder you set for recording does not actually allow writing by the engine, which typically will be set to run as user hdhomerun). Also check the journald logs (or wherever your logs are stored in your system type) for any other interesting entries [remember that viewing full logs may require running with elevated privs].
Last edited by gtb on Sun Mar 11, 2018 7:53 am, edited 2 times in total.

Dsab
Posts: 6
Joined: Thu Feb 01, 2018 10:50 am

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby Dsab » Sun Mar 11, 2018 6:36 am

Any ideas?
Check the DVR engine logs (same folder as the specified location for recording). They may tell you something (if there are no logs a common issue is the permission of the folder you set for recording does not actually allow writing by the engine, which typically will be set to run as user hdhomerun). Also check the journald logs (or wherever your logs are stored in your system type) for any other interesting entries [remember that full logs may require running with elevated privs].
[/quote]

Folder permission was the problem. Thanks for the help.

gtb
Expert
Posts: 3316
Joined: Thu Oct 06, 2011 1:00 pm
Location: Sunnyvale, CA USA

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby gtb » Tue Mar 13, 2018 10:25 am

Folder permission was the problem. Thanks for the help.
I have updated the directions (first post) to add in an item about permissions. Perhaps that will help the next person. Thanks.

ttc
Posts: 2
Joined: Mon Apr 02, 2018 5:43 pm

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby ttc » Mon Apr 02, 2018 6:13 pm

I just wanted to say thank you. I used this to get a Raspberry pi 3 working as the record engine. All is well and it handles it much better than I thought. 3 concurrent streams and the CPU usage hovers around 20%.
I have a similar setup running RPi3. I have an older NAS that doesn't support SSH, so I did "mount -t cifs -o username=<username of NAS>,password=<password of NAS>,rw '\\<IP of NAS>\HDHomeRun' /srv/HDHomeRun" to redirect the /srv/HDHomeRun folder of the RPi3 to my NAS with what think are the correct permissions. The record engine shows up on My HDHomeRun.com and shows the correct available recording space with NAS attached, basically re-directing the RPI3 record folder to a NAS record folder. Everything appears good. However, I don't get a log file when the record engine starts and the HDHomeRun app reports "No DVR Configured". HDHomeRun Version is 20180327 on both DVR and HDHomeRun CONNECT. Can you elaborate on your setup?

gtb
Expert
Posts: 3316
Joined: Thu Oct 06, 2011 1:00 pm
Location: Sunnyvale, CA USA

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby gtb » Mon Apr 02, 2018 6:32 pm

I have a similar setup running RPi3. I have an older NAS that doesn't support SSH, so I did "mount -t cifs -o username=<username of NAS>,password=<password of NAS>,rw '\\<IP of NAS>\HDHomeRun' /srv/HDHomeRun" to redirect the /srv/HDHomeRun folder of the RPi3 to my NAS with what think are the correct permissions.
I'll note that while some people have managed to get remote storage working at some level, SD has been pretty clear it is not generally a supported configuration as it typically will not work properly due to limitations in the remote storage protocols [it might appear to work at first, and then will fail later]. My guess would be that a block level remote storage solution using something like iSCSI probably would work, but that is not quite the same. You are typically expected to run the record engine on the device with the local disk.

ttc
Posts: 2
Joined: Mon Apr 02, 2018 5:43 pm

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby ttc » Thu Apr 05, 2018 5:37 pm

I have a similar setup running RPi3. I have an older NAS that doesn't support SSH, so I did "mount -t cifs -o username=<username of NAS>,password=<password of NAS>,rw '\\<IP of NAS>\HDHomeRun' /srv/HDHomeRun" to redirect the /srv/HDHomeRun folder of the RPi3 to my NAS with what think are the correct permissions.
I'll note that while some people have managed to get remote storage working at some level, SD has been pretty clear it is not generally a supported configuration as it typically will not work properly due to limitations in the remote storage protocols [it might appear to work at first, and then will fail later]. My guess would be that a block level remote storage solution using something like iSCSI probably would work, but that is not quite the same. You are typically expected to run the record engine on the device with the local disk.
I thought it would be at least worth a try. Even without the redirect statement (recording directly to the local drive) I have the same result. The recording engine appears to be running normal, but could indeed be a permissions issue to the record path. What syntax would allow write permission to the record path from hdhomerun userid? I thought system service users inherited root privileges?

gtb
Expert
Posts: 3316
Joined: Thu Oct 06, 2011 1:00 pm
Location: Sunnyvale, CA USA

Re: Unofficial HDHomeRun DVR repository for DEB based systems

Postby gtb » Tue Apr 10, 2018 1:02 pm

I thought it would be at least worth a try. Even without the redirect statement (recording directly to the local drive) I have the same result. The recording engine appears to be running normal, but could indeed be a permissions issue to the record path. What syntax would allow write permission to the record path from hdhomerun userid?
Generally something like:
chown hdhomerun <path>
chmod 0700 <path>
does what you want (gives ownership to the user, and insures only that user can access the directory)
I thought system service users inherited root privileges?
No (and it would be a terrible idea of they did). The service *can* be set to run as any user (including root), but a dedicated (for the app) non-privileged user is generally best for all services (so an issue with that service does not impact or expose anything from other services).


Return to “Downloads & Instructions”

Who is online

Users browsing this forum: No registered users and 2 guests