[Box Backup] testing boxbackup-0.09_plus2_vc2005fix_r410-backup-client-mingw32 on WinXP Home SP2

[Chris Wilson]

Hi Pete,

> Finished scan of local files
> File statistics: total file size uploaded 0, bytes already on server 0,
> encoded
> size 0
>
> It hangs there and doesn't terminate.  No obvious error in Event Viewer
> or with tail -f /var/log/box on the server.

This is the expected behaviour when you run it from the command line. It 
does not "fork into the background", as a Unix client does, because 
Windows does not have a fork() call. It should, when the time for another 
backup is reached, connect to the server again, backup any new files,
report "Finished scan", and wait for the next backup, etc.

If you want it to run in the background, you must run it as a Windows 
service.

> In another cygwin terminal, I ran:
> $ ./bbackupctl -c "C:\Program Files\Box Backup\bbackupd.conf"
> terminate
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> Daemon configuration summary:
>  AutomaticBackup = true
>  UpdateStoreInterval = 3 seconds
>  MinimumFileAge = 4 seconds
>  MaxUploadWait = 24 seconds
> Succeeded.

And that terminated the backup process without problems? If so, good, all 
as expected.

> So, I restart the daemon: $ ./bbackupd.exe -c "C:\Program Files\Box 
> Backup\bbackupd.conf"
>
> It hangs again.  Then in a second cygwin terminal I run:
> $ ./bbackupctl -c "C:\Program Files\Box Backup\bbackupd.conf"  reload
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> Daemon configuration summary:
>  AutomaticBackup = true
>  UpdateStoreInterval = 3 seconds
>  MinimumFileAge = 4 seconds
>  MaxUploadWait = 24 seconds
> Succeeded.
>
> And in the first terminal I get hundreds (thousands?) of:
>
> Communication error with control client: Server SocketOpenError
> ConnectNamedPipe failed: 6

This looks like a bug, I will investigate and get back to you.

> I couldn't find SocketOpenError or ConnectNamedPipe in the mail
> archives.  I tried using a cmd window and move the DataDirectory and
> CommandSocket to the F: drive, but that didn't help.

Unlikely to help.

> Otherwise, I think it's working.  bbackupquery works fine, and now
> accepts dashes in the command line:
>
> $ ./bbackupquery -c "C:\Program Files\Box Backup\bbackupd-test.conf"
> "list -odstr test" quit | grep 2006-02-08
> No random device -- additional seeding of random number generator not
> performed.
>
> 0000062f f-X--a 2006-02-08T14:47:16 00001 2006-02-08T0947.txt
> 00000630 f-X--- 2006-02-08T15:44:36 00001 2006-02-08T1044.txt
> 00000631 f-Xo-- 2006-02-08T15:47:05 00001 2006-02-08T1047.txt
> 00000632 f-X--- 2006-02-08T15:47:24 00001 .2006-02-08T1047.txt.swp
> 00000633 f-X--a 2006-02-08T15:47:36 00001 2006-02-08T1047.txt
> 00000634 f-X--- 2006-02-08T15:48:06 00001 2006-02-08T1048.iso
>
> It's not picking up new files, but I think that's because the time-zone
> bug is still present (see my other thread of a couple of weeks ago).
>
> Now, on the other hand, I was initially accidentally using an old
> cygwin or other install of bbackupd.exe that was in my path (I didn't
> run ./bbackupd..., ugh).

Initially being when? When it backed up the new files (after MaxUploadWait 
+ 5 hours?)

> I thought I was running the new version, and
> so I was happy to see that it was backing up new files immediately,
> albeit with the 5 hour time-zone bug:
>
> $ bbackupd.exe -c "C:\Program Files\Box Backup\bbackupd.conf"
> No random device -- additional seeding of random number generator not
> performed.
[...]
> /cygdrive/f/downloads/boxbackup/boxbackup-0.09_plus2_vc2005fix
> _r410-backup-client-mingw32
> $ ls -alrtF `which bbackupd`
> -rwxr-xr-x 1 Owner None 585642 Dec 19 12:50 /usr/local/bin/bbackupd*
> $ md5sum /usr/local/bin/bbackupd.exe
> 442596ab4e25c918466cae7466049f87 */usr/local/bin/bbackupd.exe
>
> Maybe that's the December "trunk"?

It's much smaller than any release of bbackupd.exe that I've ever made. 
It also reports version 0.09, not 0.09h_win32 (Nick's binary) or 
0.09_plus2 or 0.10 (my releases). Perhaps it is a cygwin build of the 
released 0.09?

> Notice how the new file gets backed up almost immediately:
>
> $ date; echo junk >  "C:\Documents and Settings\petjal\My
> Documents\tebuco\cli\box\test\2006-02-08T1218.txt"
> Wed Feb  8 12:18:25 EST 2006
> $ date ; ./bbackupquery -c "C:\Program Files\Box Backup\bbackupd.conf"
> "list -odstr test" quit | grep 2006-02-08T12
> Wed Feb  8 12:18:34 EST 2006
> No random device -- additional seeding of random number generator not
> performed.
>
> 0000068e f----- 2006-02-08T17:09:47 00001 2006-02-08T1209.txt
> 0000068f f----- 2006-02-08T17:15:57 00001 2006-02-08T1215.txt
> 00000690 f----- 2006-02-08T17:16:28 00001 2006-02-08T1216.txt
> 00000691 f----- 2006-02-08T17:18:25 00001 2006-02-08T1218.txt
>
> With the current boxwin, which is what I am using in production these
> days, I have to wait 5 hours before my files are backed up.  After
> killing everything, keeping my main bbackupd.conf with the short test
> timings, and restarting my boxwin service, and using the new
> bbackupquery so that I can use the dash in the command line:
[...]
> So, one bbackupd.exe version will backup immediately (with the speedy
> test timing settings), and others will not.  I'm not sure what's up
> with that.  Maybe it's a compiling thing?

That old build does not have the 5 hour problem? Perhaps it's due to the 
way we stat files in the native port (versus Cygwin). I will investigate 
this as well, although I don't have a system in a different timezone, so 
it will not be easy.

> FWIW, the new bbackupctl works with the older boxwin service daemon and 
> doesn't cause that error:

Not surprising, since the error is in bbackupd.exe and not bbackupctl.exe.

> Are there plans to update boxwin and boxi?  I really like them both. How 
> can I help?

I don't believe that boxwin will be updated again, although it's really up 
to Nick. I think we have merged all the features of boxwin into the trunk, 
so the release candidates I have been sending out should be equivalent to 
or better than the currently available version of boxwin (modulo the five 
hour timezone bug).

I definitely plan to continue development of Boxi and release new 
versions, but I'm too busy with the core code of Box Backup to do any 
development at this moment.

Of course you can help, by continuing to test Box Backup and Boxi, and 
continuing to nag us (me), here on the list, until all outstanding bugs 
are fixed. Or if you want to get into development, then finding and fixing 
bugs would be even more useful. Thanks!

Cheers, Chris.
-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |