Can't connect via browsers

Sudden problem this morning on both T2s with latest webif and packages: all attempts to connect via http fail with an "unable to connect" message, but connections via file manager, ftp and telnet are OK.

Ideas?
 

davew04

New Member
Ditto for me.
My auto-updates are on.
The web interface was working fine a few minutes ago. When I connected I saw the 'acknowledge updates' banner with (I think) three items in and clicked on it as usual, added a couple of programmes to my schedule, and after the obligatory reboot, the web interface doesn't work any more but FTP is OK.

Just in case it's relevant, I have one of (what I think is) the later-model HDRs - one where I have to do a manual reboot and wait for a full shutdown before restarting if I change the schedule since if I reboot from the web-if my HDR comes up unable to find channels.
 

Stummery

Member
Mine is working OK at the moment. I do manual updating and last updated yesterday.

My package management available upgrades is showing webif, rs and lighttpd

I will not be doing any upgrades yet!:(

If this is a package problem, how would someone who has already done a manual upgrade get back in to the webif to correct it when the repaired package is released ?
 
Last edited:

af123

Administrator
Staff member
There was an update to the web server software last night but it worked fine on all of my boxes, and that of one other person who has tested it for me. I wonder what's happening here.

Ditto for me.
My auto-updates are on.
The web interface was working fine a few minutes ago. When I connected I saw the 'acknowledge updates' banner with (I think) three items in and clicked on it as usual, added a couple of programmes to my schedule, and after the obligatory reboot, the web interface doesn't work any more but FTP is OK.
Using FTP, can you look at the /tmp/webif.log file and see if contains anything?
 
Last edited:

prpr

Well-Known Member
There was an update to the web server software last night but it worked fine on all of my boxes, and that of one other person who has tested it for me. I wonder what's happening here.
Poking through a diff, I see references like this:
Code:
-dependency_libs=''
+dependency_libs=' -L/mod/lib /mod/lib/libpcre.la'
but no /mod/lib/libpcre.la file is found.
"service start lighttpd" complains:
Code:
Starting lighttpd...
/mod/sbin/lighttpd: can't load library 'libpcre.so.1'
Done.
and there is no trace of libpcre.so.1 anywhere on the system.
 

raydon

Well-Known Member
Poking through a diff, I see references like this:
Code:
-dependency_libs=''
+dependency_libs=' -L/mod/lib /mod/lib/libpcre.la'
but no /mod/lib/libpcre.la file is found.
"service start lighttpd" complains:
Code:
Starting lighttpd...
/mod/sbin/lighttpd: can't load library 'libpcre.so.1'
Done.
and there is no trace of libpcre.so.1 anywhere on the system.
Spot on prpr !
Got mine working again temporary by using a kludge. I created a symlink named libpcre.so.1 pointing to another lib that does exist.
ln -s /mod/lib/libproc-3.2.8.so /mod/lib/libpcre.so.1
Don't recommend this for everyone, just wait till af123 posts the fix.
I very minor point I noted when starting lighttpd from command line. I got this error.
cat: can't open '/mod/etc/lighttpd/extra.d/*.conf': No such file or directory
which is caused by an 'include' entry in the lighttpd config file. Can this be made conditional on file existence to prevent the error ?
 

prpr

Well-Known Member
Spot on prpr !
;)
when starting lighttpd from command line. I got this error.
cat: can't open '/mod/etc/lighttpd/extra.d/*.conf': No such file or directory
which is caused by an 'include' entry in the lighttpd config file. Can this be made conditional on file existence to prevent the error ?
Yes, I wondered about that too when I was going through the diff, but haven't yet had the server running (except immediately after package upgrade when it was somehow started automatically OK).
 
Last edited:

af123

Administrator
Staff member
and there is no trace of libpcre.so.1 anywhere on the system.
Hmm - there is a libpcre package which should have been installed as a dependency.
Edit: but for some reason it's missing the .so : (
Fix coming later but I've pulled the package for now.
 

prpr

Well-Known Member
If this is a package problem, how would someone who has already done a manual upgrade get back in to the webif to correct it when the repaired package is released ?
If you have auto-update installed, it'll (hopefully) fix itself overnight as soon as the new package is released. If you don't, it'll be the command line I think.
It's hard work to downgrade to a working Webif as well. You need to do that from the command line and you need a copy of the old package.
Download it manually using a browser (from http://hpkg.tv/hdrfoxt2/base/lighttpd_1.4.35-4_mipsel.opk ) and get it on to the Humax somehow (you can't seem to download it on the Humax itself using wget for example).
Then you can force reinstall, having changed directory to where you put the file:
Code:
humax# opkg --force-downgrade install lighttpd_1.4.35-4_mipsel.opk
 
Last edited:

prpr

Well-Known Member
Hmm - there is a libpcre package which should have been installed as a dependency.
There is, but...
Code:
humax# opkg files libpcre
Package libpcre (8.37) is installed on root and has the following files:
/mod/include/pcre.h
/mod/include/pcrecpparg.h
/mod/lib/pkgconfig/libpcreposix.pc
/mod/lib/pkgconfig/libpcrecpp.pc
/mod/lib/pkgconfig/libpcre.pc
/mod/include/pcrecpp.h
/mod/bin/pcretest
/mod/bin/pcregrep
/mod/bin/pcre-config
/mod/include/pcreposix.h
/mod/include/pcre_stringpiece.h
/mod/include/pcre_scanner.h
...no library.
 

af123

Administrator
Staff member
If you have auto-update installed, it'll fix itself overnight as soon as the new package is released. If you don't, it'll be the command line I think.
There will be a diagnostic to make it easy for people, but now that the .37 package has been removed an 'opkg update && opkg install lighttpd --force-reinstall' should be sufficient.
 

Wallace

Traveler 34122
Bummer. Not at home at the moment, but I have just tried to access the WebIf on both my HDRs via my VPN and its a no-go.

I do have autoupdate installed on both boxes. How often does this feature run? Referring back to a post by prpr, I 'guess' its only once a day.
 

prpr

Well-Known Member
I have just tried to access the WebIf on both my HDRs via my VPN and its a no-go.
Have you not got SSH/telnet access then?
I do have autoupdate installed on both boxes. How often does this feature run? Referring back to a post by prpr, I 'guess' its only once a day.
Yes, 2:05 am
 

Wallace

Traveler 34122
Not at the moment. I have missed the 14:00 - 14:30 window when the boxes wake.

It will have to wait until I get home later.

But thanks for the info.
 

MadMart

New Member
There will be a diagnostic to make it easy for people, but now that the .37 package has been removed an 'opkg update && opkg install lighttpd --force-reinstall' should be sufficient.

Tried the opkg cmd suggested, but get:

Installing lighttpd (1.4.37) to root...
Collected errors:
* opkg_download_pkg: Package lighttpd is not available from any configured src.
* opkg_install_pkg: Failed to download lighttpd. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package lighttpd.​
 

MadMart

New Member
I did - simply cut and pasted the cmds, so the package list still appears to reference .37 ?

humax# opkg update && opkg install lighttpd --force-reinstall
Downloading hpkg.tv / hdrfoxt2 / base / Packages.gz.
Inflating hpkg.tv / hdrfoxt2 / base / Packages.gz.
Updated list of available packages in /mod / var / opkg / base.
No packages removed.
Installing lighttpd (1.4.37) to root...
Collected errors:
* opkg_download_pkg: Package lighttpd is not available from any configured src.
* opkg_install_pkg: Failed to download lighttpd. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package lighttpd.
humax#​

Package obviously already removed on second run of same command.

(had to tweak urls to be able to post)
 
Top