Project

General

Profile

Bug #1442

HTTP error 500 randomly when using '--enable-bundle'

Added by virtual dj about 12 years ago. Updated almost 12 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
User Interface
Target version:
Start date:
2012-12-01
Due date:
% Done:

0%

Estimated time:
Found in version:
5d2197c30f
Affected Versions:

Description

I've built the latest git using:
./configure --disable-avahi --enable-bundle --disable-zlib --release
and I'm running it on a QNAP x86 NAS.

Randomly some elements of the UI are not displayed and loaded correctly and there are errors in the TVHeadend debug log.
Sometimes they are a lot, other times only a few (I think that's because the Firefox browser saves the items in the cache).

Example 1
Dec 01 15:51:33 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/grid/col-move-bottom.gif
Dec 01 15:51:33 [ERROR]:HTTP: 192.168.1.1: /static/extjs/resources/images/default/grid/col-move-bottom.gif -- 500
Dec 01 15:51:33 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/grid/loading.gif
Dec 01 15:51:33 [ERROR]:HTTP: 192.168.1.1: /static/extjs/resources/images/default/grid/loading.gif -- 500
Dec 01 15:56:03 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/sizer/nw-handle.gif
Dec 01 15:56:03 [ERROR]:HTTP: 192.168.1.1: /static/extjs/resources/images/default/sizer/nw-handle.gif -- 500
Dec 01 15:56:03 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/sizer/se-handle.gif
Dec 01 15:56:03 [ERROR]:HTTP: 192.168.1.1: /static/extjs/resources/images/default/sizer/se-handle.gif -- 500

Example 2
Dec 01 16:04:12 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/panel/left-right.gif
Dec 01 16:04:12 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/panel/top-bottom.gif
Dec 01 16:04:12 [ERROR]:HTTP: 192.168.0.7: /static/extjs/resources/images/default/panel/left-right.gif -- 500
Dec 01 16:04:12 [ERROR]:HTTP: 192.168.0.7: /static/extjs/resources/images/default/panel/top-bottom.gif -- 500

Example 3
Dec 01 16:07:25 [ERROR]:webui: failed to open src/webui/static/icons/world.png
Dec 01 16:07:25 [ERROR]:HTTP: 192.168.0.7: /static/icons/world.png -- 500
Dec 01 16:07:25 [ERROR]:webui: failed to open src/webui/static/multiselect/resources/bottom2.gif
Dec 01 16:07:25 [ERROR]:HTTP: 192.168.0.7: /static/multiselect/resources/bottom2.gif -- 500

Example 4
Dec 01 16:07:57 [ERROR]:webui: failed to open src/webui/static/livegrid/resources/css/ext-ux-livegrid.css
Dec 01 16:07:57 [ERROR]:HTTP: 192.168.0.7: /static/livegrid/resources/css/ext-ux-livegrid.css -- 500
Dec 01 16:07:57 [ERROR]:webui: failed to open src/webui/static/extjs/ext-all-debug.js
Dec 01 16:07:57 [ERROR]:HTTP: 192.168.0.7: /static/extjs/ext-all-debug.js -- 500
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/form/trigger.gif
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/grid/grid-blue-split.gif
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.0.7: /static/extjs/resources/images/default/grid/grid-blue-split.gif -- 500
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.0.7: /static/extjs/resources/images/default/form/trigger.gif -- 500
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/extjs/resources/images/default/grid/refresh-disabled.gif
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.0.7: /static/extjs/resources/images/default/grid/refresh-disabled.gif -- 500
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/icons/eye.png
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.1.1: /static/icons/eye.png -- 500
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/icons/information.png
Dec 01 16:07:58 [ERROR]:webui: failed to open src/webui/static/icons/wrench.png
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.0.7: /static/icons/wrench.png -- 500
Dec 01 16:07:58 [ERROR]:HTTP: 192.168.0.7: /static/icons/information.png -- 500

I've checked the build.linux/bundle.c and the files are there.
The same happens when building with the --enable-zlib option.


Files

x86.tar.bz2 (2.34 MB) x86.tar.bz2 Compressed x86 binary with issues virtual dj, 2012-12-03 18:55

History

#1

Updated by Adam Sutton about 12 years ago

  • Status changed from New to Need feedback

I cannot replicate this, I have tried a completely clean build:

$ git clean -dfx
$ ./configure --enable-bundle --disable-zlib
$ make
$ cp build.linux/tvheadend /tmp
$ cd /tmp
$ ./tvheadend

Note: the copying and running from tmp was to remove the possibility it was picking the local source files up based on the cwd.

This works fine. Also this mechanism is currently being employed by things like the OpenELEC tvh service addon. So there are plenty of users running in this way (OE is not using --disable-zlib, but I've checked both).

Note: I also doubled checked that chrome (my browser) did in fact load each resource a fresh, and I also did a few spot checks with telnet.

Has this been working and then stopped?

Can you check the size of the binary that you're using:

ls -l $(which tvheadend)

Adam

#2

Updated by virtual dj about 12 years ago

I cannot replicate this, I have tried a completely clean build:

$ git clean -dfx
$ ./configure --enable-bundle --disable-zlib
$ make
$ cp build.linux/tvheadend /tmp
$ cd /tmp
$ ./tvheadend

Previously I've tried to remove the folder and issue a make clean and the problem persisted.
I've just tried git clean and it's the same.

Note: the copying and running from tmp was to remove the possibility it was picking the local source files up based on the cwd.

I'm compiling the sources in a virtual machine and then running the binary file on another virtual machine and the QNAP.

Note: I also doubled checked that chrome (my browser) did in fact load each resource a fresh, and I also did a few spot checks with telnet.

I was able to replicate the issue by running the attached x86 binary with:
./tvheadend -C -d
both in the QNAP and in a Debian VM with kernel 2.6.32-5-686 and gcc 4.7.1-8.

Then you clear your Firefox (or Chrome?) temporary files with Tools > Options... > Advanced tab > Network tab > Web cache > Clear now and you'll get this (with different files every time):

Of course the Web UI of the client shows missing pieces, i.e. the ones that don't load.

Has this been working and then stopped?

It is the first time that I compile a recent version of TVHeadend.
Previous versions that worked for sure with the bundled files were EricV's git version 9b71601b06 and old git version d66746c.

Can you check the size of the binary that you're using:

ls -l $(which tvheadend)

It's 7.6 MB when using "disable-zlib". I've also attached it in a compressed format so you can try.

#3

Updated by Adam Sutton about 12 years ago

Can you try master. A bug was spotted in the bundle code that might account for this.

Adam

#4

Updated by virtual dj almost 12 years ago

Sorry for the long delay of the answer, I was busy with other jobs.
I wasn't able to compile the latest master, because it's broken with this error:

CC              build.linux/src/dvb/dvb_tables.o
/root/tvheadend/tvheadend/src/dvb/dvb_tables.c:633: error: ‘TRANSMISSION_MODE_4K’ undeclared here (not in a function)
make: *** [build.linux/src/dvb/dvb_tables.o] Error 1

However, I tried with a2cec9743280e and it worked.
No more errors in the log and the web UI is OK now. Thanks!

#5

Updated by virtual dj almost 12 years ago

EDIT: Just FYI, the latest version that I can build without errors is 93fe784960.

#6

Updated by luka Zi almost 12 years ago

Same problem. I compile on ARM Synology, Linux DiskStation 2.6.32.12 #2636 Wed Aug 29 04:13:02 CST 2012 armv5tel GNU/Linux,

/opt/tvheadend/src/dvb/dvb_tables.c:633: error: 'TRANSMISSION_MODE_4K' undeclared here (not in a function) make: *** [build.linux/src/dvb/dvb_tables.o] Error 1 /opt/tvheadend #
gcc (GCC) 4.4.7
#7

Updated by Adam Sutton almost 12 years ago

  • Status changed from Need feedback to Fixed
  • Target version set to 3.2
  • Affected Versions 3.2, 3.3 added

Can you submit this as a separate bug report, I think I can see what might have happened. And can you attach the contents of the linux/dvb/version.h file.

I'm closing this as I believe the test of a slightly older version suggests the original bug is now fixed.

Adam

Also available in: Atom PDF