Tvheadend

Martin Walter Walter

The log that shows Tvheadend crashing was uploaded in my previous post. Other than that I don't see additional log entries. Uploading again just in case.

@ Chad d

Please look in the webif of tvheadend if it is realy not running. In my case it was but the center called it wasn't.

If you have video station installed and running, please give it a try and stop video station.
This helps in my case.
otherwise try login via ssh
sudo /var/packages/tvheadend/scripts/start-stop-status stop
Then try to start with packet centre

P L wrote:

Martin Walter Walter

It is stable as long as I don’t stop the package. If I do, I cannot start it again. Only thing that enables me to start it again is if I reboot DSM and try starting the package repeatedly.

nemal nemal L:
I was referring to your statement above, i.e. the fact that the package does not start again after you have stopped it. Can you provide a different log-file containing that behavior or are you telling me that you can reproduce crashes that way like in the log-file you have shared?

Russel Crowe wrote:

@ Chad d

Please look in the webif of tvheadend if it is realy not running. In my case it was but the center called it wasn't.

If you have video station installed and running, please give it a try and stop video station.
This helps in my case.
otherwise try login via ssh
sudo /var/packages/tvheadend/scripts/start-stop-status stop
Then try to start with packet centre

wow, thank you. I looked at webif and it was running just as you suspected. Weird. I'm not running Video Station, is it possible a different package could be causing the conflict? Running channel scan now. After I back up and running I will log in and do a status stop and see if that allows package center to start run.

After running through wizard, scanning channels and finishing configuration, then going back to webif, in package center, selecting run for TVheadend package starts up normal. Thank you again.

Martin Walter wrote:

nemal nemal L:
I was referring to your statement above, i.e. the fact that the package does not start again after you have stopped it. Can you provide a different log-file containing that behavior or are you telling me that you can reproduce crashes that way like in the log-file you have shared?

Martin Walter Walter
Yes I can reproduce the crash. Here goes the logs:
1 - Tvheadend running and then stopped (tvheadend_1.log)
2 - I tried starting Tvheadend one time (tvheadend_2.log) but package remained in a stopped state. Strangely the log shows no signed of Tvheadend being stopped, on the contrary.
3 - I tried starting Tvheadend again but no crash was seen in the logs again. So I tried starting Tvheadend again (tvheadend_3.log). That's when I could see the crash in the logs.

I am able to reproduce the crash but not consistently. It doesn't happen each time I start Tvheanded. Perhaps every 2 to 3 attempts sometimes every 4 or 5 attempts. No matter whether Tvheadend is crashed or not Tvheadend will be in a stopped state until I reboot and I try starting it again multiple times.

nemal nemal L : Thanks for getting back and providing all the logs. Much appreciated. I have compared your logfiles with mine. Still digging, but maybe an idea: What kind of tuners are you using? DVB-something (USB / otherwise)? A Sat>IP server? Or no tuners at all (just IPTV or similar)?

Upgrades to the latest maintenance release (TVH 4.2.6) are now available (see post #1). The new packages contain a fix for installations on non-standard volumes. As always, don't forget to backup before upgrading and keep reporting any issues you might run into.

Martin Walter Walter
Thank you for the latest update (and all priors). Any interest in integrating comskip?

I believe a comskip package is already available, as beta, but still...
https://synocommunity.com/package/comskip

Martin Walter wrote:

Upgrades to the latest maintenance release (TVH 4.2.6) are now available (see post #1). The new packages contain a fix for installations on non-standard volumes. As always, don't forget to backup before upgrading and keep reporting any issues you might run into.

Thanks a lot!
This new version starts on first try on DS418j, running DS6.2(beta). However, after stopping the package, it doesn't start again until after a DS reboot. Nothing is visible in the TVH log either.
After the reboot, it starts automatically.

Martin Walter wrote:

nemal nemal L : Thanks for getting back and providing all the logs. Much appreciated. I have compared your logfiles with mine. Still digging, but maybe an idea: What kind of tuners are you using? DVB-something (USB / otherwise)? A Sat>IP server? Or no tuners at all (just IPTV or similar)?

No worries. I still don't have a tuner so I can't even test Tvheadend for what it is supposed to do.

Martin Walter wrote:

Upgrades to the latest maintenance release (TVH 4.2.6) are now available (see post #1). The new packages contain a fix for installations on non-standard volumes. As always, don't forget to backup before upgrading and keep reporting any issues you might run into.

That update seems to have fixed the start/stop issue. I updated the package to 4.2.6 and now Tvheadend starts and stops gracefully reliably.

@Olof Sandberg : OK, at least you have got a way to get it running then. I'm really out of ideas what might cause this, but will keep it in mind. Maybe others run into the problem too, which might give us more hints on the rationales. I hope you can still use the package despite those limitations for the time being...

nemal nemal L: Great. Then it was most likely an issue with the old 4.2.5 version rather than the Synology-specific packaging. Either way: As long as it works, you can finally purchase and install your tuners now! ;-)

Martin Walter wrote:

@Olof Sandberg : OK, at least you have got a way to get it running then. I'm really out of ideas what might cause this, but will keep it in mind. Maybe others run into the problem too, which might give us more hints on the rationales. I hope you can still use the package despite those limitations for the time being...

Oh, I'm super grateful for your work! The package error is not really a big problem, since the build is really stable. And this is a big step-up in terms of my IPTV experience. Thanks a lot!!!

I'm having a problem with the EPG time on my Synology DS918 running TVHeadend 4.2.5-12. All EPG times are always wrong listed in UTC time (2 hours too early) but the Synology server has correct UTC+2 time, the network under DVB-Input is set to locale time and even when I set it to UTC+2 the EPG time still remains wrong (UTC time). On my second server DS-916 I'm having exactly the same problem.

Try setting the time in the tvh-network tab to UTC.

Perfect solution, works on both servers. But has to be corrected in the software, because makes not much sense as it is right now.

Having difficulties on a DS216j with DSM 6.1.6-15266 (Update 1) when trying to install the latest TVH version (4.2.6, armada 38x build): The package does not start in the package manager. When trying to start in manually in /var/packages/tvheadend/scripts/, I get the following errors:

./service-setup: line 6: [: : integer expression expected
Starting ...
./service-setup: line 18: type: service_prestart: not found
./start-stop-status: line 29: [: : integer expression expected

Seems that several of the required parameters like "SYNOPKG_DSM_VERSION_MAJOR" are not available on my system.

What should I do?

Thanks a lot in advance!

First of all, give it time. After the upgrade and before starting, TVH performs a backup, which can take several minutes. Then, recordings might have to be moved, which can take a lot of time. Just start it and let it run for an hour or so (ignore the run state in the package manager). After waiting, try to log into the TVH Web-userinterface. IF it works, fine. If not, provide log files please. You will find instructions how to retrieve those if you read back into this thread.

Btw, the package has to be started via the package manager. It cannot be started manually anymore.

The 4.2.6 package you guys have tested has been accepted and published on the Synocommunity repository and can be obtained from there. This thread might be reactivated with future testing packages. For the time begin, please report any Synology-package specific issues with the Synocommnity. The initial post has been updated and contains the relevant links. Many thanks to all testers and contributors here!

I have just installed the (latest version of this) package on my Synology DS1515+ running the latest DSM.
I have a dual tuner HDHomeRun.
I am based in the UK.

I am a noob, so I have no idea what I'm doing. However, having set up a network and linked it to the two tuners I am stuck. When I click on Force scan, nothing happens (nothing in the logs either).

I am doing something wrong for sure, but seeing as there are 0 docs for these things, I fail to see what I could try.

Any ideas?

As long as the tuners show up, you are in a good place.
Take a look here:
http://docs.tvheadend.org/configure_tvheadend/
This is work-in-progress but contains the key elements.
Or search the internet for some other standard configuration instructions.

Basically, you have to
(1) Define the right network you are using (probably US_ATSC, but not sure)
(2) Assign the networks to the tuners AND activate the tuners
(3) Scan for muxes and services
(4) Map services to channels

Click on the little cog wheel on the lower right hand side of the web interface to see log entries. This definitely helps to see when something goes wrong in one of the steps above...

Thank you Martin.
I have defined the network; like I said, I'm based in the UK.
I have indeed read through that wiki article, but it offers no relevant information.
I'm surprised that there are no docs for setting this stuff up. I'm thinking of typing it all up, if I manage to figure it out.

In any case, like I said, my issue is that "Force scan" does nothing. And as I said there is nothing in the logs either.

One weird thing was that my HDHomeRun was not identified as DVB-T, but DVB-C. I had to force it to DVB-T.

Does anyone have any relevant information based on the above?

Steven Moschidis wrote:

Thank you Martin.
I have defined the network; like I said, I'm based in the UK.
I have indeed read through that wiki article, but it offers no relevant information.
I'm surprised that there are no docs for setting this stuff up. I'm thinking of typing it all up, if I manage to figure it out.

In any case, like I said, my issue is that "Force scan" does nothing. And as I said there is nothing in the logs either.

One weird thing was that my HDHomeRun was not identified as DVB-T, but DVB-C. I had to force it to DVB-T.

Does anyone have any relevant information based on the above?

When Martin says "Scan for muxes and services" he means you either need to manually add the frequencies or use a pre-defined list (not recommended as they're out of date).

Here's an example of my mux list.

So are you saying that I have to manually add all the muxes (as the predefined lists are fubar)?

I thought the "Force scan" option in the network tab was supposed to make tvheadend discover all available muxes direct from the tuner. Is that not the case? If not, then why not? What is it supposed to do?

I have a friend who set up tvheadend on a pi (or nuc) using the same hdhomerun as I have. He fired up tvheadend, added the network, linked it to the tuners, hit the force-scan button and the muxes appeared.