Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Update Debian 12 > 13 / Postgres 15 > 17

Update Debian 12 > 13 / Postgres 15 > 17

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 33.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    Spheron
    wrote on last edited by
    #1

    Hello @all,

    today i updated our NetXMS server vom Debian 12 to 13. At the first try i upgraded, as part of the Debian Update, the Postgres Cluster from 15 to 17 too. But there are many warnings:

    Example:

    Fixing hardcoded library paths for stored procedures...
    WARNUNG:  Version von Sortierfolge für Datenbank »postgres« stimmt nicht überein
    DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
    TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE postgres REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
    Upgrading database postgres...
    WARNUNG:  Version von Sortierfolge für Datenbank »postgres« stimmt nicht überein
    DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
    TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE postgres REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
    Fixing hardcoded library paths for stored procedures...
    WARNUNG:  Version von Sortierfolge für Datenbank »netxms« stimmt nicht überein
    DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
    TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE netxms REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
    Upgrading database netxms...
    WARNUNG:  Version von Sortierfolge für Datenbank »netxms« stimmt nicht überein
    DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
    TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE netxms REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
    

    So i decided to rollback the snapshot of the VM and upgrade Debian without the cluster update of Potsgres.

    Are there any howto's or links to websites where i can figure out how i make the Postgres Cluster Update from 15 to 17 on the "right" way for NetXMS?

    Greetings
    Marco

    1 Reply Last reply
    0
    • A
      A
      Alex Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      Those messages are warnings, not errors. Upgrade did not fail. This is normal PostgreSQL collation mismatch. Has nothing to do with 15→17 — comes only from Debian 12→13, because Trixie has glibc 2.41 instead of 2.36, and PostgreSQL remembers glibc version used to build indexes.

      For in-place upgrade use pg_upgradecluster. Stop NetXMS, make dump for safety, drop empty PG17 cluster that was auto-created, then upgrade:

      systemctl stop netxms-server
      sudo -u postgres pg_dump -Fc netxms > /backup/netxms.dump   # safety net
      pg_dropcluster 17 main --stop        # remove empty auto-created PG17 cluster
      pg_upgradecluster 15 main
      nxdbmgr check
      systemctl start netxms-server
      # when verified:  pg_dropcluster 15 main
      

      Important detail: pg_upgradecluster without --method=upgrade uses dump method inside. It rebuilds all indexes under new glibc, so you get no collation warnings and no reindex needed. Only -m upgrade / -m link (fast file-reuse mode) makes the warnings. If you use that mode, fix it correct way — reindex first, then refresh — for each database (netxms, postgres, template1):

      REINDEX DATABASE netxms;
      ALTER DATABASE netxms REFRESH COLLATION VERSION;
      

      Do not run only REFRESH. It hides warning but leaves bad-sorted indexes. Reindex is mandatory.

      1 Reply Last reply
      0
      • S
        S
        Spheron
        wrote on last edited by
        #3

        Hello Alex,

        thanks for the description. I tried that today, but running out of storage... 😞

        Is there an function in nxdbmgr or any other tool for deleting all DCI Data in tables, so the tables has less amount of data so i can do the migration?

        Greetings
        Marco

        1 Reply Last reply
        0
        • A
          A
          Alex Kirhenshtein
          wrote on last edited by
          #4

          Simplest approach is to modify retention time in server configuration, then run housekeeper (or just leave it overnight). Once done, vacuum DB and you'll have more space.

          1 Reply Last reply
          0
          • S
            S
            Spheron
            wrote on last edited by
            #5

            Hi Alex,

            thanks for the hint. I give it a try...

            Greetings
            Marco

            1 Reply Last reply
            0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            Powered by NodeBB Contributors
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups