JoeBloggs911
Member
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?
Ideas?

Same here...
Also connection to RS is fine
Edit: using firefox and ie...

Using FTP, can you look at the /tmp/webif.log file and see if contains anything?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?
Poking through a diff, I see references like this: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.
-dependency_libs=''
+dependency_libs=' -L/mod/lib /mod/lib/libpcre.la'
Starting lighttpd...
/mod/sbin/lighttpd: can't load library 'libpcre.so.1'
Done.
Spot on prpr !Poking through a diff, I see references like this:
but no /mod/lib/libpcre.la file is found.Code:-dependency_libs='' +dependency_libs=' -L/mod/lib /mod/lib/libpcre.la'
"service start lighttpd" complains:
and there is no trace of libpcre.so.1 anywhere on the system.Code:Starting lighttpd... /mod/sbin/lighttpd: can't load library 'libpcre.so.1' Done.
Spot on prpr !

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).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 ?
Hmm - there is a libpcre package which should have been installed as a dependency.and there is no trace of libpcre.so.1 anywhere on the system.
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.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 ?
humax# opkg --force-downgrade install lighttpd_1.4.35-4_mipsel.opk
There is, but...Hmm - there is a libpcre package which should have been installed as a dependency.
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
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.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.
Have you not got SSH/telnet access then?I have just tried to access the WebIf on both my HDRs via my VPN and its a no-go.
Yes, 2:05 amI 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.
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.