Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-22363

Unable to update `core` module to 15.0.12.55 - sha1 did not match

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Asterisk Modules
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.15.1
    • Distro Version:
      FreePBX 15 (Sangoma Linux release 7.8.2003)
    • Distro:
      FreePBX Distro

      Description

      I was running updates with `fwconsole ma upgradeall` from the console, and I'm seemingly unable to ugprade the `core` module:

       

       

      {noformat}
      # fwconsole ma upgradeall
      No repos specified, using: [standard] from last GUI settings
      Module(s) requiring upgrades: core
      Upgrading module 'core' from 15.0.12.51 to 15.0.12.55
      Downloading module 'core'
      Processing core
      Verifying local module download...Redownloading
      Downloading...
      1163434/1163584 [===========================>] 99%The following error(s) occured:
      - File Integrity failed for /var/www/html/admin/modules/_cache/core-15.0.12.55.tgz.gpg - aborting (sha1 did not match){noformat}

       

       

      I checked the signature of the file in question and the GPG key matches.  I looked inside the archive as well, and saw that there was a `module.sig` inside the archive with sha256sums of the module contents (which was itself correctly signed with the same key as the archive as a whole).  I'm not sure where in the world that sha1sum is happening, even.

      Let me know if I can provide any more info!

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                apocalyptech apocalyptech
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.