Tvheadend

Try to enable the service and restart the computer:

systemctl enable tvheadend

See also: [[http://tvheadend.org/issues/4746]]

Hi

service should be enabled.

I did reconfigure tvheadend
- also install --reinstalled tvheadend

no change

when i start is via command line with:
it looks fine, gui is starting but no TV_adapter, even the log is showing channels, see attached file.

tvheadend -d -s -D -l /var/log/tvheadened.log

also
sudo service tvheadend status -l

shows results

but I do not get detailed info about the error! -> tvheadend.service: Failed with result 'exit-code'.

● tvheadend.service - Tvheadend - a TV streaming server and DVR
Loaded: loaded (/lib/systemd/system/tvheadend.service; enabled; vendor preset: enabled)
Active: inactive (dead)

Nov 29 09:30:30 UB9 systemd¹: tvheadend.service: Unit entered failed state.
Nov 29 09:30:30 UB9 systemd¹: tvheadend.service: Failed with result 'exit-code'.
Nov 29 09:31:24 UB9 systemd¹: tvheadend.service: Service hold-off time over, scheduling restart.
Nov 29 09:31:24 UB9 systemd¹: Stopped Tvheadend - a TV streaming server and DVR.
Nov 29 09:31:24 UB9 systemd¹: Starting Tvheadend - a TV streaming server and DVR...
Nov 29 09:31:24 UB9 systemd¹: tvheadend.service: Control process exited, code=exited status=1
Nov 29 09:31:24 UB9 systemd¹: Failed to start Tvheadend - a TV streaming server and DVR.
Nov 29 09:31:24 UB9 systemd¹: tvheadend.service: Unit entered failed state.
Nov 29 09:31:24 UB9 systemd¹: tvheadend.service: Failed with result 'exit-code'.
Nov 29 09:31:40 UB9 systemd¹: Stopped Tvheadend - a TV streaming server and DVR.

which are the specific access rights?
which user should do the install?
hts ?

update :

now I managed to start tvheadend from command line.
but the service always fails

--
-- Unit tvheadend.service has begun starting up.
Nov 29 10:24:44 UB9 systemd¹: tvheadend.service: Control process exited, code=exited status=1
Nov 29 10:24:44 UB9 systemd¹: Failed to start Tvheadend - a TV streaming server and DVR.
-- Subject: Unit tvheadend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tvheadend.service has failed.
--
-- The result is failed.

no detailed information in journal even I enabled debug in /etc/default/tvheadend

also reenabling the service does not help:

sudo systemctl enable tvheadend
Synchronizing state of tvheadend.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable tvheadend

very strange

Run

sudo journalctl -t tvheadend

In your /etc/default/tvheadend you should see..

#
# Default configuration for tvheadend

# systemd
# See tvheadend --help for more - default "-u hts -g video" 
OPTIONS="-u hts -g video" 

# sysvinit
#
# Editing the following variables has no effect when using systemd
# modify the OPTIONS variable (above) instead.
#
# TVH_ENABLED
#   set to 0 to disable upstart job
TVH_ENABLED=1

Hi

I do not have
OPTIONS="-u hts -g video"

but

1. Default configuration for tvheadend #

1. TVH_ENABLED
2. set to 0 to disable upstart job
   TVH_ENABLED=1

1. TVH_USER
2. if set to "" will run as root
   TVH_USER="hts"

1. TVH_GROUP
2. if set to "" will run as root
   TVH_GROUP="video"

this should be the same, right?

or should I add your option:
OPTIONS="-u hts -g video"

See attached journal file as requested.

Thanks for supporting
T

thomas reisinger wrote:

Hi

I do not have
OPTIONS="-u hts -g video"

but

1. Default configuration for tvheadend #

1. TVH_ENABLED
2. set to 0 to disable upstart job
   TVH_ENABLED=1

1. TVH_USER
2. if set to "" will run as root
   TVH_USER="hts"

1. TVH_GROUP
2. if set to "" will run as root
   TVH_GROUP="video"

this should be the same, right?

or should I add your option:
OPTIONS="-u hts -g video"

See attached journal file as requested.

Thanks for supporting
T

OK, it looks like you didn't accept the config changes on upgrade (for 4.3 only I assume you're using unstable).

Just add the options line to the top & things should start working again..

Ok thanks will add the line
yes I am using unstable

looks like it is running now.

could restart the service without error

thanks