Mine is fine. I did accept the agreements, but doubt that is a factor.
I wrote my own update script (updates A record with DNS provider via REST) and I logs events. This entry is immediately following reboot after upgrade:
Apr 15 17:19:44: Added cron job
Apr 15 17:19:44: WAN IP from...
Bit the bullet and did a factory reset, re-formatted my usb, upgraded to latest 388.1, then spent a couple of hours putting everything back in order. (Again, backups are crucial!)
Everything works as before with no libssl errors. I was on 386.4 before and this debacle was the catalyst I needed...
After restoring my backup I can see what was upgraded this morning:
- terminfo 6.3-1a -> 6.4-1
- column 2.38-2 -> 2.38.1-1
- zoneinfo-europe 2022f-1 -> 2022g-1
- bash 5.1.16-1 -> 5.2.15-1
- liblzma 5.2.7-1 ->...
I restored entware from backup and all is well, again. I think Scribe (or syslog-ng package) will need to be updated to work with newer cyrpto libraries.
Update: indeed it looks like an entware issue.
libssl.so.1.1 was replaced by libssl.so.3, and now syslog-ng is trying to load libssl.so.1.1 from /usr/lib rather than from entware/lib.
Thanks for the reply, @Martineau !
Yes, the actual error was "permission denied." I'm kicking myself for not backing up the log file, as it got overwritten after uninstall/reinstall.
As a result of this debacle, my drive is only a month old and fsck says it's healthy.
This bug report takes a...
This was not the case, and multiple restarts of unbound (and even the router) did not resolve.
I don't think adblock had anything to do with it -it's just the last thing I saw in the log before the error.
Anyway, let's see if Martineu has a chance to reply... no urgency, as it's all working...