Menu
What's new
By:
Filters Better Search

Recent content by _me_myself_and_i_

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    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...
  2. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    I was using the former. For now I uninstalled and am using the firmware’s built in ntp.
  3. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    FYI - ntpMerlin also breaks after upgrading. Same issue where it's trying to load 32bit libssl.so.1.1 from /usr/lib
  4. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Well, it all depends on what you’ve installed.
  5. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Here's my script, if useful: https://github.com/dfelicia/backup-merlin-linode
  6. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Yes. I rolled back everything. (Renamed /tmp/mnt/usb/entware and restored that folder from backup.)
  7. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    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 ->...
  8. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    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.
  9. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    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.
  10. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Yes, I also upgraded entware packages this morning.
  11. M

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Please select an option: s checking syslog-ng daemon ... alive. checking system for necessary scribe hooks ... checking S01syslog-ng ... present. checking service-event ... present. checking post-mount ...
  12. M

    Unbound could not open autotrust file for writing

    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...
  13. M

    Unbound could not open autotrust file for writing

    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...
  14. M

    Unbound could not open autotrust file for writing

    Can you elaborate? How would one do this?
  15. M

    Unbound could not open autotrust file for writing

    Hi, @Martineau After a very long stretch of flawless uptime, unbound died on me, today. It seemed to have happened just after the cron job to update adblock sites completed, and error was: Could not open autotrust file for writing /root.key.31931-0-21f5b430 The only way I could get it...
See more
Top