Cannot add repeatable job

PeerTube
1

Hello, I get the following error when upgrading from v8.1.8 to v8.3.1 (on top of Debian 13)

oct 02 16:59:00 chorro peertube[18763]: [media.interior.edu.uy:443] 2026-10-02 16:59:00.290 error: Cannot add repeatable job. {
oct 02 16:59:00 chorro peertube[18763]:   "err": {
oct 02 16:59:00 chorro peertube[18763]:     "stack": "Error: Legacy repeatable job metadata is not supported in BullMQ v6 (key: \"job::::30 5 * * 5\"). Migrate legacy repeatable jobs to Job Schedulers before upgrading. See https://docs.bullmq.io/guide/migrations/migrate-from-v5-to-v6\n    at getLegacyRepeatableJobError (/var/www/peertube/versions/peertube-v8.3.1/node_modules/.pnpm/bullmq@6.3.6_ioredis@6.0.0_pg@8.23.0/node_modules/bullmq/dist/cjs/classes/job-scheduler.js:67:12)\n    at JobScheduler.transformSchedulerData (/var/www/peertube/versions/peertube-v8.3.1/node_modules/.pnpm/bullmq@6.3.6_ioredis@6.0.0_pg@8.23.0/node_modules/bullmq/dist/cjs/classes/job-scheduler.js:243:19)\n    at JobScheduler.getSchedulerData (/var/www/peertube/versions/peertube-v8.3.1/node_modules/.pnpm/bullmq@6.3.6_ioredis@6.0.0_pg@8.23.0/node_modules/bullmq/dist/cjs/classes/job-scheduler.js:200:32)\n    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at async Promise.all (index 0)\n    at async JobScheduler.getJobSchedulers (/var/www/peertube/versions/peertube-v8.3.1/node_modules/.pnpm/bullmq@6.3.6_ioredis@6.0.0_pg@8.23.0/node_modules/bullmq/dist/cjs/classes/job-scheduler.js:287:17)\n    at async JobQueue.pruneRepeatableJobs (file:///var/www/peertube/versions/peertube-v8.3.1/dist/core/lib/job-queue/job-queue.js:403:31)",
oct 02 16:59:00 chorro peertube[18763]:     "message": "Legacy repeatable job metadata is not supported in BullMQ v6 (key: \"job::::30 5 * * 5\"). Migrate legacy repeatable jobs to Job Schedulers before upgrading. See https://docs.bullmq.io/guide/migrations/migrate-from-v5-to-v6"
oct 02 16:59:00 chorro peertube[18763]:   }
oct 02 16:59:00 chorro peertube[18763]: }

Thank you!

2

Hi,

media.interior.edu.uy seems to be on a very old version. How can you upgrade from 8.1.8?

3

Hello, I am actually testing the upgrade on chorro.interior.edu.uy, with its IP pointed to media.interior.edu.uy in my /etc/hosts. I followed this upgrade path, taking into consideration all the relevant notes from the changelog:

v3.0.1 -> v3.1.0 -> v4.1.1 -> v4.3.1 -> v5.2.1 -> v6.3.3 -> v7.3.0 -> v8.0.2 -> v8.1.8 -> v8.3.1

I built this path guided by the manual database migrations, making sure not to accumulate too many configuration/dependencies changes.

Up until v8.3.1, the error I sent before had never appeared on the logs while starting the service.

4

Thank you. I think you can use a fresh Redis database: it shouldn’t hurt. You’ll just loose pending jobs, but I think it’s okay.