• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

Lots of errors updating all packages, help!

af123 said:
Ah wait, sorry, try this:

Code: 
/bin/wget -qO- "http://hpkg.tv/diag/ssl/fix" | /bin/sh
Click to expand...

That says:

owenhdrfoxt2# /bin/wget -qO- "http://hpkg.tv/diag/ssl/fix" | /bin/sh
Connecting to hpkg.tv (89.248.55.75:80)
libcrypto.so.1.1 100% |*******************************| 3557k 0:00:00 ETA
Connecting to hpkg.tv (89.248.55.75:80)
libssl.so.1.1 100% |*******************************| 798k 0:00:00 ETA
owenhdrfoxt2#

So is it all sorted now?
 
MartinLiddle said:
It certainly looks as though it has downloaded. Try one of the methods that was previously failing and see if they now succeed.
Click to expand...

This was the only error I was seeing. What do you mean by the term "method" in this context?

You say it has downloaded, but has it installed?
 
AF's diagnostic copies the openssl libraries to the locations where they should have been installed. So, after restarting in case of locked files, the libraries will be correctly installed and available for use.

Test it by downloading a resource via https. Eg (to adapt an earlier post): wget -qO- "https://wiki.hummy.tv/wiki/Diagnostic_Utilities" | less.
 
Maybe it's late and I'm tired, but having just arrived at this thread because I just appear to have buggered one of my two humax doing updates, I'm not sure what the actual route out is.

What I did:
I haven't updated for probably six months, so just swung by to update both. As luck would have it I tried to update the first manually, i.e. packages one by one.
jim updated fine.
OpenSSL barfed. and returned I think a 104. Anyway it also showed a small dialogue of XML which included this same text.
The next one barfed too, so I gave up and clicked back to the main EPG.
At which point I got a 500 Internal Server Error.

Tried physically powering off and on the box to reboot a couple of times, but still the same.

SMB access still works, and the remote works but the web i/f doesn't.

Figuring it was the openssl update I tried manually updating the other, just without that one. All went fine.

So it sounds sort of like what d/f was describing in is first post in the thread. it was openssl 1.1.1.b-1 that I was at.

However step by step instructions to get out of this would be nice. If they're already there I apologise, I'm just not seeing them in the discussion.

Thanks.
 
Darn, couldn't leave it...
Well mine wasn't quite as painful to recover.

After a quick peruse, I decided to simply use the upgrade option on the SSH menu. There were a couple of messages at the end of the upgrade that said
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'

so after a couple of attempts to use the diag menu command I worked out that I had to drop to CLI to enter the diag ssl/fix command. This downloaded the two files. Whether I needed to do this step or not I have no idea as the web if came back after the previous upgrade command had completed.

Being cautious I then went to the second machine. This only needed the openssl upgraded as I had done the others manually before.
The openssl upgraded without any error messages. The Web was and is solid on that box.
 
One of the advantages of using autoupdating is that changes with interactions to other packages can be distributed in the correct order over a few days. When doing a mass upgrade there is little control over the order packages are installed and so, sometimes, you need to repeat the upgrade until the inter-dependencies sort themselves out.
 
But the disadvantage of auto updating is the CF may stop working at a time when I can't deal with it, due to either available free time or physical access. My parents run a box with CF on it, which I see about four times a year. There is no way I can have that auto updating.
 
Black Hole said:
I presume, without using the WebIF at all. Under those circumstances there is nothing to be gained by package auto-updates anyway, they won't be using any affected functionality.
Click to expand...

Auto unprotect is running, as is remote scheduling. If they're away and realise they've forgotten to set something to record, they phone or text me and ask me to set a recording. Fan package is also running to reduce fan noise and improve disc life.
 
Black Hole said:
So... exactly what I said then.
Click to expand...

I don't understand what point you are trying to make, it seems contradictory.

Fan, auto unprotect, remote scheduling are all packages that might get auto updated, so there would be something to be gained if you wanted them regularly updated. You are implying only webif gets updated, which is not true,
 
Not at all. fan and auto-unprotect are autonomous, requiring no input from user interaction with WebIF. They are also unlikely to be updated, and even if they were it would be to add functionality rather than correct a bug.

rs is also autonomous, and does little more than check in with the RS service to upload status and download commands. It might require an update to overcome some problem RS was having with some change in data formats, but in general any mods required will be done at the RS server rather than by an update to the rs package.

Your parents are not using the WebIF user interface, which is clearly what I meant. Presuming there are no bugs, and nothing changes in the operating conditions, there is no reason to update. The only thing to be gained by an update is a bug correction, or new functionality - which they are not using so they don't need. An "unattended" installation obviously must not be auto-updated, just in case something goes wrong.
 
I'm having all these problems again updating my aunt's box, but over wifi to a hot spot on my iPad. Still can't get libcrypto.so to update.
 
Here is what my aunt's box gives for fixweb:

Please select option: fixweb
Removing package webif from root...
Not deleting modified conffile /mod/webif/html/favicon.ico.
Installing webif (1.4.8-8) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/webif_1.4.8-8_mipsel.opk.
Configuring webif.
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
Collected errors:
* file_md5sum_alloc: Failed to open file /mod/webif/html/favicon.ico: No such f
ile or directory.

Press return to continue:
 
This looks a bit better:

irenehdrfoxt2# /bin/wget -qO- "http://hpkg.tv/diag/ssl/fix" | /bin/sh
Connecting to hpkg.tv (89.248.55.75:80)
libcrypto.so.1.1 100% |*******************************| 3557k 0:00:00 ETA
Connecting to hpkg.tv (89.248.55.75:80)
libssl.so.1.1 100% |*******************************| 798k 0:00:00 ETA
irenehdrfoxt2# opkg --force-reinstall install openssl
No packages removed.
Installing openssl (1.1.1.d-1) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/openssl_1.1.1.d-1_mipsel.opk.
Configuring openssl.
irenehdrfoxt2#
 
But fixweb still complains:

Please select option: fixweb
Removing package webif from root...
Not deleting modified conffile /mod/webif/html/favicon.ico.
Installing webif (1.4.8-8) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/webif_1.4.8-8_mipsel.opk.
Configuring webif.
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
Collected errors:
* file_md5sum_alloc: Failed to open file /mod/webif/html/favicon.ico: No such f
ile or directory.
 
Everything now works except fixweb, I think there is something wrong with that command. Repeating the commands in posting #38 then fix-flash-packages (which may or may not have been necessary but it re-installed webif fine), after reboot the webif works with https.
 
You must log in or register to reply here.
Back
Top