Can't access web interface when using new version(s)
Added by Richard Mace over 10 years ago
I have been running a dpkg installed version of tvheadend (RaspI) very successfully for over a year.
I have compiled both 3.4.7 and 3.6 and replaced the old version with the new in /usr/bin/.
However, when I restart the service I cannot access the web interface. I am obviously doing something fundamentally
wrong here!
The browser 'title' "General - TvHeadend - Chromium' comes up, but nothing else.
Incidentally, the sizes b/w the modules are vastly different:-
-rwxr-xr-x 1 root root 521368 Apr 22 2013 tvheadend
-rwxr-xr-x 1 root root 2308984 May 25 14:04 tvheadend_3.6
When I put the 'old' version back, all works fine.
Hoping someone can sort this out...
The reason I want to compile my own version, is that I am now running an Odroid U3, no 'packaged' version exists for this...
Replies (5)
RE: Can't access web interface when using new version(s) - Added by Prof Yaffle over 10 years ago
If your system supports dpkg, you should use the included build script to create a .deb, and then install that. Simply over-writing the binary (especially if you're moving from 3.4 to anything after the dvb rewrite) is a recipe for disaster... you need to either trash or migrate your config as things changed significantly. The only hesitation I have is whether the migration is automated now or not - I may have imagined that it is, in which case you need to use the migration script.
RE: Can't access web interface when using new version(s) - Added by Richard Mace over 10 years ago
Thanks for that, both systems support dpkg, My ODROID is a fresh install, my Pi is migrate.
Where are these scripts in the "tvheadend-release" folder?
Thanks very much...
I have looked in the Autobuild folder:-
-rwxr-xr-x 1 richard richard 1304 Dec 17 13:11 debian.sh*
-rw-rw-r-- 1 richard richard 114 Dec 17 13:11 lucid-amd64.sh
-rw-rw-r-- 1 richard richard 112 Dec 17 13:11 lucid-i386.sh
-rw-rw-r-- 1 richard richard 116 Dec 17 13:11 precise-amd64.sh
-rw-rw-r-- 1 richard richard 114 Dec 17 13:11 precise-i386.sh
This is my 'new install'system:-Linux my-machine 3.8.13.16 #1 SMP PREEMPT Tue Feb 11 10:47:21 BRST 2014 armv7l armv7l armv7l GNU/Linux
Is there a suitable script?
Additionally, I have looked @ the migration script, it says "migration from 3 to 4" I am only going from 3.4. to 3.6. Will this script cater?
edit: I have used the debian option, has built 'something', not sure if appropriate for my system though...? Forgive me but is this architecture related? I am arm7l... I
RE: Can't access web interface when using new version(s) - Added by Prof Yaffle over 10 years ago
You can download the migration script directly from the link in that post if you need it. That said (and 3.6 bypassed me), from the commits it appears that the new dvb code went into master/3.9 and not 3.6, so I'm maybe sending you the wrong way on that.
Regarding building a deb for the Odroid... way out of my league, I'm afraid. I'd guess at the Debian script, albeit potentially with some hacking around if your target is ARM and not x86. The only posts I can find are about building for Android. Perhaps it's worth looking in the repos (and elsewhere) for a Debian ARM build.
RE: Can't access web interface when using new version(s) - Added by Richard Mace over 10 years ago
Ok, thanks for that.
On my 'new' (ARM) odroid machine, do I really need to build a dpkg package? It seems to have compiled successfully, it is running..
If I start it with -C or --noacl (as per the faq's, should I be able to get into the web interface & configure?
(can't actually try it myself at the moment....)
RE: Can't access web interface when using new version(s) - Added by Prof Yaffle over 10 years ago
No, I don't suppose you have to... it's good practice, and it ensures that everything ends up in the right place when you install, startup rules are created, that sort of thing - but it's not essential. Indeed, you don't have to even install the binary - you could run it in a terminal, or write your own init script, and so on. If you do run it as a regular user like this, make sure you have access to the adapters via the video group or similar.