Web interface suddenly stopped working

[philbean]

So tried going to the web-interface tonight..

I'm getting the header loading with the pie chart, but the dotmatrix display on the left is just stuck at Loading... and nothing else happens.
Below is just a blank white page

Tried the usual hard reboot etc. No joy.

On my phone, the mobile interface loads up and most options work OK except 'Packages' where I get "error loading page" and 'Settings' which just takes me to the desktop version page and is stuck as above.


Its yonks since I last did any telnetting.. but I tried some. (v 1.03.12/3.13)
I updated the packages which seemed to work OK and rebooted again but still no joy with the webif.

So I tried 'fixweb' which ran and then ended with

/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'

...


Any ideas?

 

[/df]

Post in thread 'No access to Webif'

Oct 17, 2024

It's difficult to know what the root problem is here. The Jim interpreter is only partially working it seems - it works when run directly, but not when called by the shell to execute a script. We've seen this error several times and never managed to get to the bottom of it.
It's possibly something environmental, but without direct access to the machine it's too difficult/time consuming to diagnose, so, reluctantly, I think you'll have to do the RMA process as BH describes at the bottom of post #2.

• prpr

 

[Black Hole]

And for reference, the "bottom of post #2":

An alternative, avoiding reformatting the disk, is to use the Telnet menu to set RMA mode, reboot, then clear RMA. RMA mode erases the CF /mod folder on disk and sets a flag to prevent reinstallation of WebIF, so you have to clear the flag if you want to reinstall.

 

[philbean]

Blimey.
Might not bother and have to live with a busted webif.
The box is still working perfectly.

 

[philbean]

OK so thinking about what I'd lose I think I'm gonna have to try and fix.

So.. to be clear? RMA mode will wipe my firmware yes?

use the Telnet menu to set RMA mode, reboot, then clear RMA.

To clear RMA do I just telnet back in and turn it off?
RMA mode won't prevent me telneting in? Won't mess with network settings?

RMA mode erases the CF /mod folder on disk and sets a flag to prevent reinstallation of WebIF, so you have to clear the flag

How do I clear this flag?


And then when this is done... do I need to reinstall the custom firmware from scratch?
From USB ?

 

[Black Hole]

RMA mode will wipe my firmware yes?

No. From your own quotes:

RMA mode erases the CF /mod folder on disk

The CF firmware does not reside on disk, only the CF packages (which of course include the WebIF). Reinstalling the packages afresh is what's gonna fix your problem, which is due to the disk contents getting scrambled for one reason or another. WEBIF IS NOT THE CF. WEBIF IS A GUI APP WHICH RUNS IN CF.

To clear RMA do I just telnet back in and turn it off?

Yes.

RMA mode won't prevent me telneting in?

No. That's all handled in the firmware.

Won't mess with network settings?

Why the f*** would it? The Humax firmware handles your network connection (networking is not a custom addition).

How do I clear this flag?

The RMA flag? See above. Just do it.

And then when this is done... do I need to reinstall the custom firmware from scratch?
From USB ?

NO!!!!! I refer you to previous answers. Just do it and stop asking stupid questions.

However, prior to reinstalling the packages (from the installation web page at the WebIF URL), you probably ought to run fixdisk from the maintenance mode menu (you get into maintenance mode from the telnet menu).

 

[philbean]

OK so I ran fixdisk as suggested

I'm getting an output of thousands and thousands of

Inode 9216864 has compression flag set on filesystem without compression support.  Clear? yes

Inode 9216864, i_size is 5721333495262975430, should be 0.  Fix? yes

Inode 9216864, i_blocks is 163184987, should be 0.  Fix? yes

then after about 90 mins it ended with

hmx_int_stor: e2fsck canceled.

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
Memory used: 66676k/102192k (66625k/52k), time: 4893.25/2666.66/797.89
I/O read: 8362MB, write: 5801MB, rate: 2.89MB/s
tee: /tmp/fix-disk.log: I/O error
Mon May 26 17:48:18 BST 2025
Insufficient memory to remove swap. Very large fix-disk log?
sed: can't read /tmp/fix-disk.progress: No such file or directory
ls: /tmp/fix-disk.progress: No such file or directory

I'm assuming this is not good news

 

[/df]

I think BH was suggesting fixdisk after RMA. Did you get to that stage?

What you reported from fixdisk could happen if the filesystem structure has been corrupted so that disk blocks expected to be index blocks (inodes) are actually free blocks, or (bad news) blocks within some of your precious (if it is) content. This corruption is so pervasive that the log file exceeded its available space and the repair stopped.

So:

• running fixdisk again (and again?) might succeed because a large number of bad inode entries will have been cleared already, avoiding the log file overflow
• if not, or if you had previously stashed any precious content elsewhere, you could just reformat the disk
• if fixdisk either did not find any disk errors (as opposed to filesystem errors such as those shown), or corrected any such errors, you could run the filesystem check more easily by putting the disk in a USB caddy attached to a real computer running Linux (natively or booted from a live CD), and that might succeed where the on-box repair doesn't.

However I suspect that, even with a "real computer" it's still possible for a filesystem to be corrupted such that the repair takes longer than anyone is prepared to wait, maybe only completing after DVB-T/T2 broadcasts have been closed, or after the 2038 time_t bomb, or closer to the exhaustion of the Sun's hydrogen supply.

 

[philbean]

LOL Cheers
Yes I did it after the RMA which has indeed fixed my Webif issue. So cheers for that.

Maybe its time to start thinking about a new HDD. Its still the original one in there. Little trooper that it is.