The support forum

Bvckup 2 Unstoppable Changes Detection

Doequer :

Sep 26, 2018

Hello, I've just downloaded the last 79.9 version and after creating a test job, I'm seeing a weird program's behavior, which I have never seen before:

After enabling it, the test job keeps running indefinitely, because there is some "supposed" changes detection. But the thing is, there isn't actually any changes being made at all, not that I'm aware of at least.

I created two test folders, "copy a" and "copy b", they are empty and located at the system's desktop. But it doesn't matter if I create other ones at a different location. I have to disable it.

I leave you a partial section from "bvckup2.log" which came to my attention. Let me know if you need the full one.

2018.09.26 09:43:42.934 (UTC-3) 3 DC:38 en | Job [1] needs to run, reason 1
2018.09.26 09:43:42.934 (UTC-3) 3 DC:38 en | Created system shutdown block
2018.09.26 09:43:42.934 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [running]
2018.09.26 09:43:42.934 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 5, needs-a-run 0 at 2018/09/26 09:43:42.905, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:43:42.905
2018.09.26 09:43:43.038 (UTC-3) 2 DC:38 en | Job [1], state [running] -> [idle]
2018.09.26 09:43:43.038 (UTC-3) 3 DC:38 en | Released system shutdown block
2018.09.26 09:43:43.538 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 3, needs-a-run 2 at 2018/09/26 09:43:48.538, quiet 0 / 0000/00/00 00:00:00.000 => next 2018/09/26 09:43:48.538, was 0000/00/00 00:00:00.000
2018.09.26 09:43:48.554 (UTC-3) 3 DC:38 en | Job [1] needs to run, reason 2
2018.09.26 09:43:48.554 (UTC-3) 3 DC:38 en | Created system shutdown block
2018.09.26 09:43:48.554 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [running]
2018.09.26 09:43:48.554 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 5, needs-a-run 0 at 2018/09/26 09:43:48.538, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:43:48.538
2018.09.26 09:43:48.658 (UTC-3) 2 DC:38 en | Job [1], state [running] -> [idle]
2018.09.26 09:43:48.658 (UTC-3) 3 DC:38 en | Released system shutdown block
2018.09.26 09:43:49.159 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 3, needs-a-run 2 at 2018/09/26 09:43:54.159, quiet 0 / 0000/00/00 00:00:00.000 => next 2018/09/26 09:43:54.159, was 0000/00/00 00:00:00.000
2018.09.26 09:43:54.205 (UTC-3) 3 DC:38 en | Job [1] needs to run, reason 2
2018.09.26 09:43:54.205 (UTC-3) 3 DC:38 en | Created system shutdown block
2018.09.26 09:43:54.205 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [running]
2018.09.26 09:43:54.205 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 5, needs-a-run 0 at 2018/09/26 09:43:54.159, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:43:54.159
2018.09.26 09:43:54.311 (UTC-3) 2 DC:38 en | Job [1], state [running] -> [idle]
2018.09.26 09:43:54.311 (UTC-3) 3 DC:38 en | Released system shutdown block
2018.09.26 09:43:54.811 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 3, needs-a-run 2 at 2018/09/26 09:43:59.811, quiet 0 / 0000/00/00 00:00:00.000 => next 2018/09/26 09:43:59.811, was 0000/00/00 00:00:00.000
2018.09.26 09:43:59.855 (UTC-3) 3 DC:38 en | Job [1] needs to run, reason 2
2018.09.26 09:43:59.855 (UTC-3) 3 DC:38 en | Created system shutdown block
2018.09.26 09:43:59.855 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [running]
2018.09.26 09:43:59.855 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 5, needs-a-run 0 at 2018/09/26 09:43:59.811, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:43:59.811
2018.09.26 09:43:59.960 (UTC-3) 2 DC:38 en | Job [1], state [running] -> [idle]
2018.09.26 09:43:59.960 (UTC-3) 3 DC:38 en | Released system shutdown block
2018.09.26 09:44:00.460 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 3, needs-a-run 2 at 2018/09/26 09:44:05.460, quiet 0 / 0000/00/00 00:00:00.000 => next 2018/09/26 09:44:05.460, was 0000/00/00 00:00:00.000
2018.09.26 09:44:05.468 (UTC-3) 3 DC:38 en | Job [1] needs to run, reason 2
2018.09.26 09:44:05.468 (UTC-3) 3 DC:38 en | Created system shutdown block
2018.09.26 09:44:05.468 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [running]
2018.09.26 09:44:05.468 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 5, needs-a-run 0 at 2018/09/26 09:44:05.460, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:44:05.460
2018.09.26 09:44:05.573 (UTC-3) 2 DC:38 en | Job [1], state [running] -> [idle]
2018.09.26 09:44:05.573 (UTC-3) 3 DC:38 en | Released system shutdown block
2018.09.26 09:44:06.073 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 3, needs-a-run 2 at 2018/09/26 09:44:11.073, quiet 0 / 0000/00/00 00:00:00.000 => next 2018/09/26 09:44:11.073, was 0000/00/00 00:00:00.000
2018.09.26 09:44:06.924 (UTC-3) 3 DC:00 ui | Applying [disable] command to 1 job
2018.09.26 09:44:06.924 (UTC-3) 3 DC:00 ui | Job [1] is in [idle] state
2018.09.26 09:44:06.924 (UTC-3) 2 DC:38 en | Job [1], state [idle] -> [disabled]
2018.09.26 09:44:06.924 (UTC-3) 3 DC:38 en | Scheduling job [1] - state 1, needs-a-run 0 at 2018/09/26 09:44:11.073, quiet 0 / 0000/00/00 00:00:00.000 => next 0000/00/00 00:00:00.000, was 2018/09/26 09:44:11.073





Alex Pankratov :

Sep 26, 2018

What do you in the log for the job itself?

(It might be easier to look at this over email if you prefer)

Alex Pankratov :

Sep 26, 2018

Ah, I think we can reproduce this. Please stand by...

Doequer :

Sep 26, 2018

I didn't even have copied any files into the folders, but just enabled the job.

Another weird thing I noted (maybe related or not), is that program's initial window was way too wide. Something that I never saw happening before as well.

Alex Pankratov :

Sep 26, 2018



Should be resolved now with 79.10 -
https://bvckup2.com/support/forum/topic/1060/6168

Thanks for the heads up. Also reverted the default window size change. You are right, it looked better the old way :)

New topic

Create
Made by Pipemetrics in Switzerland
Support

Follow
Blog / RSS
Social Twitter
Reddit
Miscellanea Press resources
Testimonials
Company
Imprint
Legal Terms
Privacy