MythTV Backend Scheduler

Tell us your most wanted features from QNAP products.
Locked
torero22
New here
Posts: 5
Joined: Sun Aug 11, 2013 7:38 am

Re: MythTV Backend Scheduler

Post by torero22 » Thu Aug 15, 2013 3:41 pm

Well the Australian EPG service is working well, some how TVheadend is grabbing the EPG data from somewhere and is proving it to XBMC.

User avatar
bry
Know my way around
Posts: 195
Joined: Sun Jan 31, 2010 12:05 am

Re: MythTV Backend Scheduler

Post by bry » Mon Aug 19, 2013 10:21 pm

anybody successfully get this running on a 639 pro with a hd homerun prime?

vbier
Starting out
Posts: 30
Joined: Mon Jun 11, 2012 3:57 pm

Re: MythTV Backend Scheduler

Post by vbier » Tue Sep 24, 2013 8:27 pm

Just for info: I decided to install debian on my NAS some time ago and this was a good decision. I now have full control over the system and timely security updates.
You can even install mythtv from the deb-multimedia repos.

The only problem I have is that rsync hangs my NAS. But if you do not need that, I would try to install debian.

QMike
New here
Posts: 4
Joined: Sat Jun 22, 2013 2:21 am

Re: MythTV Backend Scheduler

Post by QMike » Mon Sep 30, 2013 9:27 am

Hi all

After few days of compilation, I am stuck on all side...hopefully someone can help on one of those 3 cases. I would like to go with option 3 but option 1 or 2 will be welcome as well.

My setup (This setup is currently working on my ubuntu workstation on 0.26 but would like to move to my Qnap NAS):
TS-219P running 4.0.2
HDHomeRun


1- Mythtv 0.24
Compile and configuration was ok
Access the backend from xbmc I get the following message in mythtv backend logs:

Code: Select all

MainServer::HandleVersion - Client speaks protocol version 8 but we speak 63

Access the backend from mythtv frontend 0.26 on ubuntu system:

Code: Select all

Database require update

I haven't been able to watch live tv from the hdhomerun due to those 2 issues and honoestly, I gave up quickly to use 0.24 because it wasn't the latest version and I told myself I should use the latest one anyway.



2- MythTv 0.26
Compile QT 4.7.4 OK
Applied the patches to Mythtv with manually patching mythcdrom-linux.cpp because patch wasn't design for 0.26 (from what I understood)
Configure Mythtv with following command:

Code: Select all

./configure --disable-frontend --prefix=/opt --qmake=/opt/Qt-4.7.3/bin/qmake

End up with the following warning:

Code: Select all

      DVB location needs to have linux/dvb/frontend.h [/usr/src/linux-2.6.33.2/include]
      WARNING: disabling Python bindings; missing MySQLdb
      WARNING: disabling Python bindings; missing lxml
      WARNING: disabling Python bindings; missing urlgrabber
      WARNING: disabling Perl bindings; missing DBD::mysql
      WARNING: disabling Perl bindings; missing HTTP::Request
      WARNING: disabling Perl bindings; missing LWP::UserAgent
      WARNING: disabling Perl bindings; missing Net::UPnP::QueryResponse
      WARNING: disabling Perl bindings; missing Net::UPnP::ControlPoint
      WARNING: disabling Perl bindings; missing IO::Socket::INET6

I tried the compilation (i was hoping it would pass even with all those warnings):
I got many lines like this:

Code: Select all

configure: creating ./config.status
              config.status: creating Makefile
         gawk: ./conf5jHmhj/subs.awk:2: S["/; s/!.*/"]=am__EXEEXT_FALSE!%!_!# ""
         gawk: ./conf5jHmhj/subs.awk:2:                                 ^ syntax error
         gawk: ./conf5jHmhj/subs.awk:3: S["/; s/!.*/"]=am__EXEEXT_FALSE!%!_!# ""
         gawk: ./conf5jHmhj/subs.awk:3:                                     ^ syntax error

which ends up with this error:

Code: Select all

config.status: error: could not create Makefile
         make[1]: *** [zeromq/Makefile] Error 1
         make[1]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/MythTv/mythtv-0.26.1/mythtv/external'
         make: *** [external] Error 2


At this point, why not trying the 0.27...

3- MythTv 0.27
After looking for a possible way to fix my 0.26, I saw that 0.27 was recently, why not :)
This version require QT 4.8 and up, Downloaded 4.8.5 and 5.1.1
Compile QT5.1.1:

Code: Select all

./configure --opensource -confirm-license -release -prefix /opt/Qt-4.8.5 -I /usr/local/mysql/include/mysql -L /usr/local/mysql/lib/mysql -sql-mysql-plugin

End up with this error:

Code: Select all

make[3]: *** [../../lib/libQt5Core.so.5.1.1] Error 1
      make[3]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/MythTv/qt-everywhere-opensource-src-5.1.1/qtbase/src/corelib'
      make[2]: *** [sub-corelib-make_first] Error 2
      make[2]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/MythTv/qt-everywhere-opensource-src-5.1.1/qtbase/src'
      make[1]: *** [sub-src-make_first] Error 2
      make[1]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/MythTv/qt-everywhere-opensource-src-5.1.1/qtbase'


Compile QT4.8.5:

Code: Select all

./configure --opensource -confirm-license -release -prefix /opt/Qt-4.8.5 -I /usr/local/mysql/include/mysql -L /usr/local/mysql/lib/mysql -sql-mysql-plugin

End up with this error:

Code: Select all

make[1]: *** [../../lib/libQtCore.so.4.8.5] Error 1
      make[1]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/MythTv/qt-everywhere-opensource-src-4.8.5/src/corelib'
      make: *** [sub-corelib-make_default-ordered] Error 2


Like I wrote at the beginning of my message, if someone can help to fix one of those 3 issues (I just want to have 1 working at this point lol).
Please note I am new at compiling...if I missed a basic point in compilation, let me know!

Thanks,

Mike

321liftoff
Know my way around
Posts: 214
Joined: Sat Oct 22, 2011 6:54 pm

Re: MythTV Backend Scheduler

Post by 321liftoff » Wed Nov 06, 2013 8:52 pm

Wow, Mike! You sure are trying a lot of options to get it to work. I used to use MythTV, but now use TVHeadend. I'm thinking of switching back to MythTV since it has commercial skipping features.

Regarding Option 1, I figured that I would give it a test for you. Fortunately, I still have my MythTV 0.24.3 installation on my QNAP TS-219P+. I started it up and was able to connect with XBMC 12.2 using the cmyth PVR plugin v1.6.10 (included with XBMC). I didn't see the error you were talking about.

I tried MythBox v1.1.0 for the first time and saw the errors you are talking about:

Code: Select all

2013-11-06 07:48:32.441 MainServer::HandleVersion - Client speaks protocol version 8 but we speak 63!


So I assume you are using MythBox?

321liftoff
Know my way around
Posts: 214
Joined: Sat Oct 22, 2011 6:54 pm

Re: MythTV Backend Scheduler

Post by 321liftoff » Wed Nov 06, 2013 9:00 pm

Also, I should mention that despite the errors, Mythbox was able to connect and see my recordings and EPG; I don't have any recordings to play yet. I saw this forum that mentions the difference between protocol versions, which may shed some light.

Liberty
Starting out
Posts: 23
Joined: Mon Jun 09, 2014 11:45 pm

Re: MythTV Backend Scheduler

Post by Liberty » Sun Jul 06, 2014 4:49 am

Firstlyt,thanks for posting the Wiki on getting Myth to run on the nas!

I have a diskless TS-469L V4.0.7 firmware loaded with 3 2T WD Reds in a raid 5 config (if memory serves). I have 1 of the 3T used for backups, pix, etc. I have nothing in the expansion RAM slot at the moment. I intend to expand to max soon but would like to move forward with my efforts to get mythtv operating in the meantime if possible. I know this thread seems to have died out and it would be great if it was because there now exists a simpler, better solution but I haven't found it! I am trying this with current versions in the hope and expectation that some issues will be simplified by doing so - a big assumption I know. My objective is to us the QNAP box (in part) as a backend and purchase a 2 or 3 channel homerun HD to replace the PCI based Happauge HD receiver card I have in my old server for OTA ATSC capture. MythWeb for config. Front ends - probably XBMC or mythtv for the most part and I don't expect to be doing any transcoding. I also want to avoid clutter on the Nas box so would like to avoid any unnecessary X stuff etc. if possible. I would also like to retain the simplicity of the UI present in the QNAP as it is (if possible) so am avoiding a full Debian, Webmin, Samba install on the box. To those ends I have followed the Wiki http://wiki.qnap.com/wiki/How_to_install_MythTV up to the point of
Using Kernel modules tuners
. No errors noted to this point. However...

Just prior to that I read
Note even if you are using a network tuner you will still need to download and untar the kernel source, it is required for dvb headers
and just after I read
NOTE: YOU DO NOT NEED THIS STEP IF YOU HAVE A HOMERUN HD DEVICE.
This is rather confusing! Which is it? Further, I find the first link broken so I did this

Code: Select all

 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.gz
instead. This results in:

Code: Select all

[/share/HDA_DATA/myth] # wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.gz --no-check-certificate
--2014-07-05 00:19:21--  http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.gz
Resolving www.kernel.org... 149.20.4.69, 198.145.20.140, 199.204.44.194
Connecting to www.kernel.org|149.20.4.69|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.gz [following]
--2014-07-05 00:19:21--  https://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.gz
Connecting to www.kernel.org|149.20.4.69|:443... connected.
WARNING: cannot verify www.kernel.org's certificate, issued by `/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 2 Primary Intermediate Server CA':
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 84544343 (81M) [application/x-gzip]
Saving to: `linux-2.6.33.2.tar.gz'
27% [=================================================>                                                                                                                                     ] 23,415,632   341K/s   in 71s
Cannot write to `linux-2.6.33.2.tar.gz' (No space left on device).
[/share/HDA_DATA/myth] #


And I am getting stuff ike this

Code: Select all

Number,Type,Date,Time,Users,Source IP,Computer name,Content
298,Information,7/5/2014,9:10:11,System,127.0.0.1,localhost,[HDD SMART] Host: Drive1 Rapid Test result: Completed without error.
297,Information,7/5/2014,9:10:11,System,127.0.0.1,localhost,[HDD SMART] Host: Drive3 Rapid Test result: Completed without error.
296,Information,7/5/2014,9:05:01,System,127.0.0.1,localhost,[HDD SMART] Host: Drive2 Rapid Test result: Completed without error.
295,Information,7/5/2014,9:03:01,System,127.0.0.1,localhost,[HDD SMART] Host: Drive1 Rapid Test started.
,,,,,,,
293,Information,7/5/2014,0:42:04,System,127.0.0.1,localhost,[Media Library] Media Library Server started.
292,Information,7/5/2014,0:41:14,System,127.0.0.1,localhost,System started.
291,Warning,7/5/2014,0:41:14,System,127.0.0.1,localhost,The system was not shut down properly last time.
290,Information,7/4/2014,19:40:39,System,127.0.0.1,localhost,[eSATADisk1]  Device detected. The file system is EXT4.
289,Error,7/5/2014,0:38:46,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/antivirus.global], section = [Antivirus], field = [AntivirusStatus], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
288,Error,7/5/2014,0:38:39,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/tmp/wireless_status], section = [], field = [status], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
287,Error,7/5/2014,0:38:39,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/wireless.conf], section = [], field = [status], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
286,Information,7/5/2014,0:38:35,System,127.0.0.1,localhost,System was shut down on Sat Jul  5 00:38:35 EDT 2014.
285,Error,7/5/2014,0:38:34,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [Misc], field = [System Started], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
284,Error,7/5/2014,0:38:31,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/tmp/wireless_status], section = [], field = [status], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
283,Error,7/5/2014,0:38:31,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/wireless.conf], section = [], field = [status], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
,,,,,,,
281,Error,7/5/2014,0:37:57,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [UPS], field = [Server Mode], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
280,Error,7/5/2014,0:37:56,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [UPS], field = [Server Mode], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
279,Error,7/5/2014,0:37:54,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [UPS], field = [Server Mode], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
278,Error,7/5/2014,0:37:53,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [UPS], field = [Server Mode], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
277,Error,7/5/2014,0:37:35,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/default_config/uLinux.conf], section = [QWEB], field = [PHP_ZEND_SUPPORT], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
276,Error,7/5/2014,0:37:23,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/var/.application.conf], section = [PhotoStation], field = [Enable], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
275,Error,7/5/2014,0:37:20,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/var/.application.conf], section = [MusicStation], field = [Enable], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
274,Error,7/5/2014,0:37:20,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/var/.application.conf], section = [MultimediaStation], field = [USBSound], value = [TRUE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
273,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Allowed mode], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
272,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Log Subfolder], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
271,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Log Folder], value = [Public]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
270,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Root Subfolder], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
269,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Root Folder], value = [Public]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
268,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [PORT], value = [69]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
267,Error,7/5/2014,0:37:08,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Enable], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
266,Information,7/5/2014,0:37:08,admin,192.168.1.214,---,[Power Management] System will be restart now.
,,,,,,,
,,,,,,,
263,Information,7/4/2014,23:22:17,System,127.0.0.1,localhost,[Media Library] Media Library Server started.
262,Information,7/4/2014,23:21:27,System,127.0.0.1,localhost,System started.
261,Information,7/4/2014,18:20:51,System,127.0.0.1,localhost,[eSATADisk1]  Device detected. The file system is EXT4.
260,Warning,7/4/2014,18:20:41,System,127.0.0.1,localhost,"[Volume DataVol1, Pool 1] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System""."""
259,Error,7/4/2014,23:18:49,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/tmp/wireless_status], section = [], field = [status], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
258,Error,7/4/2014,23:18:49,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/wireless.conf], section = [], field = [status], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
257,Information,7/4/2014,23:18:45,System,127.0.0.1,localhost,System was shut down on Fri Jul  4 23:18:45 EDT 2014.
256,Error,7/4/2014,23:18:42,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/tmp/wireless_status], section = [], field = [status], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
255,Error,7/4/2014,23:18:42,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/wireless.conf], section = [], field = [status], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
254,Error,7/4/2014,23:17:55,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/default_config/uLinux.conf], section = [QWEB], field = [PHP_ZEND_SUPPORT], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
253,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Allowed mode], value = [0]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
252,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Log Subfolder], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
251,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Log Folder], value = [Public]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
250,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Root Subfolder], value = []) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
249,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Root Folder], value = [Public]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
248,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [PORT], value = [69]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
247,Error,7/4/2014,23:17:29,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Enable], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
246,Error,7/4/2014,23:14:34,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/var/qnapddns.conf], section = [QNAP DDNS Service], field = [Wan IP], value = [108.8.102.236]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
245,Error,7/4/2014,23:05:47,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/.qos_config/users/admin/config], section = [common], field = [lastLoginVer], value = [4.0.7]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
244,Error,7/4/2014,23:05:47,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/.qos_config/users/admin/config], section = [common], field = [lastLogin], value = [1404529547]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
243,Error,7/4/2014,23:05:47,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/etc/config/.qos_config/users/admin/config], section = [datetime], field = [login], value = [1404529547]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
242,Error,7/4/2014,22:59:33,System,127.0.0.1,localhost,"The system is unable to save your settings (file = [/var/qnapddns.conf], section = [QNAP DDNS Service], field = [Wan IP], value = [108.8.102.236]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."
241,Information,7/4/2014,19:01:47,System,127.0.0.1,localhost,Optware 0.99.163 has been installed in /share/CACHEDEV1_DATA/.qpkg/Optware.

in my error logs. I understand that the NAS is not operating quite the same as a traditional server in terms of system memory, RAM, disk, etc. I am not at all certain that adding 2G of RAM will resolve this issue or if it does that it will not reappear later. If it does this would suggest there is an interim solution that would be beneficial in any case...

Is there a better way to get where I want to go from here?
Is it foolhardy to attempt to use current firmware?
Current version of Mythtv?
TS 469L
4 WD red WD20EFRX drives
Raid 5 config + spare
3Gig Ram (max)
Firmware 4.3.4.0569

FourG
New here
Posts: 7
Joined: Mon Jan 16, 2012 1:57 pm

Re: MythTV Backend Scheduler

Post by FourG » Sun Jul 06, 2014 6:14 am

I personally abandoned my attempts to build with native QNAP firmware in December 2013, and moved on to installing Ubuntu 64-bit LTS Server (12.04.4, at the moment) on my QNAP and then added the MythBuntu repository and set the QNAP up as a master backend (no frontend). So far recording from the HDHomeRun Prime with CableCard has been working well, though commercial flagging jobs do take a while to finish compared to my old non-Atom based server.

Installation
1. I started w/ QNAP Firmware 4.x
2. Download and install 64-bit Ubuntu 12.04.4 LTS (MythBuntu installation media doesn't support Software RAID, and they don't officially support any non-LTS )
a. Choose "Default" from first menu
b. DHCP on Eth1 (was Eth0 on the QNAP FW?). I may have ended up swapping the Ethernet cables for the LAN and the HDHomeRun around at this point. NOTE: If the port connected to the HDHomeRun is set to a 169.254.x.y/255.255.0.0 IP address, running a DHCP server is unnecessary for HDHomeRun to be discovered! :)
c. Hostname: mythbuntu
d. Had to Ctrl-C after the hostname step for some reason, and was returned to the hostname setup screen one more time. This time, downloads occurred after completing the step.
e. Set up new user
f. Accept time zone
g. HW detects the RAID controller
h. I selected 'Manual partitioning'. The original partitions were:
i. RAIDmd124, partition #1 - Your data. DON’T DELETE IF YOU DON'T HAVE A BACKUP.
ii. RAIDmd125 - /opt, probably for the qpkg addons
iii. RAIDmd126 - Swap
iv. RAIDmd127, partition #1 - qpkg updates, SQLite DB ds.db (DownloadStation?)
i. Since I had a backup, I ended up partitioning my disks as follows:
i. Made the 512MB USB FOB /dev/sda1 and mounted on /boot
ii. RAID disks are /dev/sd[c,d,e,f] and are part of a soft-RAID array
1) /dev/md0 is 100GB mounted on /
2) /dev/md2 is rest of disk mounted on /raid
3. After Ubuntu installation, follow the instructions at http://www.mythbuntu.org/existing-ubuntu to add Mythbuntu Control Center.
4. Launch MCC. I chose 0.27 under the Repositories section of Mythbuntu Control Center to support the Frontend builds for OS X Mavericks. Your mileage may vary.

The Front Panel LCD
1. The Front Panel LCD will stay illuminated with the startup message after you reboot. You can address this by following the instructions from viewtopic.php?t=19180#p244813
a. Set the baud rate to 1200:

Code: Select all

sudo stty -F /dev/ttyS1 1200

b. Tun on the backlight

Code: Select all

echo -e "M^\x1" > /dev/ttyS1

c. Set Line 1 text (string following "\x0 " must be exactly 16 characters)

Code: Select all

echo -e "M\f\x0 HELLO WORLD 1234" > /dev/ttyS1

d. Set Line 2 text (string following "\x1 " must be exactly 16 characters)

Code: Select all

echo -e "M\f\x1 HELLO WORLD 1234" > /dev/ttyS1

e. Turn off the backlight

Code: Select all

sudo echo -e "M^\x0" > /dev/ttyS1

2. A script to manage the LCD can also be found in the next reply to that thread (viewtopic.php?t=19180#p401624): Here is a script to set it. Save the content between the ===== lines in to a file set_qnap_lcd
Then make the file executable with chmod +x set_qnap_lcd
Then just do "set_qnap_lcd on" to turn it on and "set_qnap_lcd 2 Hello World" to set text of second line
====================================================================

Code: Select all

   #!/bin/bash
   
   TEXT="${@:2:$#}"
   
   function printUsage() {
   echo "Usage: $0 <off|on>"
   echo "Usage: $0 <1|2> Text Message"
   exit 0
   }
   
   function setDisplay() {
   if [ ${#2} -gt 15 ]; then
   echo "String to set can be max 16 characters!"
   exit 1
   fi
   
   printf "Setting line $1 on display to \"%s\"\n" "$2"
   # Text we print must be padded to exactly 16 characters to wipe old text
   printf "M\f\x`expr $1 - 1` %-16s" "$2" > /dev/ttyS1
   }
   
   if [ $# -eq 0 ]; then
   printUsage
   fi
   
   stty -F /dev/ttyS1 1200
   
   if [ $1 = "off" ]; then
   echo "Turning display off"
   echo -e "M^\x0" > /dev/ttyS1
   exit 0
   fi
   
   if [ $1 = "on" ]; then
   echo "Turning display on"
   echo -e "M^\x1" > /dev/ttyS1
   exit 0
   fi
   
   if [ $1 = "1" ] || [ $1 = "2" ]; then
   setDisplay $1 "$TEXT"
   exit 0
   fi
   
   printUsage

====================================================================

321liftoff
Know my way around
Posts: 214
Joined: Sat Oct 22, 2011 6:54 pm

Re: MythTV Backend Scheduler

Post by 321liftoff » Sun Jul 06, 2014 11:28 am

Liberty wrote:Firstlyt,thanks for posting the Wiki on getting Myth to run on the nas!


It's good to see someone else enthusiastic about the prospects of getting MythTV working on the QNAP NAS. I've always had the vision that a NAS would be the perfect DVR replacement. In fact, I've been using my QNAP TS-219P (ARM-based) as a DVR with mythtv and hdhomerun for 2 years now and have been very happy with it. I'm still using 0.24.3, and am considering upgrading to a newer version since all the mythtv android apps require atleast version 0.25 because of an API change. I'm still on the older kernel version, and I've heard that they have recently upgraded the linux kernel on the newer QNAP firmware releases. I use a Cubox-i running XBMC to access the ATSC files recorded by MythTV on my NAS. Also, I have a Windows 7 laptop that is running MythTV configured as a slave backend to do commercial detection at night for my recordings so the next day I can watch commercial free. If only XBMC would improve the GUI for PVR functions, it would be a complete replacement for Windows Media Center.

Regarding your issues, I think you downloaded the kernel source to a directory (HDA_DATA) that is located on your RAMDISK, not your hard disks. Because the RAMDISK is formed in ram, you filled it up and now other apps are complaining. If you delete that kernel source zip file from your RAMDISK and re-download to your hard-drives, that should clear the other problems you are having. If you are in fact using a RAID 5 configuration, then your HDD path should be /share/MD0_DATA/.

As I said, I'm using the hdhomerun devices and I don't think I downloaded the kernel sources. Compiling QT was a beast, and so was MythTV, but after it was done, and spending a couple of days configuring it, it is stable as a rock! I don't think there is a way around QT or X-windows when compiling MythTV since it is so integral to the code. Maybe in the newer versions of Myth, they separate the backend code to not require QT and the backend could be configured from a web interface instead of needing remote access to the x-server on the QNAP. If so, that would definitely save a lot of headache and would make it that much more accessible to low-power, headless systems like ours.

Good luck with your endeavors and let us know how it goes!

Liberty
Starting out
Posts: 23
Joined: Mon Jun 09, 2014 11:45 pm

Re: MythTV Backend Scheduler

Post by Liberty » Mon Jul 07, 2014 7:12 am

Thanks for the replies FourG and 321liftoff .

FourG

I am disappointed but not surprised to hear of your decision. I have been using Ubuntu 12.o4 LTS as my server os and Myth platform for some time. However, I never have been able to get Samba to work properly in terms of user access rights (my fault I know). I have the qnap box working as desired in that regard with little effort. I am no expert but have quite a bit of experience with the details of networking etc. and have used Ubuntu off and on since early in its development.

I had several reasons to get the Qnap really, power savings, capacity, raid, simplicity... So, now to decide. Do I set up another box to be the backend for Myth or try to get all the features I want running outside the confines of Qnap but using that hardware...

I really appreciate the time you took to run down the steps you took to get Ubuntu working for you. But there are a few questions I am left with about your process.
You attached a keyboard and monitor in order to complete the setup process correct?
Apparently you are running (loading) the your OS from a partition on the raid array correct?
I doubt my existing volume configuration will be handled properly by Ubuntu so I should plan on restoring from a backup. that raises backup compatibility concerns can you speak to this?
I assume bootable usb media are allowed on the QNAP boxes correct?

321liftoff,

Your usage model and complaints regarding XBMC are in line with mine.

I get this

Code: Select all

[//share/HDA_DATA] # uname -a
Linux Nas1 3.4.6 #1 SMP Thu Apr 10 05:20:37 CST 2014 x86_64 unknown

on my box which is running 4.0.7. Is this helpful at all in informing what version of Myth should be considered?

Thanks for your thoughts on my issues. When I

Code: Select all

[//share/HDA_DATA] # ls

as admin I get nothing. The unit has been re-started since the first error. If this location is on the ramdisk shouldn't anything I put there go away on reboot (I didn't power down)?
Shouldn't and the file(s) be visible there now if it needs to be deleted?
Also, following the directions at an earlier step I created a directory (I used /share/HDA_DATA/myth instead of /share/HDA_DATA/labratory ) which isn't visible. What happened with all of those earlier commands? Should I un-do them? My available ram has dropped by about 1/3.

I will probably not get back to this issue other than to do some research for 2 weeks so please bear this in mind if you reply.

Regards
TS 469L
4 WD red WD20EFRX drives
Raid 5 config + spare
3Gig Ram (max)
Firmware 4.3.4.0569

FourG
New here
Posts: 7
Joined: Mon Jan 16, 2012 1:57 pm

Re: MythTV Backend Scheduler

Post by FourG » Mon Jul 07, 2014 7:40 am

Yeah, the Ubuntu + MythTV decision was just to take advantage of the pre-built packages for x86_64 and regular security updates from upstream. Much more familiar to administer and closer to plug-and-play, which is what I personally prefer. If I could have successfully gotten QPKG to work for me, I might have stuck with QNAP FW.

Liberty wrote:You attached a keyboard and monitor in order to complete the setup process correct?

Correct, since my TS-459 ProII has a VGA port I hooked my monitor up to that and used a standard USB keyboard and mouse. AMI BIOS recognized everything, no problems there. The AMI BIOS allowed me to set the boot order so I could boot of the USB key with the installation media on it.

Liberty wrote:Apparently you are running (loading) the your OS from a partition on the raid array correct?

A portion of the OS, yes. The /boot partition that houses the GRUB bootloader, the kernel, and the initrd (initial Ramdisk) are all on the USB-based disk the QNAP software used to reside on. The root partition (/) is the 100GB partition I created on the RAID array.

Liberty wrote:I doubt my existing volume configuration will be handled properly by Ubuntu so I should plan on restoring from a backup. that raises backup compatibility concerns can you speak to this?

I was fortunate that my existing data all fit on the 1GB USB3 external drive, so that's what I did (backed up, completely wiped the on-board USB disk and the RAID array, installed, then restored the RAID data from the USB3 external drive). Total process took the better part of a day due to the relatively slow speed of the USB3 external disk.

Liberty wrote:I assume bootable usb media are allowed on the QNAP boxes correct?

Correct, navigate through the AMI BIOS screens to set the boot order if you have an Intel-based unit. I don't know what the ARM-based units support, though.

If you want to "preserve" the QNAP firmware, you might even want to consider using a separate USB thumb drive as your "/boot" partition. I used a 32GB SanDisk Cruzer Fit (CZ33) initially as my "/" as a proof-of-concept. It ran out of space quickly though as I added more packages, which is why I suggest using USB media as "/boot" and putting the "/" and swap partitions on the RAID array. Once I was confident I could boot off of the USB, I switched "/boot" to the built-in USB disk since 475MB was enough space for a few kernels and initrds. I did 3 partitions on the RAID array ("/", swap, and "/raiddata") so I could blow away the "/" partition with less chance of losing my data, should an OS re-install become required in the future. I do still back up critical directories in the RAID to offsite or USB3-based media as a precaution though.

321liftoff
Know my way around
Posts: 214
Joined: Sat Oct 22, 2011 6:54 pm

Re: MythTV Backend Scheduler

Post by 321liftoff » Mon Jul 07, 2014 9:32 am

Liberty wrote: 321liftoff,

Your usage model and complaints regarding XBMC are in line with mine.

I get this

Code: Select all

[//share/HDA_DATA] # uname -a
Linux Nas1 3.4.6 #1 SMP Thu Apr 10 05:20:37 CST 2014 x86_64 unknown

on my box which is running 4.0.7. Is this helpful at all in informing what version of Myth should be considered?


I get this and am running 4.0.1:

Code: Select all

[~] # uname -a
Linux NAS 2.6.33.2 #1 Tue Jun 4 05:23:55 CST 2013 armv5tel unknown

So I'm on an older version of the kernel. I think they have moved the ARM NAS's to 3.4.6 in firmware version 4.1, but I don't want to upgrade since everything is working well. As far as I know, MythTV doesn't rely on a specific kernel version to operate, so you should be okay to try versions of MythTV that are newer than 0.24.3, although I can't really help with those since I haven't tried them. And since you'll be using hdhomerun devices, you won't need to compile kernel-level drivers for tv tuners, so even more reason for you not to need to worry about the kernel version. What may constrict you is if there are "busybox" flavors of linux packages included with the QNAP firmware, which are usually stripped down versions from what ubuntu or debian uses. Sometimes, you have to install the standard versions through Optware IPKG to get things to work.

Liberty wrote:Thanks for your thoughts on my issues. When I

Code: Select all

[//share/HDA_DATA] # ls

as admin I get nothing. The unit has been re-started since the first error. If this location is on the ramdisk shouldn't anything I put there go away on reboot (I didn't power down)?
Shouldn't and the file(s) be visible there now if it needs to be deleted? Also, following the directions at an earlier step I created a directory (I used /share/HDA_DATA/myth instead of /share/HDA_DATA/labratory ) which isn't visible. What happened with all of those earlier commands? Should I un-do them? My available ram has dropped by about 1/3.

You may be right, that after a reboot the kernel source files and "mythtv" directory were discarded and a new RAMDISK was created. try running "ls /share/MD0_DATA/" and see what is listed. All your files should be stored in directories here if you are using a RAID setup, including all your files that you store on your NAS that you access through SAMBA. Take a minute and browse the directories of the NAS and get comfortable with it's structure. You'll be seeing a glimpse of the the "behind the scenes" of the QNAP GUI that you have been using.

Just to let you know, the wiki was written as a general guidance and assumes some amount of linux knowledge. Try your best to learn the "why" behind an instruction on the wiki to see if you need to modify it to meet your needs or specific configuration. For example, if you are using RAID, wherever you see "HDA_DATA" use MD0_DATA instead. If you find that the wiki is lacking in clarity, feel free to modify it to make it easier to follow. I did some re-writes on the wiki to help me. Glad to hear that you're giving it a go!

Liberty
Starting out
Posts: 23
Joined: Mon Jun 09, 2014 11:45 pm

Re: MythTV Backend Scheduler

Post by Liberty » Wed Jul 23, 2014 3:36 am

Thanks for the completeness of your replies.

321liftoff,

I guess there must be some notable diffs. between your version and mine. I get

Code: Select all

[//share] # ls -l
drwxrwxrwx   26 admin    administ      4096 Jul 22 11:11 CACHEDEV1_DATA/
drwxrwxrwx    4 admin    administ      4096 Jun 13 15:29 CE_CACHEDEV2_DATA/
lrwxrwxrwx    1 admin    administ        23 Jul 22 06:08 Download -> CACHEDEV1_DATA/Download/
drwxrwxrwx    2 admin    administ      1024 Sep 18  2005 HDA_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDB_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDC_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDD_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDE_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDF_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDG_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDH_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDI_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDJ_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDK_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDL_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDM_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDN_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDO_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDP_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDQ_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDR_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDS_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDT_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDU_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDV_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDW_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDX_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDY_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDZ_DATA/
lrwxrwxrwx    1 admin    administ        25 Jul 22 06:08 Multimedia -> CACHEDEV1_DATA/Multimedia/
lrwxrwxrwx    1 admin    administ        21 Jul 22 06:08 Public -> CACHEDEV1_DATA/Public/
drwxr-xr-x    2 admin    administ      1024 Jul 22 11:09 Qsync/
lrwxrwxrwx    1 admin    administ        25 Jul 22 06:08 Recordings -> CACHEDEV1_DATA/Recordings/
lrwxrwxrwx    1 admin    administ        18 Jul 22 06:08 Usb -> CACHEDEV1_DATA/Usb/
lrwxrwxrwx    1 admin    administ        18 Jul 22 06:08 Web -> CACHEDEV1_DATA/Web/
drwxrwxr-x   28 admin    administ      1024 Feb 28  2006 external/
lrwxrwxrwx    1 admin    administ         2 Jul 22 11:08 home -> %H@
lrwxrwxrwx    1 admin    administ        20 Jul 22 06:08 homes -> CACHEDEV1_DATA/homes/
drwxr-xr-x    2 admin    administ      1024 Jul 22 12:35 myth/
lrwxrwxrwx    1 admin    administ        38 Jul 22 11:11 twonkymedia -> /share/CACHEDEV1_DATA/.@twonkymedia.db/


No "MD0_DATA" so I assume I need to substitute "CACHEDEV1_DATA" instead. This seems to work. Am I correct?

I have created another issue. I decided to update firmware to 4.1.0. Still

Code: Select all

Linux Nas1 3.4.6 #1 SMP Thu Jun 12 17:15:43 CST 2014 x86_64 unknown
I hope this was a good idea. The improvements seemed worthwhile. Esp. related to the way media files get indexed. However, ipkg command line seems to be broken.

Code: Select all

[/share/CACHEDEV1_DATA/test] # ipkg install nano gcc make automake ncurses ncursesw wget ncurses-dev
-sh: ipkg: command not found

I didn't do anything special to get ipkg to work beyond installing Optware ipkg in 4.0.7. I re-started system just in case - no help. I can install single packages (ok by me) using web interface. It says

Code: Select all

Installing wget (1.12-2) to root...
Downloading http://ipkg.nslu2-linux.org/feeds/optware/ts509/cross/unstable/wget_1.12-2_i686.ipk
Configuring wget
Successfully terminated.

I hadn't noticed before if messages were coming up "installing to root" if this is proper, great! A more informed opinion would be appreciated. I have looked at the wiki for Optware \ ipkg but it seems dated (2012) and ipkg worked (seemed to) without me doing any of that. Since I did an update I am suspicious of the update. Should I forge ahead with the web based ipkg installer or not? The web installer does not give option to change where installed but the myth wiki puts making directory first and running ipkg while in that new dir after suggesting that this is necessary for the following (ipkg) steps.

Input appreciated.

Liberty
TS 469L
4 WD red WD20EFRX drives
Raid 5 config + spare
3Gig Ram (max)
Firmware 4.3.4.0569

321liftoff
Know my way around
Posts: 214
Joined: Sat Oct 22, 2011 6:54 pm

Re: MythTV Backend Scheduler

Post by 321liftoff » Thu Jul 24, 2014 5:26 pm

Yes, you are correct that CACHEDEV1_DATA is the directory you should be using. I've never seen that type of directory, but that's probably because I'm new to this as well.

You should be fine to install the packages by web interface, but it may be slower if you have to install one at a time. When you run ipkg from the command line, even it you are in a directory, the packages still get installed to their specific locations on the NAS, typically /opt. So don't worry about that part.

It sounds like your PATH variable got mucked up during the upgrade. You could try to uninstall the Optware package, and re-install it to see if the Optware directory is added back to the PATH variable, but this will require you to reinstall all your packages again. Instead, you could try searching your NAS for the location of ipkg and manually edit your PATH variable to include the directory that stores ipkg (typically /opt/bin/ipkg). When I do the following command, I get:

Code: Select all

# echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin/X11:/usr/local/sbin:/opt/bin:/opt/sbin

so you see that /opt/bin (where ipkg resides) is in my PATH variable so whenever I run ipkg from any directory it will find it. If you don't want to edit the PATH variable, you could simply try adding the directory in front of the command: "/opt/bin/ipkg install wget" (for example) and it should work that way too.

Liberty
Starting out
Posts: 23
Joined: Mon Jun 09, 2014 11:45 pm

Re: MythTV Backend Scheduler

Post by Liberty » Fri Jul 25, 2014 6:12 am

Thanks again 321liftoff,

You could try to uninstall the Optware package, and re-install it to see if the Optware directory is added back to the PATH variable, but this will require you to reinstall all your packages again.

I un-installed all packages installed by ipkg prior to any attempts to move forward. It was not (that is why I think it may be broken). Since I already removed them It really won't matter.

My path:

Code: Select all

[/] # echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin/X11:/usr/local/sbin:/usr/local/bin


So you are correct. I added to path by:

Code: Select all

 # PATH=/opt/bin:/opt/sbin:$PATH


It worked. Only have time to put back packages ATM but will try to steal more time before the week is over.

I hope all this back and forth will help and encourage others to try and make this work...

One more Question. Any reason I shouldn't use newest stable version of QT? Any cautions?

Regards,

Liberty
TS 469L
4 WD red WD20EFRX drives
Raid 5 config + spare
3Gig Ram (max)
Firmware 4.3.4.0569

Locked

Return to “Features Wanted”