Fixing Virtualizor Migration Issue: “Task Not Updated on Master from Last 30 Minutes”

When performing a VPS migration in Virtualizor, you may encounter this error:

Task not updated on Master from last 30 minutes

This issue is caused by a mismatch between task IDs on the Master and Slave servers. Specifically, the Master is expecting task updates from the Slave using an actid (Auto Increment ID) that is higher than the Slave’s current counter.

Here’s how to fix it using phpMyAdmin — no terminal access required.

✅ Step-by-Step Fix (Using phpMyAdmin)

1️⃣ On the Master Server

1. Log in to phpMyAdmin.

2. Select the virtualizor database.

3. Click the SQL tab.

4. Run this query:

🔒 Replace SLAVE_ID with the actual ID of the slave server (from Virtualizor panel: Servers > Manage Servers).

🔎 This returns the highest task ID the Master expects from the Slave.

2️⃣ On the Slave Server

1. Log in to phpMyAdmin.

2. Select the virtualizor database.

3. Click the SQL tab.

4. Run this query:

This shows the current highest task ID on the Slave.

3️⃣ Check the Result

• If the Slave’s actid is less than the Master’s slaveactid, the Slave can’t send valid updates.

• This is what causes the migration task to freeze.

4️⃣ Fix the Auto Increment on Slave

You need to set the Slave’s task table AUTO_INCREMENT to one more than the Master’s slaveactid.

✅ Example:

• If Master shows MAX(slaveactid) = 2001, set Slave’s AUTO_INCREMENT to 2002.

Two ways to do this:

Option A: Using GUI

1. In the Slave’s phpMyAdmin, open the tasks table.

2. Go to the Structure tab.

3. Find the actid field → Click Change.

4. Set Auto Increment to the new value.

5. Save the change.

Option B: Run this SQL on the Slave:

(Adjust 2002 to the correct value as per your case.)

🔁 Final Step: Resync Cron Jobs

If you have SSH access, run:

On Slave:

On Master:

If you don’t have SSH, Virtualizor’s background cron will sync it automatically in a few minutes.

🎉 That’s It!

You’ve successfully fixed the task ID desynchronization. Your VPS migration should now proceed without being stuck.