<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Ubuntu">Dear Danny,<br>
      <br>
      I have tested the same upgrade path as you did from mr13.1.1 to
      mr13.3.1 and finally to mr13.4.1 and I did not get any errors.<br>
      <br>
      Regarding the 1st problem you mentioned, the prosody_unique_index
      up script should not create any problems as this is only
      introduced in mr13.4.1. Maybe some leftover from prior attempts to
      mr13.4.1 that was not cleaned up?<br>
      <br>
      Regarding the 2nd problem maybe some corrupted data present in the
      DB prior to upgrade?<br>
      <br>
      Best regards,<br>
      Jose Su<br>
      <br>
    </font>
    <div class="moz-cite-prefix">On 8/20/25 21:02, Danny Cappellari via
      Spce-user wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:8ef8ffe249a44881acf8b543d69113b5@connectlife.it">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
      <div id="divtagdefaultwrapper"
style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, &quot;EmojiFont&quot;, &quot;Apple Color Emoji&quot;, &quot;Segoe UI Emoji&quot;, NotoColorEmoji, &quot;Segoe UI Symbol&quot;, &quot;Android Emoji&quot;, EmojiSymbols;"
        dir="ltr">
        <div>Hi Marco, the upgrade process to 13.4.1 is still having
          some issues. I managed to upgrade from 13.1.1 to 13.3.1
          without any problems.<br>
          <br>
          When I try to upgrade from 13.3.1 to 13.4.1, I encounter
          several issues during the second stage of the upgrade.<br>
          <br>
          <b>First problem:</b></div>
        <br>
        <div>CREATE UNIQUE INDEX prosody_unique_index ON
          prosody(`host`(20), `user`(20), `store`(20), `key`(20)) USING
          BTREE<br>
          --------------<br>
          <br>
          ERROR 1061 (42000) at line 5 in file:
          '/usr/share/ngcp-db-schema/db_scripts/diff/15841.up':
          Duplicate key name 'prosody_unique_index'<br>
          <br>
          ERROR: the step 'mr12.5/ngcp_update_db_schema' failed, upgrade
          aborted!<br>
          Please fix the root of the issue and restart 'ngcp-upgrade'<br>
          (see error details in log file
/ngcp-data/ngcp-upgrade/mr13.3.1-mr13.4.1/logs/ngcp-upgrade-mr13.3.1-mr13.4.1-1755716002.log
          ).</div>
        <div><br>
        </div>
        <div>Bypass by comment DROP and CREATE in <span>/usr/share/ngcp-db-schema/db_scripts/diff/15841.up</span></div>
        <div><br>
        </div>
        <div><b>Second problem:</b></div>
        <div><br>
        </div>
        <div><span>After the update, some services won't start
            (including MariaDB). In the MariaDB logs, I see:</span></div>
        <div><span><br>
          </span></div>
        <div><span><br>
          </span></div>
        <div><span>
            <div>2025-08-20 20:56:27 0 [ERROR] InnoDB: The change buffer
              is corrupted<br>
              2025-08-20 20:56:27 0 [ERROR] InnoDB: Plugin
              initialization aborted with error Data structure
              corruption<br>
              2025-08-20 20:56:27 0 [Note] InnoDB: Starting shutdown...<br>
              2025-08-20 20:56:28 0 [ERROR] Plugin 'InnoDB' registration
              as a STORAGE ENGINE failed.<br>
              2025-08-20 20:56:28 0 [Note] Plugin 'FEEDBACK' is
              disabled.<br>
              2025-08-20 20:56:28 0 [Note] Plugin 'wsrep-provider' is
              disabled.<br>
              2025-08-20 20:56:28 0 [ERROR] Unknown/unsupported storage
              engine: InnoDB<br>
              2025-08-20 20:56:28 0 [ERROR] Aborting</div>
            <br>
          </span></div>
        <div><span><br>
          </span></div>
        <div><span><b><i><span><u>I have reverted the VM to 13.3.1 for
                    now</u></span></i></b></span></div>
        <div><span><b><i><span><u><br>
                  </u></span></i></b></span></div>
        <div><span><b><i><span><u><br>
                  </u></span></i></b></span></div>
        <br>
        <div style="color: rgb(0, 0, 0);">
          <hr tabindex="-1" style="display:inline-block; width:98%">
          <div id="divRplyFwdMsg" dir="ltr"><font
              face="Calibri, sans-serif" color="#000000"
              style="font-size:11pt"><b>Da:</b> Marco Capetta
              <a class="moz-txt-link-rfc2396E" href="mailto:mcapetta@sipwise.com">&lt;mcapetta@sipwise.com&gt;</a><br>
              <b>Inviato:</b> mercoledė 20 agosto 2025 17:16<br>
              <b>A:</b> Danny Cappellari<br>
              <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>
              <b>Oggetto:</b> Re: [Spce-user] Error during upgrade
              mr13.1.1 to mr13.4.1</font>
            <div> </div>
          </div>
          <div>
            <div dir="ltr">Hi Danny,
              <div><br>
              </div>
              <div>it seems that both SEMS and MARIADB services are
                failing.<br>
                You can check the respective logs and identify what it
                going wrong.</div>
              <div><br>
              </div>
              <div>Regards</div>
              <div>Marco</div>
            </div>
            <br>
            <div class="gmail_quote gmail_quote_container">
              <div dir="ltr" class="gmail_attr">On Wed, Aug 20, 2025 at
                2:23\u202fPM Danny Cappellari via Spce-user &lt;<a
                  href="mailto:spce-user@lists.sipwise.com"
                  moz-do-not-send="true" class="moz-txt-link-freetext">spce-user@lists.sipwise.com</a>&gt;
                wrote:<br>
              </div>
              <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
                <div class="msg-5429462461899694944">
                  <div dir="ltr">
                    <div id="m_-5429462461899694944divtagdefaultwrapper"
                      dir="ltr"
style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, &quot;EmojiFont&quot;, &quot;Apple Color Emoji&quot;, &quot;Segoe UI Emoji&quot;, NotoColorEmoji, &quot;Segoe UI Symbol&quot;, &quot;Android Emoji&quot;, EmojiSymbols;">
                      <div>Hi, we are unable to upgrade from mr13.1.1 to
                        mr13.4.1. We detect an error during the Second
                        Stage of Update (<span>ngcp-upgrade --target
                          mr13.4.1</span>)<br>
                        <br>
                        ngcp-service: info: Action restart skipped,
                        service acpid is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service kannel-bearerbox is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service kannel-smsbox is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service ngcp-logic-engine is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service ntpd is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service prometheus is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service rtpengine-recording is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service sssd is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service valkey is not enabled<br>
                        ngcp-service: info: Action restart skipped,
                        service vboxadd-service is not enabled<br>
                        Job for mariadb.service failed because the
                        control process exited with error code.<br>
                        See "systemctl status mariadb.service" and
                        "journalctl -xeu mariadb.service" for details.<br>
                        A dependency job for kamailio-proxy.service
                        failed. See 'journalctl -xe' for details. <br>
                        Job for ngcp-sems.service failed because the
                        control process exited with error code.<br>
                        See "systemctl status ngcp-sems.service" and
                        "journalctl -xeu ngcp-sems.service" for details.<br>
                        2025-08-20 14:19:03 spce: Synchronizing current
                        with expected services state<br>
                        Job for mariadb.service failed because the
                        control process exited with error code.<br>
                        See "systemctl status mariadb.service" and
                        "journalctl -xeu mariadb.service" for details.<br>
                        A dependency job for kamailio-proxy.service
                        failed. See 'journalctl -xe' for details. <br>
                        Job for ngcp-sems.service failed because the
                        control process exited with error code.<br>
                        See "systemctl status ngcp-sems.service" and
                        "journalctl -xeu ngcp-sems.service" for details.<br>
                        ERROR: the step 'mr9.5/apply_new_configs'
                        failed, upgrade aborted!<br>
                        Please fix the root of the issue and restart
                        'ngcp-upgrade'<br>
                        (see error details in log file
/ngcp-data/ngcp-upgrade/mr13.1.1-mr13.4.1/logs/ngcp-upgrade-mr13.1.1-mr13.4.1-1755692307.log
                        ).<br>
                        <br>
                        Any advice?</div>
                    </div>
                  </div>
                  -- <br>
                  Spce-user mailing list<br>
                  <a href="mailto:Spce-user@lists.sipwise.com"
                    target="_blank" moz-do-not-send="true"
                    class="moz-txt-link-freetext">Spce-user@lists.sipwise.com</a><br>
                  <a
href="http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a><br>
                </div>
              </blockquote>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
    </blockquote>
    <br>
  </body>
</html>