[webif] Web Interface 1.2.x

Black Hole said:
Yeah, it's the old-school command interface that catches the unwary grown too accustomed to GUI-everything. Before one of AF's magic tweaks it was necessary to issue a command to change the line end handling too.
Click to expand...
That was one of xyz321's tweaks. It's no longer necessary to select the type of line-ending in either windows telnet or PuTTY, I need to update the wiki page.
 
ian_j said:
Browsing the Humax Media Files seems faster though as do searches on the EPG, I don't know if tcpfix could affect these or if it's my imagination.
Click to expand...
It's possible but I haven't done any measurements. I don't know if this is a bug in the Linux kernel implementation of either window scaling or cubic congestion control (2.6.18 /is/ rather old and these features were fairly new at the time). If it is then it could speed everything up.
 
webif 1.2.8-4 will automatically install the tcpfix package which should put an end to problems downloading package updates thereafter (and CFW 3.10 will have this built-in). I've done more testing and it definitely seems to stop the problems occuring.
I've also made changes to the package results and diagnostic result dialogues so that the output is shown as it goes along rather than it just sitting there and all of the output just appearing at the end. Tested in Firefox, Safari and whatever-version-of-IE-is-on-Windows-10.

A good test for both of these is to go to the diagnostics screen and force-reinstall one of the big packages (webif-channelicons is a safe candidate).
 
af123 said:
Please do : ) I had to 'phone a friend to get them to test on IE for me.
Click to expand...
Edge is actually rather nippy. I think that IE is still version 11 on Windows 10. Microsoft must have decided that IE had become so bloated and sluggish that it was time to start again.
 
af123 said:
I've also made changes to the package results and diagnostic result dialogues so that the output is shown as it goes along rather than it just sitting there and all of the output just appearing at the end. Tested in Firefox, Safari and whatever-version-of-IE-is-on-Windows-10.
Click to expand...
Yes, but in Safari/iOS9 the results log screen doesn't keep up with the updates so you still can't see anything happening without scrolling down!
 
I installed bootHDR - which of course is a very long download, and then it sits there for ages with something like "configuring bootHDR" as the last line until it eventually comes up with the "success" tick (I almost gave up waiting).
 
Black Hole said:
I installed bootHDR - which of course is a very long download, and then it sits there for ages with something like "configuring bootHDR" as the last line until it eventually comes up with the "success" tick (I almost gave up waiting).
Click to expand...
Ah, yes, that one does a lot quietly during the configure phase IIRC. Next webif version will scroll the boxes automatically - good test is the resetnew diagnostic.
 
I'm still having problems with package updates, although the behaviour has changed since installing 1.2.8-4.

I just updated from 1.2.8-4 to 1.2.8-5. This time I didn't get the internal server error message, and the update appeared to complete successfully. However, it was again not possible to access the webif afterwards. Only rebooting the box would bring it back.

I'm sure this started happening after I updated lightpd. Is there something I can run to restore an older version, or otherwise fix this behaviour?
 
AJones said:
I'm sure this started happening after I updated lightpd.
Click to expand...
Moi aussi! At the moment every time I upgrade a package I get an "Internal server error" dialog and have to reboot to re-establish access to the WebIf.
The "Internal server error" dialog appears, it seems, at the end of the upgrade process, but before there is a listing about the upgrade process in the pop-up. Dismissing the "Internal server error" dialog results in a "the page cannot be displayed" error. The packages appear to (after the restart) be upgraded, at least according to the package listing. The last upgrade was to WebIf 1.2.8-5 (mentioned in case that will now change the symptoms).

I am positive this started happening after I upgraded lighttpd to 1.4.39-1 a few days ago. I think that "Internal server error"actually occurred at the end of the upgrade of that one; but I am not 100% sure - it might have been the next one after that that ended in "Internal server error" (but definitely one or the other).

Web interface version: 1.2.8-5
Custom firmware version: 3.02 (build 2295)
Humax Version: 1.03.12 (kernel HDR_CFW_3.00)
 
hairy_mutley said:
Have you tried post #222?
Click to expand...

Apologies, I missed that too. I ran the commands in the Windows 10 Telnet client, so hopefully things are fixed now, I'll confirm when there's another package update available.

I seem to be missing some output compared to what others have quoted, in particular the grep command didn't return anything. Does this look OK?

Code: 
humax# opkg update
Downloading http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Inflating http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Updated list of available packages in /mod/var/opkg/base.
humax# opkg upgrade
Configuring lighttpd.
Configuring webif.
SMART: (PASSED)
startstop: 9216
realloc: 0
hours: 5109
spinretry: 0
pending: 0
offline: 0
humax# grep lightpd /mod/var/opkg/info/*.p*
humax#
 
[
QUOTE="AJones, post: 93411, member: 3118"]
I seem to be missing some output compared to what others have quoted, in particular the grep command didn't return anything. Does this look OK?

Code: 
humax# grep lightpd /mod/var/opkg/info/*.p*
[/QUOTE]
You are missing a "t" in lighttpd in your grep command:

grep lighttpd /mod/var/opkg/info/*.p*
 
So I am! Thanks.

Code: 
humax# grep lighttpd /mod/var/opkg/info/*.p*
/mod/var/opkg/info/lighttpd.postinst:  /mod/etc/init.d/S01lighttpd stop
/mod/var/opkg/info/lighttpd.postinst:  /mod/etc/init.d/S01lighttpd start
/mod/var/opkg/info/lighttpd.prerm:/mod/etc/init.d/S01lighttpd stop
humax#

That's better!
 
I have just upgrade to 1.2.8-5 of webif. I was on 1.2.8-4.
The update worked but I could not access webif until I telenetted in an restarted lighttpd.
Which version of webif is supposed to fix this? Or is there something else I need to do?


Sent from my iPad using Tapatalk
 
HarveyB said:
I have just upgrade to 1.2.8-5 of webif. I was on 1.2.8-4.
The update worked but I could not access webif until I telenetted in an restarted lighttpd.
Which version of webif is supposed to fix this? Or is there something else I need to do?


Sent from my iPad using Tapatalk
Click to expand...
You need to run an upgrade from the command line. 'opkg upgrade' from the command line should fix it.
 
You must log in or register to reply here.
Back
Top