Tvheadend

I also made a upgrade of the XBMC plugin, could that be the problem?

No
It is problem in tvheadend server webgui.

Perhaps, backup failed so the tvheadend process is down.. Check the log files...

Jaroslav Kysela wrote:

Perhaps, backup failed so the tvheadend process is down.. Check the log files...

I have same problem and I have done a new clean installation with version v3.9.1498 and the webui doesn't work.

OK, is something in the log file ? Have you tried another browser ? Could you provide some more information ? Browser cannot connect or hangs ?

For me on version 3.9.1499 work OK

Jaroslav Kysela wrote:

OK, is something in the log file ? Have you tried another browser ? Could you provide some more information ? Browser cannot connect or hangs ?

Which log file is of interest?

I have tried with both Chrome and IE and I only get "Unable to load page".

When I run v3.9.1500:

./tvheadend -u hts -g video -c /home/hts/.hts/tvheadend/

I just get the following message:

2014-09-16 20:52:08.815 [ INFO] charset: 138 entries loaded
2014-09-16 20:52:09.014 [ INFO] linuxdvb: adapter added /dev/dvb/adapter3
2014-09-16 20:52:09.210 [ INFO] linuxdvb: adapter added /dev/dvb/adapter2
2014-09-16 20:52:09.406 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2014-09-16 20:52:09.602 [ INFO] linuxdvb: adapter added /dev/dvb/adapter0
Segmentation fault (core dumped)

and the it exit to command line again.

Mikael Persson wrote:

When I run v3.9.1500:

./tvheadend -u hts -g video -c /home/hts/.hts/tvheadend/

I just get the following message:

2014-09-16 20:52:08.815 [ INFO] charset: 138 entries loaded
2014-09-16 20:52:09.014 [ INFO] linuxdvb: adapter added /dev/dvb/adapter3
2014-09-16 20:52:09.210 [ INFO] linuxdvb: adapter added /dev/dvb/adapter2
2014-09-16 20:52:09.406 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2014-09-16 20:52:09.602 [ INFO] linuxdvb: adapter added /dev/dvb/adapter0
Segmentation fault (core dumped)

and the it exit to command line again.

If I look in the syslog it's look like:

[434829.360288] init: tvheadend main process (21853) killed by SEGV signal
[434829.360309] init: tvheadend main process ended, respawning
[434831.420291] init: tvheadend main process (21874) killed by SEGV signal
[434831.420312] init: tvheadend main process ended, respawning
[434832.856314] init: tvheadend main process (21899) killed by SEGV signal
[434832.856335] init: tvheadend main process ended, respawning
[434834.944805] init: tvheadend main process (21920) killed by SEGV signal
[434834.944826] init: tvheadend main process ended, respawning
[434836.390647] init: tvheadend main process (21945) killed by SEGV signal
[434836.390667] init: tvheadend main process ended, respawning
[434838.433243] init: tvheadend main process (21972) killed by SEGV signal
[434838.433270] init: tvheadend main process ended, respawning
[434839.876304] init: tvheadend main process (21997) killed by SEGV signal
[434839.876328] init: tvheadend main process ended, respawning
[434841.940293] init: tvheadend main process (22018) killed by SEGV signal
[434841.940313] init: tvheadend main process ended, respawning
[434842.984300] init: tvheadend main process (22043) killed by SEGV signal

So the tvheadend doesn't seems to start at all.

Please, follow https://tvheadend.org/projects/tvheadend/wiki/Debugging to get the location of the segfault..