QNAP QPKG for DVR Record Engine

[321liftoff]

Have a Qnap TS-219P+ (2-disk arm) and installed version 0.55a. It did not detect that I use MD0_DATA, so after installation, I had to manually change the record path to "/share/MD0_DATA/Recordings/HDHomeRunDVR". The discovered logfiles is blank.It has found my one tuner (HDTC-2US tuners 20150826 47 Channels)

I have this error at the top:
"Notice: Undefined index: TunerCount in /share/MD0_DATA/.qpkg/HDHomeRunDVR/ui/includes/dvrui_hdhrjson.php on line 43"

I have restarted the DVR record engine...first using the ./HDHomeRunDVR.sh stop command (because it complained about permissions), and now using the buttons.

The only thing in the config file is the following:
RecordPath=/share/MD0_DATA/Recordings/HDHomeRunDVR

should there be more?

[demonrik]

Have a Qnap TS-219P+ (2-disk arm) and installed version 0.55a. It did not detect that I use MD0_DATA, so after installation, I had to manually change the record path to "/share/MD0_DATA/Recordings/HDHomeRunDVR". The discovered logfiles is blank.It has found my one tuner (HDTC-2US tuners 20150826 47 Channels)

I have this error at the top:
"Notice: Undefined index: TunerCount in /share/MD0_DATA/.qpkg/HDHomeRunDVR/ui/includes/dvrui_hdhrjson.php on line 43"

I have restarted the DVR record engine...first using the ./HDHomeRunDVR.sh stop command (because it complained about permissions), and now using the buttons.

The only thing in the config file is the following:
RecordPath=/share/MD0_DATA/Recordings/HDHomeRunDVR

should there be more?

config file is good
does your QNAP not map /share/MD0_DATA/Recordings to just /share/Recordings?
discovered logfiles will be blank if they don't exist in that dir.. so if you change the conf file, you need to restart the record engine. Then it should start dumping logfiles there..

if it's not too much trouble can you provide the list of your /share directory, i.e.

Code: Select all

ls -l /share

using the stop command at ssh is only necessary if you want to control the record engine from the UI. I'm still trying to find a viable solution.. but am reaching my end I think
the problem is trying to find something that works from UI AND works from reboot. it seems we must choose one or other
Maybe I just need to make the choice available from the UI?!?!

[321liftoff]

Yes, recordings is linked to /share/MD0_DATA/Recordings. I manually entered the path "/share/MD0_DATA/Recordings/HDHomeRunDVR" as the recordings directory because it was set to CacheDEV1 originally which I don't have.

I don't have a subscription to HDHomeRun DVR yet, so maybe that is why log files are not being generated?

Any ideas what this error means at the top of the page?:
Notice: Undefined index: TunerCount in /share/MD0_DATA/.qpkg/HDHomeRunDVR/ui/includes/dvrui_hdhrjson.php on line 43

[demonrik]

Yes, recordings is linked to /share/MD0_DATA/Recordings. I manually entered the path "/share/MD0_DATA/Recordings/HDHomeRunDVR" as the recordings directory because it was set to CacheDEV1 originally which I don't have.

I don't have a subscription to HDHomeRun DVR yet, so maybe that is why log files are not being generated?

You should still get a logfile I would think.
Let's make sure we're running the engine right
ssh to the qnap
What do you get from

Code: Select all

ps -ef | grep hdhomerun

And let's check the config file

Code: Select all

cat /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf

Any ideas what this error means at the top of the page?:
Notice: Undefined index: TunerCount in /share/MD0_DATA/.qpkg/HDHomeRunDVR/ui/includes/dvrui_hdhrjson.php on line 43

Combination of a bug and your HDHR not using latest firmware. In recent firmware the tuner count is made available and I mistakenly assumed firmware would be updated. Will fix.

[321liftoff]

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # ps -ef | grep hdhomerun
 1736 admin       488 S   grep hdhomerun 
22464 httpdusr    348 S   /tmp/hdhomerun_record_arm start --conf /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf 

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # cat /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf
RecordPath=/share/Recordings/HDHomeRunDVR

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # ls /share/Recordings/HDHomeRunDVR
[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # 

[321liftoff]

Regarding firmware version, I appear to have the latest: 20150826, as listed on the Firmware changelog:

http://www.silicondust.com/support/down ... changelog/

Is there a newer version out? Where does this one reside?

[demonrik]

Regarding firmware version, I appear to have the latest: 20150826, as listed on the Firmware changelog:

http://www.silicondust.com/support/down ... changelog/

Is there a newer version out? Where does this one reside?

Latest for the Extend is 20160321atest1
You install with the windows installer http://download.silicondust.com/hdhomer ... atest1.exe

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # ps -ef | grep hdhomerun
 1736 admin       488 S   grep hdhomerun 
22464 httpdusr    348 S   /tmp/hdhomerun_record_arm start --conf /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf 

Cool.. Engine is running with the right config file

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # cat /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf
RecordPath=/share/Recordings/HDHomeRunDVR

And this looks right too.

Code: Select all

[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # ls /share/Recordings/HDHomeRunDVR
[/share/MD0_DATA/.qpkg/HDHomeRunDVR] # 

But no logfile..
Could be either permissions or as you said, not signed up.
Let's check a few things..
First check permissions

Code: Select all

ls -l /share/Recordings/

And also let's just start the record engine from command line and see if it reports anything strange
First stop the engine

Code: Select all

/share/MD0_DATA/.qpkg/HDHomeRunDVR/hdhomerun_record_linux stop

Then start it

Code: Select all

/share/MD0_DATA/.qpkg/HDHomeRunDVR/hdhomerun_record_linux start --conf /share/MD0_DATA/.qpkg/HDHomeRunDVR/HDHomeRunDVR.conf

What is the output?

Don't forget to rerun the stop command before starting up in UI again

[321liftoff]

It looks like it's a permissions issue:

Code: Select all

[~] # ls -l /share/Recordings/
drwxr-xr-x    2 admin    administ      4096 Apr 15 22:54 HDHomeRunDVR/
[/share/Recordings] # chmod 777 HDHomeRunDVR/
[/share/Recordings] # ls -l                  
drwxrwxrwx    2 admin    administ      4096 Apr 15 22:54 HDHomeRunDVR/

Restart the service...then:

Code: Select all

[/share/Recordings/HDHomeRunDVR] # ls
20160416.log
[/share/Recordings/HDHomeRunDVR] # cat 20160416.log 
HDHomeRun RECORD 20160406atest1 Linux
20160416-19:54:24 System: RecordPath: /share/Recordings/HDHomeRunDVR/
20160416-19:54:24 System: file limit = 4096
20160416-19:54:24 System: LocalIP: xxx.xxx.xxx.xxx 255.255.255.0
20160416-19:54:24 Recorded: directory /share/Recordings/HDHomeRunDVR/ with 0 subdirs and 0 recordings
20160416-19:54:24 Recording: discover on xxx.xxx.xxx.xxx
20160416-19:54:24 Status: Resource: dmk=10
20160416-19:54:24 Status: ticks = 11518139613
20160416-19:54:25 Recording: xxxxxx lineup request success (found 47 channels)
20160416-19:54:25 Recording: discover on xxx.xxx.xxx.xxx
20160416-19:54:25 Recording: discover response from xxxxxxx: lineup url = http://xxx.xxx.xxx.xxx:80/lineup.json
20160416-19:54:25 Recording: event download from my.hdhomerun.com
20160416-19:54:25 Recording: authorization error or not subscribed to dvr service
20160416-19:54:25 Recording: event download failed
20160416-19:54:25 Recording: disk space available = 879GB
20160416-19:54:25 Recording: current time = Sat Apr 16 19:54:25 2016 (correction of 0s)
20160416-19:54:25 Recording: no timer events planned
[/share/Recordings/HDHomeRunDVR] # 

Then I changed it back to 755, deleted the log file and started the service from the command line and saw a log file pop in there. So it appears that the start/stop commands from the webgui are running under user "httpdusr" and from the command line is "admin". I think you are already aware of this issue, though.

Still, don't know why the default recording path was CACHEDEV1_DATA. Maybe look into that, by using /share/Recordings/HDHomeRunDVR instead?

So it appears to be working as best as it can without me being a subscriber. Thanks for your help!

Do you know if having that latest firmware is required for DVR capability? It might be, since the tuner needs to know whether it's authorized for DVR capability, which is probably done through the windows loader application, and the current firmware probably doesn't even have this feature in it.

[demonrik]

It looks like it's a permissions issue:

Code: Select all

[~] # ls -l /share/Recordings/
drwxr-xr-x    2 admin    administ      4096 Apr 15 22:54 HDHomeRunDVR/
[/share/Recordings] # chmod 777 HDHomeRunDVR/
[/share/Recordings] # ls -l                  
drwxrwxrwx    2 admin    administ      4096 Apr 15 22:54 HDHomeRunDVR/

Restart the service...then:

Code: Select all

[/share/Recordings/HDHomeRunDVR] # ls
20160416.log
[/share/Recordings/HDHomeRunDVR] # cat 20160416.log 
HDHomeRun RECORD 20160406atest1 Linux
20160416-19:54:24 System: RecordPath: /share/Recordings/HDHomeRunDVR/
20160416-19:54:24 System: file limit = 4096
20160416-19:54:24 System: LocalIP: xxx.xxx.xxx.xxx 255.255.255.0
20160416-19:54:24 Recorded: directory /share/Recordings/HDHomeRunDVR/ with 0 subdirs and 0 recordings
20160416-19:54:24 Recording: discover on xxx.xxx.xxx.xxx
20160416-19:54:24 Status: Resource: dmk=10
20160416-19:54:24 Status: ticks = 11518139613
20160416-19:54:25 Recording: xxxxxx lineup request success (found 47 channels)
20160416-19:54:25 Recording: discover on xxx.xxx.xxx.xxx
20160416-19:54:25 Recording: discover response from xxxxxxx: lineup url = http://xxx.xxx.xxx.xxx:80/lineup.json
20160416-19:54:25 Recording: event download from my.hdhomerun.com
20160416-19:54:25 Recording: authorization error or not subscribed to dvr service
20160416-19:54:25 Recording: event download failed
20160416-19:54:25 Recording: disk space available = 879GB
20160416-19:54:25 Recording: current time = Sat Apr 16 19:54:25 2016 (correction of 0s)
20160416-19:54:25 Recording: no timer events planned
[/share/Recordings/HDHomeRunDVR] # 

Then I changed it back to 755, deleted the log file and started the service from the command line and saw a log file pop in there. So it appears that the start/stop commands from the webgui are running under user "httpdusr" and from the command line is "admin". I think you are already aware of this issue, though.

Yep - am aware of it.. and is proving to be a pain to fix..
But yay!! you are up and running

Still, don't know why the default recording path was CACHEDEV1_DATA. Maybe look into that, by using /share/Recordings/HDHomeRunDVR instead?

oversight on my part - new version pending which does exactly that and removes CACHEDEV1_DATA from the config file because it's not actually needed and also causing the problem you mention

So it appears to be working as best as it can without me being a subscriber. Thanks for your help!

Happy to

Do you know if having that latest firmware is required for DVR capability? It might be, since the tuner needs to know whether it's authorized for DVR capability, which is probably done through the windows loader application, and the current firmware probably doesn't even have this feature in it.

Yes - you will need to use the latest firmware for the DVR and new VIEW clients.

[demonrik]

New 0.5.6 uploaded which fixes the tuner count not present on old firmwares, and also fixes the issues in the default config file on dual/single bay NAS where there is no CACHEDEV1_DATA

https://drive.google.com/folderview?id= ... sp=sharing

Note: I'm going to be away at NAB Show in Vegas all week.. so won't be able to support from tomorrow April-17 until the following Sunday April-24. Will respond as quickly as I can once I return

[321liftoff]

Version 0.5.5a shows version 0.5.4 in the GUI and version 0.5.6 shows version 0.5.5. Also, version 0.5.6.qpkg doesn't fix the tuner count error. Maybe you are offset a version when you compiled the qpkgs?

[demonrik]

Version 0.5.5a shows version 0.5.4 in the GUI and version 0.5.6 shows version 0.5.5. Also, version 0.5.6.qpkg doesn't fix the tuner count error. Maybe you are offset a version when you compiled the qpkgs?

The versioning differences are deliberate.
The QPKG itself has a version to indicate the version of the routines/structure required to create the package.
The UI has a version
And of course the record engine has too..

It wasn't until 0.5.5 I modified the QPKG differently from the UI..
I need to come up with better convention thought to make it more apparent.
So for now.. I've done the following..
All UI versions will look like uX.Y.Z
All QPKG versions will take the form qX.Y.Z
where X will be significant releases (new big features), Y minor releases (minor tweaks/enhancements) and Z is bug fixes.

As for tuners.. aggh..
Problem is I don't have an old firmware device so can't test it.
I think I found it. Please let me know if it's not fixed in this new release.

So...
New package (following new scheme) q0.7.0 is now up on the google shared drive https://drive.google.com/folderview?id= ... sp=sharing

It includes the UI u0.6.0 (reset for this version) and record engine 20160419atest1
https://www.silicondust.com/forum/viewt ... 39#p209539

[321liftoff]

Thanks for the explaination. I tried the latest version and that seems to have fixed it. FYI,since you don't have a unit to test, on the right under detected tuners, it used to say:

Code: Select all

XXXXXXXXX
HDTC-2US 
tuners 
20150826 
47 Channels

and now it says:

Code: Select all

XXXXXXXXX 
HDTC-2US 
?? tuners 
20150826 
47 Channels

which seems like expected behavior.

[demonrik]

New package (following new scheme) q0.7.1 is now up on the google shared drive https://drive.google.com/folderview?id= ... sp=sharing

It includes the UI u0.6.0 and record engine 20160426atest1
https://www.silicondust.com/forum/viewt ... 13#p211213

[alphatech]

Rik, I wanted to thank you for following up with me in private about my post in regard of installing this QPKG. For some reason, I 'm unable to reply to your email so I will try to bother you with my issue about installing it on this post. I hope I will not annoying anyone here as well. First of all your dedication is admirable and you have lot of patience, that is appreciated. My current status at the moment, I was able to install the QPKG without issues, unfortunately maybe because I'm accessing it from the web portal I'm getting this error "The operation timed out." I will check it again when I get back home and report to you back. In the mean time, thanks again for reaching out to me.

P.S. Do you know why I can't reply to you via the private message system?