Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
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 (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. mysql: DB migration failed with 9.0.10 update

mysql: DB migration failed with 9.0.10 update

Scheduled Pinned Locked Moved Unsolved Support
upgrademigration
5 Posts 3 Posters 44 Views 3 Watching
  • 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.
  • K Offline
    K Offline
    keldorn
    wrote last edited by girish
    #1

    Upgrade to 9.0.10 fails partially

    Hello,

    So I have tried to upgrade from 8.3.2 to 9.0.10. At some point the dashboard would freeze indefinitely. The log indicates a DB migration failed.

    But when I reboot the VM, everything seems to be working fine, at least until a try to execute a backup, which will fails, presumably because the DB migration failed.

    Any help would be appreciated. (I have a paid subscription, but I figured it would be more helpful to other users If I share info here instead of using email support).

    Backup logs:

    Nov 16 01:01:46 box:locks write: current locks: {"full_backup_task_3c8364e2-f2b2-4a1c-84c8-d5bd386016f4":null}
    Nov 16 01:01:46 box:locks release: app_backup_04439498-8ce4-48b2-9b09-dc8492c571f7
    Nov 16 01:01:46 box:tasks setCompleted - 17471: {"result":null,"error":{"message":"Unknown column 'siteId' in 'field list'","reason":"Database Error"},"percent":100}
    Nov 16 01:01:46 box:tasks updating task 17471 with: {"completed":true,"result":null,"error":{"message":"Unknown column 'siteId' in 'field list'","reason":"Database Error"},"percent":100}
    Nov 16 01:01:46 box:taskworker Task took 105.083 seconds
    Nov 16 01:01:46 BoxError: Unknown column 'siteId' in 'field list'
    Nov 16 01:01:46 at Object.query (/home/yellowtent/box/src/database.js:96:22)
    Nov 16 01:01:46 at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    Nov 16 01:01:46 Exiting with code 0
    

    Update logs:

    I could not find the update logs, but the error message here is similar when I execute the following

    sudo /home/yellowtent/box/setup/start.sh
    
    mysqladmin: [Warning] Using a password on the command line interface can be insecure.
    Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
    mysql: [Warning] Using a password on the command line interface can be insecure.
    mysql: [Warning] Using a password on the command line interface can be insecure.
    2025-11-16T09:25:55 ==> start: Migrating data
    Backup counts. rsync: 1 tgz: 231 total: 232 . theOneFormat: null
    Existing format is tgz . Adding clone backup site for rsync
    [ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Unknown column 'priority' in 'field list'
        at /home/yellowtent/box/node_modules/db-migrate/lib/commands/on-complete.js:15:14
        at tryCatcher (/home/yellowtent/box/node_modules/bluebird/js/release/util.js:16:23)
        at Promise.successAdapter (/home/yellowtent/box/node_modules/bluebird/js/release/nodeify.js:22:30)
        at Promise._settlePromise (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:601:21)
        at Promise._settlePromiseCtx (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:641:10)
        at _drainQueueStep (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:97:12)
        at _drainQueue (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:86:9)
        at Async._drainQueues (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:102:5)
        at Async.drainQueues [as _onImmediate] (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:15:14)
        at process.processImmediate (node:internal/timers:485:21)
        at Packet.asError (/home/yellowtent/box/node_modules/mysql2/lib/packets/packet.js:740:17)
        at Query.execute (/home/yellowtent/box/node_modules/mysql2/lib/commands/command.js:29:26)
        at Connection.handlePacket (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:477:34)
        at PacketParser.onPacket (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:93:12)
        at PacketParser.executeStart (/home/yellowtent/box/node_modules/mysql2/lib/packet_parser.js:75:16)
        at Socket.<anonymous> (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:100:25)
        at Socket.emit (node:events:519:28)
        at addChunk (node:internal/streams/readable:561:12)
        at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
        at Readable.push (node:internal/streams/readable:392:5)
        at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
    

    System Details

    Cloudron Version

    "version": "9.0.10"

    Ubuntu Version

    No LSB modules are available.
    Distributor ID:	Ubuntu
    Description:	Ubuntu 24.04.3 LTS
    Release:	24.04
    Codename:	noble
    

    Cloudron installation method

    Options:

    • Manual with ./cloudron-setup

    Output of cloudron-support --troubleshoot

    sudo cloudron-support --troubleshoot
    Vendor: QEMU Product: Standard PC (Q35 + ICH9, 2009)
    Linux: 6.8.0-87-generic
    Ubuntu: noble 24.04
    Processor: 13th Gen Intel(R) Core(TM) i5-13400
    BIOS pc-q35-10.1  CPU @ 2.0GHz x 4
    RAM: 19976216KB
    Disk: /dev/vda2       104G
    [OK]	node version is correct
    [OK]	IPv6 is enabled in kernel. No public IPv6 address
    [OK]	docker is running
    [OK]	docker version is correct
    [OK]	MySQL is running
    [OK]	nginx is running
    [OK]	dashboard cert is valid
    [OK]	dashboard is reachable via loopback
    [OK]	box v9.0.10 is running
    [OK]	netplan is good
    [OK]	DNS is resolving via systemd-resolved
    [OK]	Dashboard is reachable via domain name
    [WARN]	Domain XXXXXX.ch e
    
    1 Reply Last reply
    1
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote last edited by
      #2

      @keldorn thanks for reporting. There is a bug in the migration where there are mixed backup formats from previous version (i.e maybe you changed the backup format from rsync to tgz or viceversa). Testing the fix.

      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote last edited by
        #3

        @keldorn Can you please try this:

        • Take the raw file from https://git.cloudron.io/platform/box/-/raw/417f5c36100ba63f41c4841c742b64a8448a2308/migrations/20250724141339-backups-add-siteId.js and put it into /home/yellowtent/box/migrations/20250724141339-backups-add-siteId.js
        • Then run, sudo /home/yellowtent/box/setup/start.sh
        1 Reply Last reply
        0
        • T Offline
          T Offline
          thoschworks
          wrote last edited by
          #4

          @girish

          I "fixed" the frozen UI by rebooting the host. Later I got problems with the back up.

          The fix with the changed file worked for me. 👍 👍 👍

          BTW: I have a new backup destination "Copy of Default". This backup gets stuck with the following error:

          Error opening new cache file: ENOENT: no such file or directory, open '/home/yellowtent/platformdata/backup/71675862-9254-4cb1-91ce-4c387c56723f/0038cb4e-cf5a-42f5-aeca-c5fbe7e86bad.sync.cache.new' 
          

          Should I open a new ticket for this?

          1 Reply Last reply
          0
          • K Offline
            K Offline
            keldorn
            wrote last edited by
            #5

            Hey @girish, thanks for fix.

            Just as @thoschworks, I got a "Copy of Default" backup destination, which I intend to use from now on. I haven't tried to execute a backup yet.

            1 Reply Last reply
            0
            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.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search