Replication, way in the future schedule

[Manny Vazquez]

I am trying to make a few machines replicate, this was working fine a while back , it stopped working and I never bothered with it since I really do not care much about the HA of this machines, but it wold be great to ave the replication, once a day working, but when I add the replication job, I get it schedule on Jan 1st, 2070, can someone help with this error?


this is on a 5.0 proxmox


But in the other cluster the schedule works fine on a proxmox 5.3

 

[wolfgang]

Hi
This looks like an over left artifact from a previous job.
please check /var/lib/pve-manager/pve-replication-state.json

 

[Manny Vazquez]

Hi
This looks like an over left artifact from a previous job.
please check /var/lib/pve-manager/pve-replication-state.json

Not sure how to check that,

I did a cat of this file on all 3 nodes, it is just {}
But I had deleted the jobs that of course where never going to execute, so I created anew job,



it scheduled again to 2070-01-01


And then did a cat of the .json file
the only thing inside that file is just {}



I have learned to live without replication and put only VMs that do not host live data on this cluster, meaning that a backup from 2 dats ago is as good as a backup from 10 minutes ago, but I would like to have replication back so I could put some more "live" vms on this cluster which is super reliable, it has been functional, no shutdown of any node, or problem for 1 year and a half. I did a full reboot manually of each one of the nodes on the one year anniversary, was that bad?

 

[dcsapak]

can you output of

date

on the hosts ?

also what is your pveversion -v ?

 

[Manny Vazquez]

can you output of

date

on the hosts ?

on all 3 affected hosts, not a second difference

also what is your pveversion -v ?

 

[dcsapak]

please upgrad to the current version (5.4) and try again

 

[Manny Vazquez]

please upgrad to the current version (5.4) and try again

Not an option for me.

 

[dcsapak]

Not an option for me.

if it is a bug, the only solution to fix it is update... i do not want to chase something which might already be fixed in a new version