The support forum

2017.08.03 06:43:38.646 (UTC+1) 0 3 Timeout waiting for the command to complete

SEKCobra :

Aug 03, 2017

2017.08.03 02:27:36.177 (UTC+1) 3 3             Command: cmd /c "timeout /t 30 & rundll32 powrprof.dll,SetSuspendState Standby"
2017.08.03 02:27:36.177 (UTC+1) 3 4                 Timeout: 1 hour

This isn't a huge deal, but it means the backup restarts when I return the PC to active state and also starts the standby script again. Is there any way to tell bvckup to just ignore the return code of the script? Basically set the timeout to 0 or something?

Alex Pankratov :

Aug 03, 2017



Yes, it's possible. Set the following two lines in job's settings.ini as follows:

        conf.command_pre_timeout    1 sec
        conf.command_pre_crit             0

First sets the timeout, second tells bvckup to assume the script succeeded regardless of its exit code.

See here for instructions on how to find and edit settings.ini -
https://bvckup2.com/support/forum/topic/933

SEKCobra :

Aug 09, 2017

Sorry for the late reply, forgot to check back in here. Thanks for the advice!

SEKCobra :

Oct 21, 2017

I tried this but still get the same problem that after going to standby the backup thinks something went wrong. I just want it to ignore the command results altogether, really.

Alex Pankratov :

Oct 21, 2017

You will need to elaborate on exact symptoms. The INI patch I showed above does _exactly_ what you asked for in the opening post.

SEKCobra :

Oct 24, 2017

2017.10.24 02:26:40.428 (UTC+1) 0 2         Destination snapshot is out of sync
2017.10.24 02:26:40.428 (UTC+1) 3 3             Destination folder has been modified by another entity
2017.10.24 02:26:40.428 (UTC+1) 3 3             See "Detecting changes" section in this backup's settings for details
2017.10.24 02:26:40.428 (UTC+1) 2 2         Forcing destination re-scan and restarting the backup...
2017.10.24 02:26:40.479 (UTC+1) 2 2         Running external post-backup command ...

2017.10.24 02:26:40.506 (UTC+1) 3 3             Command: cmd /c ""C:\Program Files (x86)\PuTTY\plink" shutdown -p now & timeout /t 30 & rundll32 powrprof.dll,SetSuspendState Standby"
2017.10.24 02:26:40.506 (UTC+1) 3 4                 Spawn as: process
2017.10.24 02:26:40.506 (UTC+1) 3 4                 Exit code: any
2017.10.24 02:26:40.506 (UTC+1) 3 4                 Timeout: 1 second
2017.10.24 02:26:41.525 (UTC+1) 0 3             Timeout waiting for the command to complete
2017.10.24 02:26:41.525 (UTC+1) 2 1     Completed in 4.89 sec with 3 errors
2017.10.24 02:26:41.630 (UTC+1) 2 0 Restarting the backup ...
2017.10.24 02:26:41.630 (UTC+1) 2 1     Preparing ...
2017.10.24 02:26:41.630 (UTC+1) 3 2         Run number: 1215
2017.10.24 02:26:41.630 (UTC+1) 3 3             App: 78.9
2017.10.24 02:26:41.630 (UTC+1) 3 3             Source:
2017.10.24 02:26:41.630 (UTC+1) 3 3             Destination:
2017.10.24 02:26:41.630 (UTC+1) 3 3             Copying: contents, timestamps (modified, created, accessed), attributes
2017.10.24 02:26:41.630 (UTC+1) 3 4                 Using delta copier
2017.10.24 02:26:41.630 (UTC+1) 2 2         Verifying configuration ...
2017.10.24 02:26:41.630 (UTC+1) 3 3             Normalized src path:
2017.10.24 02:26:41.630 (UTC+1) 3 3             Normalized dst path:
2017.10.24 02:26:41.630 (UTC+1) 2 2         Checking source location ...
2017.10.24 02:26:41.630 (UTC+1) 3 3             OK
2017.10.24 02:26:41.630 (UTC+1) 2 2         Checking destination location ...
2017.10.24 02:26:43.637 (UTC+1) 0 3             Error: destination device is missing
2017.10.24 02:26:43.637 (UTC+1) 2 2         Running external post-backup command ...

2017.10.24 02:26:44.640 (UTC+1) 3 3             Command: cmd /c ""C:\Program Files (x86)\PuTTY\plink" shutdown -p now & timeout /t 30 & rundll32 powrprof.dll,SetSuspendState Standby"
2017.10.24 02:26:44.640 (UTC+1) 3 4                 Spawn as: process
2017.10.24 02:26:44.640 (UTC+1) 3 4                 Exit code: any
2017.10.24 02:26:44.640 (UTC+1) 3 4                 Timeout: 1 second
2017.10.24 02:26:45.656 (UTC+1) 0 3             Timeout waiting for the command to complete
2017.10.24 02:26:45.656 (UTC+1) 2 1     Completed in 4.03 sec with 2 errors
2017.10.24 02:26:45.658 (UTC+1) 2 0 Destination network share is no longer accessible

As you can see it restarts the backup after completely finishing it and after it turned off the desitnation server and (was supposed to) send the computer to sleep.

Alex Pankratov :

Oct 24, 2017

Looking into it...

Alex Pankratov :

Oct 24, 2017



OK, thanks for the report and your patience. This was indeed a bug and it should be resolved in 78.10.

In particular, the backup engine now treats timeouts as normal command completion _IF_ conf.command_pre_crit is set to 0.

Additionally, it is now possible to use "0 sec" timeout to make the backup continue immediately after launching a pre/post command and without waiting for it to complete.

SEKCobra :

Oct 24, 2017

Many thanks, this was a little thing but it was a bit annoying every once in a while. Absolutely love Bvckup otherwise!

New topic

Create
Made by Pipemetrics in Switzerland
Support


Follow
Twitter
Dev blog
Miscellanea Press resources
Testimonials
On robocopy
Company
Imprint

Legal Terms
Privacy